AWS Elastic Block Store Storage – EBS

EC2 Elastic Block Storage – EBS

  • Elastic Block Storage – EBS provides highly available, reliable, durable, block-level storage volumes that can be attached to an EC2 instance.
  • EBS as a primary storage device is recommended for data that requires frequent and granular updates e.g. running a database or filesystem.
  • An EBS volume
    • behaves like a raw, unformatted, external block device that can be attached to a single EC2 instance at a time.
    • persists independently from the running life of an instance.
    • is Zonal and can be attached to any instance within the same Availability Zone and can be used like any other physical hard drive.
    • is particularly well-suited for use as the primary storage for file systems, databases, or any applications that require fine granular updates and access to raw, unformatted, block-level storage.

Elastic Block Storage Features

  • EBS Volumes are created in a specific Availability Zone and can be attached to any instance in that same AZ.
  • Volumes can be backed up by creating a snapshot of the volume, which is stored in S3.
  • Volumes can be created from a snapshot that can be attached to another instance within the same region.
  • Volumes can be made available outside of the AZ by creating and restoring the snapshot to a new volume anywhere in that region.
  • Snapshots can also be copied to other regions and then restored to new volumes, making it easier to leverage multiple AWS regions for geographical expansion, data center migration, and disaster recovery.
  • Volumes allow encryption using the EBS encryption feature. All data stored at rest, disk I/O, and snapshots created from the volume are encrypted.
  • Encryption occurs on the EC2 instance, providing encryption of data-in-transit from EC2 to the EBS volume.
  • Elastic Volumes help easily adapt the volumes as the needs of the applications change. Elastic Volumes allow you to dynamically increase capacity, tune performance, and change the type of any new or existing current generation volume with no downtime or performance impact.
  • You can dynamically increase size, modify the provisioned IOPS capacity, and change volume type on live production volumes.
  • General Purpose (SSD) volumes support up to 10,000 16000 IOPS and 160 250 MB/s of throughput and Provisioned IOPS (SSD) volumes support up to 20,000 64000 IOPS and 320 1000 MB/s of throughput.
  • EBS Magnetic volumes can be created from 1 GiB to 1 TiB in size; EBS General Purpose (SSD) and Provisioned IOPS (SSD) volumes can be created up to 16 TiB in size.

EBS Benefits

  • Data Availability
    • Data is automatically replicated in an Availability Zone to prevent data loss due to the failure of any single hardware component.
  • Data Persistence
    • persists independently of the running life of an EC2 instance
    • persists when an instance is stopped, started, or rebooted
    • Root volume is deleted, by default, on Instance termination but the behaviour can be changed using the DeleteOnTermination flag
    • All attached volumes persist, by default, on instance termination
  • Data Encryption
    • can be encrypted by the EBS encryption feature
    • uses 256-bit AES-256 and an Amazon-managed key infrastructure.
    • Encryption occurs on the server that hosts the EC2 instance, providing encryption of data-in-transit from the EC2 instance to EBS storage
    • Snapshots of encrypted EBS volumes are automatically encrypted.
  • Snapshots
    • provides the ability to create snapshots (backups) of any EBS volume and write a copy of the data in the volume to S3, where it is stored redundantly in multiple Availability Zones.
    • can be used to create new volumes, increase the size of the volumes or replicate data across Availability Zones or Regions.
    • are incremental backups and store only the data that was changed from the time the last snapshot was taken.
    • Snapshot size can probably be smaller than the volume size as the data is compressed before being saved to S3.
    • Even though snapshots are saved incrementally, the snapshot deletion process is designed so that you need to retain only the most recent snapshot in order to restore the volume.

EBS Volume Types

Refer blog post @ EBS Volume Types

EBS Volume

EBS Volume Creation

  • Creating New volumes
    • Completely new from console or command line tools and can then be attached to an EC2 instance in the same Availability Zone.
  • Restore volume from Snapshots
    • Volumes can also be restored from previously created snapshots
    • New volumes created from existing snapshots are loaded lazily in the background.
    • There is no need to wait for all of the data to transfer from S3 to the volume before the attached instance can start accessing the volume and all its data.
    • If the instance accesses the data that hasn’t yet been loaded, the volume immediately downloads the requested data from S3, and continues loading the rest of the data in the background.
    • Volumes restored from encrypted snapshots are always encrypted, by default.
  • Volumes can be created and attached to a running EC2 instance by specifying a block device mapping

