A developer is preparing to update an AWS CloudFormation stack that manages a production backend application. The update involves introducing a new external service API key that must be stored securely with support for automatic rotation. Additionally, the developer must ensure that any manual, out-of-band changes previously made to the stack's resources are identified and resolved before the update is performed to prevent deployment failures.
Which combination of actions should the developer take to meet these requirements? (Select TWO.)
- Store the API key in AWS Secrets Manager, and reference it in the CloudFormation template using a dynamic reference.Cevap
- Run drift detection on the CloudFormation stack, identify any drifted resources, and update the template or import resources to resolve the differences before updating the stack.Cevap
- CStore the API key in Systems Manager Parameter Store as a Standard parameter, and reference it in the CloudFormation template using a Systems Manager dynamic reference.
- DModify the drifted resources manually in the AWS Management Console to match the updated template configurations, then apply the stack update.
- EInitiate the stack update directly, and if a failure occurs, manually delete the resource that caused the rollback while the stack is in the ROLLBACK_IN_PROGRESS state.
Cevap
Storing the API key in AWS Secrets Manager and referencing it via a dynamic reference, and running drift detection to identify and resolve drifted resources before updating the stack.
Storing the API key in AWS Secrets Manager satisfies the requirements for secure storage and automatic rotation, and referencing it via a dynamic reference ensures security. Running drift detection identifies any out-of-band changes that would cause the stack update to fail, allowing the developer to synchronize the template and actual resource configurations before deploying the update.
Adım Adım Çözüm
Anahtar Kavram
CloudFormation update mechanics, drift detection, and secure parameter retrieval.