Which process should the Database Specialist recommend to meet these requirements?
Organize common and environmental-specific parameters hierarchically in the AWS Systems Manager Parameter Store, then reference the parameters dynamically from an AWS CloudFormation template. Deploy the CloudFormation stack using the environment name as a parameter.
Create a parameterized AWS CloudFormation template that builds the required objects. Keep separate environment parameter files in separate Amazon S3 buckets. Provide an AWS CLI command that deploys the CloudFormation stack directly referencing the appropriate parameter bucket.
Create a parameterized AWS CloudFormation template that builds the required objects. Import the template into the CloudFormation interface in the AWS Management Console. Make the required changes to the parameters and deploy the CloudFormation stack.
Create an AWS Lambda function that builds the required objects using an AWS SDK. Set the required parameter values in a test event in the Lambda console for each environment that the Application team can modify, as needed. Deploy the infrastructure by triggering the test event in the console.
Explanations:
This option uses AWS Systems Manager Parameter Store to organize parameters hierarchically, allowing for dynamic referencing within the AWS CloudFormation template. This enables the Application team to maintain separate environment settings efficiently while standardizing the core infrastructure. The deployment using environment names as parameters minimizes configuration errors and rework.
Although this option mentions creating a parameterized AWS CloudFormation template, storing environment parameter files in separate Amazon S3 buckets adds unnecessary complexity. The AWS CLI command referencing S3 buckets directly could lead to issues with parameter management and environment differentiation, increasing the chance of configuration errors.
This option requires manual intervention to import the parameterized AWS CloudFormation template through the AWS Management Console and make changes before deployment. This process can lead to inconsistencies and human errors, as it does not provide a standardized, automated way to manage environment-specific settings effectively.
Using an AWS Lambda function to build the required objects is less standard compared to CloudFormation. The dependency on test events and manual modifications in the console for each environment complicates the deployment process and increases the likelihood of errors. This approach lacks the standardization and separation of environment settings that the Application team desires.
I rank that the answer is:
Organize common and environmental-specific parameters hierarchically in the AWS Systems Manager Parameter Store, then reference the parameters dynamically from an AWS CloudFormation template. Deploy the CloudFormation stack using the environment name as a parameter.