Practice & Scenarios
A database requires 20,000 IOPS consistently. Which volume type?
Answer: io2 - Provisioned IOPS SSD
Cost-effective storage for infrequently accessed log files?
Answer: sc1 - Cold HDD
Big data analytics requiring high throughput?
Answer: st1 - Throughput Optimized HDD
How to copy encrypted snapshot to another region?
Answer: Copy with re-encryption using destination region KMS key
Restore from snapshot with immediate full performance?
Answer: Enable Fast Snapshot Restore (FSR)
Automate daily snapshots with 30-day retention?
Answer: Use Data Lifecycle Manager (DLM)
How to encrypt existing unencrypted EBS volume?
Enable encryption for all new EBS volumes?
gp2 volume performance degrading after initial burst?
Answer: Upgrade to gp3 or increase volume size
Inconsistent EBS performance on EC2 instance?
Answer: Enable EBS-optimized instance
Monitor EBS volume performance metrics?
Answer: Use CloudWatch VolumeReadOps, VolumeWriteOps
Share EBS volume between multiple EC2 instances?
Answer: Use Multi-Attach with io1/io2 and cluster file system
Increase EBS volume size without downtime?
Answer: Use Elastic Volumes feature
Oracle RAC cluster storage requirements?
Answer: io2 Multi-Attach with cluster-aware file system
Company migrating 2TB database requiring 15,000 IOPS with 99.99% uptime SLA.
Solution:
Critical application needs cross-region backup with 4-hour RTO requirement.
Solution:
Using HDD volumes as boot volumes
Expecting Multi-Attach to work with standard file systems
Not extending file system after volume resize
gp3: 16,000 | io2: 64,000 | gp2: 16,000
Match workload requirements to appropriate type
Cannot directly encrypt existing volumes