EBS Volume Detachment

  • EBS volumes can be detached from an instance explicitly or by terminating the instance.
  • EBS root volumes can be detached by stopping the instance.
  • EBS data volumes, attached to a running instance, can be detached by unmounting the volume from the instance first.
  • If the volume is detached without being unmounted, it might result in the volume being stuck in a busy state and could possibly damage the file system or the data it contains.
  • EBS volume can be force detached from an instance, using the Force Detach option, but it might lead to data loss or a corrupted file system as the instance does not get an opportunity to flush file system caches or file system metadata.
  • Charges are still incurred for the volume after its detachment

EBS Volume Deletion

  • EBS volume deletion would wipe out its data and the volume can’t be attached to any instance. However, it can be backed up before deletion using EBS snapshots

EBS Volume Resize

  • EBS Elastic Volumes can be modified to increase the volume size, change the volume type, or adjust the performance of your EBS volumes.
  • If the instance supports Elastic Volumes, changes can be performed without detaching the volume or restarting the instance.

EBS Volume Snapshots

Refer blog post @ EBS Snapshot

EBS Encryption

  • EBS volumes can be created and attached to a supported instance type and support the following types of data
    • Data at rest
    • All disk I/O i.e All data moving between the volume and the instance
    • All snapshots created from the volume
    • All volumes created from those snapshots
  • Encryption occurs on the servers that host EC2 instances, providing encryption of data-in-transit from EC2 instances to EBS storage.
  • EBS encryption is supported with all EBS volume types (gp2, io1, st1, and sc1), and has the same IOPS performance on encrypted volumes as with unencrypted volumes, with a minimal effect on latency
  • EBS encryption is only available on select instance types.
  • Volumes created from encrypted snapshots and snapshots of encrypted volumes are automatically encrypted using the same encryption key.
  • EBS encryption uses AWS KMS customer master keys (CMK) when creating encrypted volumes and any snapshots created from the encrypted volumes.
  • EBS volumes can be encrypted using either
    • a default CMK created for you automatically.
    • a CMK that you created separately using AWS KMS, giving you more flexibility, including the ability to create, rotate, disable, define access controls, and audit the encryption keys used to protect your data.
  • Public or shared snapshots of encrypted volumes are not supported, because other accounts would be able to decrypt your data and needs to be migrated to an unencrypted status before sharing.
  • Existing unencrypted volumes cannot be encrypted directly, but can be migrated by
    • Option 1
      • create an unencrypted snapshot from the volume
      • create an encrypted copy of an unencrypted snapshot
      • create an encrypted volume from the encrypted snapshot
    • Option 2
      • create an unencrypted snapshot from the volume
      • create an encrypted volume from an unencrypted snapshot
  • An encrypted snapshot can be created from an unencrypted snapshot by creating an encrypted copy of the unencrypted snapshot.
  • Unencrypted volume cannot be created from an encrypted volume directly but needs to be migrated

EBS Multi-Attach

Refer blog Post @ EBS Multi-Attach

EBS Performance

Refer blog Post @ EBS Performance

EBS vs Instance Store

Refer blog post @ EBS vs Instance Store

