An organization is designing a high-volume financial transaction platform (OLTP workload). The platform requires a relational database that can support up to 50,000 read requests per second and 10,000 write requests per second. The system must maintain a Recovery Point Objective (RPO) of 0 (no data loss) and a Recovery Time Objective (RTO) of less than 30 seconds during an Availability Zone outage. The database must encrypt all data at rest, and the security team in Account A must centrally manage the encryption keys and audit key usage for database instances deployed in Account B.
Which database and storage configuration meets these requirements?
- Deploy an Amazon Aurora PostgreSQL database cluster in Account B with Aurora Replicas. Enable Aurora Auto Scaling for the replicas to handle read scaling. Encrypt the database cluster at rest using an AWS KMS Customer Managed Key (CMK) created in Account A and shared with Account B via key policy.Cevap
- BDeploy an Amazon RDS for PostgreSQL database instance with a Multi-AZ standby deployment in Account B. Direct the read traffic to the standby instance during peak traffic hours to scale read operations. Encrypt the database instance at rest using an AWS KMS Customer Managed Key (CMK) created in Account A and shared with Account B.
- CDeploy an Amazon Aurora PostgreSQL database cluster in Account B with Aurora Replicas. Encrypt the database cluster at rest using the default AWS managed key for Amazon RDS (aws/rds). Configure IAM permissions to allow the security team in Account A to manage and audit the encryption key.
- DDeploy a single-AZ Amazon RDS for PostgreSQL database instance in Account B. Configure automated daily backups and copy them to a secondary Availability Zone. In the event of an Availability Zone outage, restore the database from the copied snapshot in the secondary zone.
Cevap
Deploying an Amazon Aurora PostgreSQL database cluster in Account B with Aurora Replicas and scaling them using Aurora Auto Scaling, encrypted with a cross-account Customer Managed Key (CMK) from Account A.
The correct option meets all requirements. Amazon Aurora PostgreSQL supports synchronous replication within its storage volume across multiple Availability Zones, ensuring an RPO of 0. Aurora's failover mechanism promotes a replica to primary in less than 30 seconds, meeting the RTO requirement. Aurora Replicas can serve read queries and support auto-scaling to handle high read volumes. By using an AWS KMS Customer Managed Key (CMK) in Account A, the key policy can be modified to grant the database in Account B permissions to use the key, while keeping key management and auditing under the control of Account A.
Adım Adım Çözüm
Anahtar Kavram
Designing database and storage solutions to meet replication, scale, and security requirements by choosing between Aurora and RDS, managing read capacity, and implementing cross-account AWS KMS encryption.