A financial services company is migrating a legacy SQL-based clustered database to Amazon EC2. The database cluster requires a shared block storage volume that can be concurrently mounted by up to Nitro-based EC2 instances in a single Availability Zone. The storage must support clustered file system protocols, require SCSI-3 persistent reservations for node fencing, and deliver consistent sub-millisecond latency. Which storage solution will meet these requirements with the highest performance?
- Provision an Amazon EBS io2 volume, enable EBS Multi-Attach, and mount the volume across the EC2 database instances.Answer
- BProvision an Amazon EBS gp3 volume, enable EBS Multi-Attach, and mount the volume across the EC2 database instances.
- CCreate an Amazon EFS file system configured with Provisioned Throughput and Max I/O performance mode, and mount it on the EC2 instances.
- DCreate an Amazon FSx for Lustre file system using SSD storage, and mount it concurrently using the Lustre client on all EC2 instances.
Answer
Provision an Amazon EBS io2 volume, enable EBS Multi-Attach, and mount the volume across the EC2 database instances.
The correct option is correct because Amazon EBS Multi-Attach enables attaching a single Provisioned IOPS SSD (io1 or io2) volume to up to Nitro-based EC2 instances in the same Availability Zone. Furthermore, io2 volumes natively support SCSI-3 persistent reservations, which are a prerequisite for clustered database deployments requiring node fencing, while offering consistent sub-millisecond latency.
Step-by-Step Solution
Key Concept
Amazon EBS Multi-Attach with SCSI-3 Persistent Reservations on io2 Volumes