AWS Certification Exam Practice Questions

  • Questions are collected from Internet and the answers are marked as per my knowledge and understanding (which might differ with yours).
  • AWS services are updated everyday and both the answers and questions might be outdated soon, so research accordingly.
  • AWS exam questions are not updated to keep up the pace with AWS updates, so even if the underlying feature has changed the question might not be updated
  • Open to further feedback, discussion and correction.
  1. _____ is a durable, block-level storage volume that you can attach to a single, running Amazon EC2 instance.
    1. Amazon S3
    2. Amazon EBS
    3. None of these
    4. All of these
  2. Which Amazon storage do you think is the best for my database-style applications that frequently encounter many random reads and writes across the dataset?
    1. None of these.
    2. Amazon Instance Storage
    3. Any of these
    4. Amazon EBS
  3. What does Amazon EBS stand for?
    1. Elastic Block Storage
    2. Elastic Business Server
    3. Elastic Blade Server
    4. Elastic Block Store
  4. Which Amazon Storage behaves like raw, unformatted, external block devices that you can attach to your instances?
    1. None of these.
    2. Amazon Instance Storage
    3. Amazon EBS
    4. All of these
  5. A user has created numerous EBS volumes. What is the general limit for each AWS account for the maximum number of EBS volumes that can be created?
    1. 10000
    2. 5000
    3. 100
    4. 1000
  6. Select the correct set of steps for exposing the snapshot only to specific AWS accounts
    1. Select Public for all the accounts and check mark those accounts with whom you want to expose the snapshots and click save.
    2. Select Private and enter the IDs of those AWS accounts, and click Save.
    3. Select Public, enter the IDs of those AWS accounts, and click Save.
    4. Select Public, mark the IDs of those AWS accounts as private, and click Save.
  7. If an Amazon EBS volume is the root device of an instance, can I detach it without stopping the instance?
    1. Yes but only if Windows instance
    2. No
    3. Yes
    4. Yes but only if a Linux instance
  8. Can we attach an EBS volume to more than one EC2 instance at the same time?
    1. Yes
    2. No
    3. Only EC2-optimized EBS volumes.
    4. Only in read mode.
  9. Do the Amazon EBS volumes persist independently from the running life of an Amazon EC2 instance?
    1. Only if instructed to when created
    2. Yes
    3. No
  10. Can I delete a snapshot of the root device of an EBS volume used by a registered AMI?
    1. Only via API
    2. Only via Console
    3. Yes
    4. No
  11. By default, EBS volumes that are created and attached to an instance at launch are deleted when that instance is terminated. You can modify this behavior by changing the value of the flag_____ to false when you launch the instance
    1. DeleteOnTermination
    2. RemoveOnDeletion
    3. RemoveOnTermination
    4. TerminateOnDeletion
  12. Your company policies require encryption of sensitive data at rest. You are considering the possible options for protecting data while storing it at rest on an EBS data volume, attached to an EC2 instance. Which of these options would allow you to encrypt your data at rest? (Choose 3 answers)
    1. Implement third party volume encryption tools
    2. Do nothing as EBS volumes are encrypted by default
    3. Encrypt data inside your applications before storing it on EBS
    4. Encrypt data using native data encryption drivers at the file system level
    5. Implement SSL/TLS for all services running on the server
  13. Which of the following are true regarding encrypted Amazon Elastic Block Store (EBS) volumes? Choose 2 answers
    1. Supported on all Amazon EBS volume types
    2. Snapshots are automatically encrypted
    3. Available to all instance types
    4. Existing volumes can be encrypted
    5. Shared volumes can be encrypted
  14. How can you secure data at rest on an EBS volume?
    1. Encrypt the volume using the S3 server-side encryption service
    2. Attach the volume to an instance using EC2’s SSL interface.
    3. Create an IAM policy that restricts read and write access to the volume.
    4. Write the data randomly instead of sequentially.
    5. Use an encrypted file system on top of the EBS volume
  15. A user has deployed an application on an EBS backed EC2 instance. For a better performance of application, it requires dedicated EC2 to EBS traffic. How can the user achieve this?
    1. Launch the EC2 instance as EBS dedicated with PIOPS EBS
    2. Launch the EC2 instance as EBS enhanced with PIOPS EBS
    3. Launch the EC2 instance as EBS dedicated with PIOPS EBS
    4. Launch the EC2 instance as EBS optimized with PIOPS EBS
  16. A user is trying to launch an EBS backed EC2 instance under free usage. The user wants to achieve encryption of the EBS volume. How can the user encrypt the data at rest?
    1. Use AWS EBS encryption to encrypt the data at rest (Encryption is allowed on micro instances)
    2. User cannot use EBS encryption and has to encrypt the data manually or using a third party tool (Encryption was not allowed on micro instances before)
    3. The user has to select the encryption enabled flag while launching the EC2 instance
    4. Encryption of volume is not available as a part of the free usage tier
  17. A user is planning to schedule a backup for an EBS volume. The user wants security of the snapshot data. How can the user achieve data encryption with a snapshot?
    1. Use encrypted EBS volumes so that the snapshot will be encrypted by AWS
    2. While creating a snapshot select the snapshot with encryption
    3. By default the snapshot is encrypted by AWS
    4. Enable server side encryption for the snapshot using S3
  18. A user has launched an EBS backed EC2 instance. The user has rebooted the instance. Which of the below mentioned statements is not true with respect to the reboot action?
    1. The private and public address remains the same
    2. The Elastic IP remains associated with the instance
    3. The volume is preserved
    4. The instance runs on a new host computer
  19. A user has launched an EBS backed EC2 instance. What will be the difference while performing the restart or stop/start options on that instance?
    1. For restart it does not charge for an extra hour, while every stop/start it will be charged as a separate hour
    2. Every restart is charged by AWS as a separate hour, while multiple start/stop actions during a single hour will be counted as a single hour
    3. For every restart or start/stop it will be charged as a separate hour
    4. For restart it charges extra only once, while for every stop/start it will be charged as a separate hour
  20. A user has launched an EBS backed instance. The user started the instance at 9 AM in the morning. Between 9 AM to 10 AM, the user is testing some script. Thus, he stopped the instance twice and restarted it. In the same hour the user rebooted the instance once. For how many instance hours will AWS charge the user?
    1. 3 hours
    2. 4 hours
    3. 2 hours
    4. 1 hour
  21. You are running a database on an EC2 instance, with the data stored on Elastic Block Store (EBS) for persistence At times throughout the day, you are seeing large variance in the response times of the database queries Looking into the instance with the isolate command you see a lot of wait time on the disk volume that the database’s data is stored on. What two ways can you improve the performance of the database’s storage while maintaining the current persistence of the data? Choose 2 answers
    1. Move to an SSD backed instance
    2. Move the database to an EBS-Optimized Instance
    3. Use Provisioned IOPs EBS
    4. Use the ephemeral storage on an m2.4xLarge Instance Instead
  22. An organization wants to move to Cloud. They are looking for a secure encrypted database storage option. Which of the below mentioned AWS functionalities helps them to achieve this?
    1. AWS MFA with EBS
    2. AWS EBS encryption
    3. Multi-tier encryption with Redshift
    4. AWS S3 server-side storage
  23. A user has stored data on an encrypted EBS volume. The user wants to share the data with his friend’s AWS account. How can user achieve this?
    1. Create an AMI from the volume and share the AMI
    2. Copy the data to an unencrypted volume and then share
    3. Take a snapshot and share the snapshot with a friend
    4. If both the accounts are using the same encryption key then the user can share the volume directly
  24. A user is using an EBS backed instance. Which of the below mentioned statements is true?
    1. The user will be charged for volume and instance only when the instance is running
    2. The user will be charged for the volume even if the instance is stopped
    3. The user will be charged only for the instance running cost
    4. The user will not be charged for the volume if the instance is stopped
  25. A user is planning to use EBS for his DB requirement. The user already has an EC2 instance running in the VPC private subnet. How can the user attach the EBS volume to a running instance?
    1. The user must create EBS within the same VPC and then attach it to a running instance.
    2. The user can create EBS in the same zone as the subnet of instance and attach that EBS to instance. (Should be in the same AZ)
    3. It is not possible to attach an EBS to an instance running in VPC until the instance is stopped.
    4. The user can specify the same subnet while creating EBS and then attach it to a running instance.
  26. A user is creating an EBS volume. He asks for your advice. Which advice mentioned below should you not give to the user for creating an EBS volume?
    1. Take the snapshot of the volume when the instance is stopped
    2. Stripe multiple volumes attached to the same instance
    3. Create an AMI from the attached volume (AMI is created from the snapshot)
    4. Attach multiple volumes to the same instance
  27. An EC2 instance has one additional EBS volume attached to it. How can a user attach the same volume to another running instance in the same AZ?
    1. Terminate the first instance and only then attach to the new instance
    2. Attach the volume as read only to the second instance
    3. Detach the volume first and attach to new instance
    4. No need to detach. Just select the volume and attach it to the new instance, it will take care of mapping internally
  28. What is the scope of an EBS volume?
    1. VPC
    2. Region
    3. Placement Group
    4. Availability Zone

