Which solution will meet these requirements in the MOST operationally efficient way?
Create RDS resources by using AWS CloudFormation. Share the CloudFormation template with each account.
Create an RDS snapshot. Share the snapshot with each account. Deploy the snapshot into each account.
Use AWS CloudFormation to create RDS instances in each account. Run AWS Database Migration Service (AWS DMS) replication to each of the created instances.
Create a script by using the AWS CLI to copy the RDS instance into the other accounts from a template account.
Explanations:
Using AWS CloudFormation to create RDS resources allows for an automated, repeatable solution, and sharing the CloudFormation template enables each account to deploy compliant RDS instances with ease. This method ensures efficiency and consistency across all accounts.
Creating and sharing an RDS snapshot is inefficient here, as the company needs new RDS instances, not copies of existing data. This method also does not provide the ability to enforce compliance parameters during instance creation.
AWS DMS replication is unnecessary in this scenario, as data replication is not required. This method is overly complex and operationally inefficient for simply creating RDS instances with specific compliance parameters in each account.
Using a script with AWS CLI to copy an RDS instance from a template account is inefficient and complex to manage across more than 100 accounts. It also lacks CloudFormation’s inherent compliance controls and parameter enforcement.
As I recall, the answer is:
Create RDS resources by using AWS CloudFormation. Share the CloudFormation template with each account.
I categorize that the answer is:
Create RDS resources by using AWS CloudFormation. Share the CloudFormation template with each account.