Which of the following designs will meet these objectives?
Instantiate a c3.8xlarge instance in us-east-1. Provision 4x1TB EBS volumes, attach them to the instance, and configure them as a single RAID 5 volume. Ensure that EBS snapshots are performed every 15 minutes.
Instantiate a c3.8xlarge instance in us-east-1. Provision 3xlTB EBS volumes, attach them to the Instance, and configure them as a single RAID 0 volume. Ensure that EBS snapshots are performed every 15 minutes.
Instantiate an i2.8xlarge instance in us-east-1a. Create a RAID 0 volume using the four 800GB SSD ephemeral disks provided with the instance. Provision 3x1TB EBS volumes, attach them to the instance, and configure them as a second RAID 0 volume. Configure synchronous, block-level replication from the ephemeral-backed volume to the EBS-backed volume.
Instantiate a c3.8xlarge instance in us-east-1. Provision an AWS Storage Gateway and configure it for 3 TB of storage and 100,000 IOPS. Attach the volume to the instance.
Instantiate an i2.8xlarge instance in us-east-1a. Create a RAID 0 volume using the four 800GB SSD ephemeral disks provided with the instance. Configure synchronous, block-level replication to an identically configured instance in us-east-1b.
Explanations:
RAID 5 can tolerate a single disk failure, but it does not meet the performance requirements for 100,000 IOPS. Additionally, EBS volumes do not span across Availability Zones, so this setup cannot survive an Availability Zone failure.
RAID 0 can provide high performance, but it has no redundancy, so it cannot tolerate any disk failure. Additionally, EBS volumes do not span across Availability Zones, making it unable to survive an Availability Zone failure.
While using RAID 0 with ephemeral storage provides high performance, ephemeral disks do not survive instance termination or Availability Zone failure, and RAID 0 provides no redundancy. Therefore, it does not meet the durability requirements for data persistence across disk, instance, or AZ failure.
AWS Storage Gateway is typically used for hybrid cloud storage rather than high-performance block storage in the cloud, and it cannot provide 100,000 IOPS. It also does not inherently replicate data across Availability Zones.
RAID 0 using ephemeral disks on i2 instances can achieve high IOPS, and synchronous replication to an identical instance in a different Availability Zone provides redundancy across disk, instance, and AZ. This setup meets the performance, capacity, and durability requirements.
I design that the answer is:
Instantiate an i2.8xlarge instance in us-east-1a. Create a RAID 0 volume using the four 800GB SSD ephemeral disks provided with the instance. Configure synchronous, block-level replication to an identically configured instance in us-east-1b.
I believe the answer is:
Instantiate an i2.8xlarge instance in us-east-1a. Create a RAID 0 volume using the four 800GB SSD ephemeral disks provided with the instance. Configure synchronous, block-level replication to an identically configured instance in us-east-1b.