Reference

Amazon_EBS

61 thoughts on “AWS Elastic Block Store Storage – EBS

  1. Hi Jayendra, Thank you for your effort to put all the docs in one place.
    Regarding question number 24 , how can the answer ‘Snapshots are automatically encrypted’ is correct ? If the volume in not encrypted , the snapshot you take will not be encrypted. Please correct me if I am wrong.

    Thanks.
    Tarun

  2. Key point in the question is the behavior of Encrypted EBS Volumes, and snapshots generated from an encrypted volumes are always encrypted.

  3. Hi Jayendra, Can you please clarify question no 25.EBS snapshots characteristics

    EBS snapshots can only be restored and mounted to an instance in the same Availability Zone as the original EBS volume….

    I believe EBS snapshot can be copied into other region as well and can restore as volume.?

    1. Hi Muthu, by default EBS snapshots are AZ specific and you cannot create an instance in a different AZ or Region without it being copied. You can always copy a snapshot to a different AZ or region and restore a volume, but the snapshot is different and not the original snapshot.

        1. Agreed Sophia, I had corrected the answer based on the follow up discussions as per the comments below. Snapshots are region specific and not limited to the same AZ

    2. #25. I think the answer should be C. You can not attach a volume to a running instance. I tried and I got the error.

      1. What error did you get ?
        Haven’t tried it, but as per AWS documentation EBS volume can be attached to a running instance except if it has AWS Marketplace product code.

  4. If there is no need to pre-warm as you answered in question(6) why do we see a iops loss in first time we attach the EBS as you answered Question(7) ?

    this making me confused.

      1. Hi Jayandra

        We can enable ‘Encryption’ flag for attached ebs volume. why would we need to go for third party tools for encryption?

        1. Question is a bit old, as previously AWS did not allow encryption of the Root volumes and it had to be done with third party tools. It has changed now.

  5. If there is no need to pre-warm as you answered in question(6) why do we see a iops loss in first time we attach the EBS as you answered Question(7) ?

    this making me confused.

    1. As mentioned, the questions may be outdated, but still appear on the exam, as they do not keep pace with the AWS updates.
      For #6, pre warming was needed before but is not needed anymore.
      For #7, the IOPS are lost cause of Pre Warming, but the question is not valid anymore but can still come in the exam unless AWS updates it question set.

      1. Thanks for the information , so at the moment in real life scenario you will not be losing any IOPS the first time.

    1. AWS billing hour is reset for every Stop & Start but not for restart
      for e.g. if you have a instance running for one hour
      1. you stop and start the instance during that one hour (at probably half an hour in that hour), you would actually be be charged for 2 hours even though you had the instance running for One hour only i.e. two partial hours are rounded off to 2 full hours
      1. you restarted/rebooted the instance during that one hour (at probably half an hour in that hour), you would actually be be charged for 1 hour only.

      1. Hi jay,
        isn’t EC2 charges are second based not hourly?
        https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html

        “When you stop an instance, we shut it down. We don’t charge usage for a stopped instance, or data transfer fees, but we do charge for the storage for any Amazon EBS volumes. Each time you start a stopped instance we charge a minimum of one minute for usage. After one minute, we charge only for the seconds you use. For example, if you run an instance for 20 seconds and then stop it, we charge for a full one minute. If you run an instance for 3 minutes and 40 seconds, we charge for exactly 3 minutes and 40 seconds of usage.”

        Thanks for a great blog.

        1. Thats right, the pricing is now changed from hourly basis. We check and update accordingly.

      2. “Pricing is per instance-hour consumed for each instance, from the time an instance is launched until it is terminated or stopped. Each partial instance-hour consumed will be billed per-second for Linux Instances and as a full hour for all other instance types.”

  6. Hi Jayendra
    Thanks for your wonderful website.

    Question 28: A user is trying to launch an EBS backed EC2 instance under free usage. The user wants to achieve encryption of the EBS volume. How can the user encrypt the data at rest?

    Just to my understanding its pointing to Root Volume ? if not then the correct answer is selecting the flag.

    Rez

    1. Its an EBS backed Instance and hence the EBS volume is the root volume. The key point here is under free usage, which was not supported before.
      However, there have been quite some changes with EC2 encryption, with EC2 boot volume encryption being supported, and encryption was also supported for t2.micro instances recently which are the only ones available in free tier usage.

  7. Hi
    For QN #25 i guess a and ba are correct and d is not

    d. EBS snapshots can only be restored and mounted to an instance in the same Availability Zone as the original EBS volume (Snaphots are specific to region not AZ and we can take a snapshot of te running instance).

    Please correct if I am wrong.

    Great Blog… cheers

    1. Thanks Masood, you are correct, snapshot can be used to create a volume in any AZ and does not depend on the original EBS AZ volume from which the snapshot was taken

    1. Correct. As the documentation mentions, stopping seems be the quicker and consistent approach, as the handling would not be done by you.

      Then ensure that the associated EC2 instance is no longer writing to the RAID array by taking steps such as freezing the file system, unmounting the RAID array, or shutting down the associated EC2 instance

  8. Hello Jayendra

    23. A user has stored data on an encrypted EBS volume. The user wants to share the data with his friend’s AWS account. How can user achieve this?

    Since its a encrypted volume and wanted to share specific account, we can take a snapshot and share with others account. Why do we need to unencrypt and share ?
    could you please clarify?

    1. Encrypted snapshots were not permitted to be shared between accounts or made public, for security reasons as it needs providing the encryption as well.
      So ideally you had to create an unencrypted snapshot and share it.
      However, this has changed with Cross Account Sharing of Encrypted EBS Snapshots @ Blog Link and may not be applicable.

      1. I agree that we can’t share encrypted snapshots shared with public, but we can share with particular account. Pls find below the url :

        http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSEncryption.html

        “Snapshots that are taken from encrypted volumes are automatically encrypted. Volumes that are created from encrypted snapshots are also automatically encrypted. Public snapshots of encrypted volumes are not supported, but you can share an encrypted snapshot with specific accounts if you take the following steps:

        Use a custom CMK, not your default CMK, to encrypt your volume.
        Give the specific accounts access to the custom CMK.
        Create the snapshot.
        Give the specific accounts access to the snapshot.”

        Based on the above theory we have to choose option ‘C’.

        Please correct me if I am wrong

        1. Agreed. This is an old question and outdated and the answer #B was valid before.
          If the question still exists on the exam, your best bet would be B.
          However, #C is still not a complete answer cause it does not mention sharing of the keys, without which it would not work.

          1. They released Cross account Copying. So we can go with “Take a snapshot and share the snapshot with a friend.” but they did not mentioned about same keys. What you suggest and what is the correct answer. If they ask same question for February 2018 Release.

  9. Hello Jayendra.

    Question #9 – EBS root volumes can persist independently from the running life of the instance if they are instructed, but ,in general, EBS volumes persist by default, unless you check “Delete on termination”.
    So, what makes you think the right answer is #a?

    Thank you for your blog!

    1. Thanks Eduardo, the behavior is different for the root EBS volumes and the attached EBS volumes which had a different selection for Delete on Termination option.
      So you can always specify or change this behavior, hence the selection is #a.

  10. Jayendra, then if the question where written in the opposite way, the answer would be still the same, right?

    i.e. Is data on Amazon EBS volumes deleted independently from the running life of an Amazon EC2 instance? Only if instructed to when created

    1. yup Eduardo, the deletion or non deletion can be controlled (instructed is rather a loose term here) when you create and instance and attach volumes to it. So the answer would still remain the same.

  11. Thanks so much! This is by far the best study material I have seen besides the AWS whitepapers and documentation.

    1. Thanks Nandkishor, will update the same
      Encryption was not allowed before on Micro instance, which were allowed in free tier.
      However, with latest enhancements this is allowed.

  12. For question 23, answer should be A as using AMI, we can create an decrypt image of encrypted volume and make it public or share with friends,
    This seems to be more valid rather than copying data to volume and share,

    What’s your suggestion,

  13. Q13 says snapshot are always encrypted whereas Q17 says Use encrypted EBS volumes so that the snapshot will be encrypted by AWS

    1. Both of them talk about Encrypted Amazon Elastic Block Store (EBS) volumes
      For normal EBS volumes, snapshots are not encrypted.

  14. Hi,

    I think answer for below should be “a”.
    Pls suggest.

    18. A user has launched an EBS backed EC2 instance. The user has rebooted the instance. Which of the below mentioned statements is not true with respect to the reboot action?
    a. The private and public address remains the same.
    b. The Elastic IP remains associated with the instance.
    c. The volume is preserved.
    d. The instance runs on a new host computer.

  15. Hello,

    It looks like “a” is the correct answer for this. Pls suggest.

    5. A user has provisioned 2000 IOPS to the EBS volume. The application hosted on that EBS is experiencing less IOPS than provisioned. Which of the below mentioned options does not affect the IOPS of the volume?
    a. The application does not have enough IO for the volume.
    b. Instance is EBS optimized.
    c. The EC2 instance has 10 Gigabit Network connectivity.
    d. Volume size is too large.

  16. Hi jayendra,

    I guess D is false… as its just a reboot..so it wont reboot on another host…
    Regarding A..will ip remain same after reboot or not..

    Please clarify

    1. My bad it should be d. As the reboot, will not launch it on a new host. While all the other things are preserved. The IPs remain the same.

  17. Hi Jeyandra
    Designing storage layer for a production relational database. Database will run on Amazon EC2. The database is accessed by an application that performs intensive read and writes, so database requires lowest random /i/o latency
    Which data storage method fulfills above requirements?

    Store data in file system backed by amazon efs
    Store data in amazon s3 and use third party solution to expose s3 as file system to db server
    Stripe dat aacross multiple amazon ebs volumes using raid 0

    Which option would you chose?

    1. I had actually divided the topic further and moved the questions accordingly. Thats why the different.

Comments are closed.