Explanation:
To share an encrypted Amazon RDS snapshot across accounts, the snapshot must be shared along with access to the AWS KMS key used to encrypt it. By modifying the KMS key policy to grant access to the target (migration) account and sharing the snapshot, the migration account can copy or restore the snapshot. This approach requires the least administrative overhead compared to setting up read replicas across accounts or using native export/import tools.
Ultimate access to all questions.
A SysOps administrator wants to share a copy of a production database with a migration account. The production database is hosted on an Amazon RDS DB instance and is encrypted at rest with an AWS Key Management Service (AWS KMS) key that has an alias of production-rds-key. What must the SysOps administrator do to meet these requirements with the LEAST administrative overhead?
A
Take a snapshot of the RDS DB instance in the production account. Amend the KMS key policy of the production-rds-key KMS key to give access to the migration account's root user. Share the snapshot with the migration account.
B
Create an RDS read replica in the migration account. Configure the KMS key policy to replicate the production-rds-key KMS key to the migration account.
C
Take a snapshot of the RDS DB instance in the production account. Share the snapshot with the migration account. In the migration account, create a new KMS key that has an identical alias.
D
Use native database toolsets to export the RDS DB instance to Amazon S3. Create an S3 bucket and an S3 bucket policy for cross-account access between the production account and the migration account. Use native database toolsets to import the database from Amazon S3 to a new RDS DB instance.
No comments yet.