A company is designing a new customer portal (OLTP workload) that uses Amazon Aurora PostgreSQL. During marketing campaigns, the portal experiences sudden, massive surges in read traffic, while write traffic remains stable. The database must automatically scale read capacity to maintain latency under , and it must support a cross-region disaster recovery plan with a Recovery Time Objective (RTO) of less than and a Recovery Point Objective (RPO) of less than . The database must be encrypted at rest, and the encryption keys must support delegation to a separate security account for centralized key management. Which database and storage strategy meets these requirements?
- Deploy an Amazon Aurora Global Database with the primary cluster in the main region and a secondary cluster in the recovery region. Configure Aurora Auto Scaling to dynamically add reader instances to the clusters based on CPU utilization. Encrypt the clusters using Customer Managed Keys (CMKs) in AWS KMS in each region, configuring the key policies to allow access from the security account.Cevap
- BDeploy an Amazon Aurora cluster with Multi-AZ enabled in the main region. Configure the Multi-AZ standby instance to automatically scale its instance size during peak read traffic. Encrypt the database using AWS Managed Keys (aws/rds) and configure IAM policies to allow cross-account access from the security account.
- CDeploy Amazon Aurora PostgreSQL in the main region and set up cross-region replication to an Amazon RDS for PostgreSQL read replica in the recovery region. Use AWS Managed Keys (aws/rds) for database encryption and share the keys with the security account.
- DDeploy Amazon Aurora PostgreSQL in the main region with Aurora Auto Scaling enabled for reader instances. Use AWS Backup to replicate database backups to the recovery region every . Encrypt the database using Customer Managed Keys (CMKs) and delegate key management to the security account.
Cevap
Deploy an Amazon Aurora Global Database with the primary cluster in the main region and a secondary cluster in the recovery region, configure Aurora Auto Scaling based on CPU utilization, and encrypt using Customer Managed Keys (CMKs) in AWS KMS configured to allow access from the security account.
The correct strategy utilizes an Amazon Aurora Global Database to achieve cross-region disaster recovery, as it replicates data asynchronously with typical latency of less than 1 second (meeting the RPO of less than 1 minute) and can be promoted to a primary cluster in minutes (meeting the RTO of less than 10 minutes). Aurora Auto Scaling dynamically scales reader instances to handle read traffic spikes. Using Customer Managed Keys (CMKs) in AWS KMS is necessary because AWS Managed Keys cannot be shared cross-account or have their key policies modified to allow delegation of key management to a separate security account.
Adım Adım Çözüm
Anahtar Kavram
Selecting database replication, scaling, and key management strategies that satisfy specific RTO, RPO, performance, and cross-account security constraints.