Explanation:
The correct answer is B. The issue arises because the custom AMI ID used in the us-east-1 region does not exist in the us-west-1 region. To resolve this with the least amount of operational overhead, the most efficient approach is to copy the custom AMI from us-east-1 to us-west-1. After copying the AMI, update the AWS CloudFormation template for the us-west-1 region to reference the new AMI ID and then relaunch the stack. This ensures consistency between both regions and leverages the existing custom AMI.
Ultimate access to all questions.
No comments yet.
A company's web application, deployed on Amazon EC2 using a custom AMI and AWS CloudFormation, operates in the us-east-1 Region. The company faces an error indicating a non-existent AMI ID when attempting to replicate the deployment in the us-west-1 Region. What is the most operationally efficient solution to resolve this error?
A
Modify both regional AWS CloudFormation templates to utilize an AWS-provided AMI and redeploy the stacks.
B
Replicate the custom AMI to us-west-1, update the us-west-1 CloudFormation template with the new AMI ID, and redeploy the stack.
C
Construct a new custom AMI in us-west-1 and generate a corresponding CloudFormation template for deployment in that region.
D
Deploy the application in us-west-1 manually, bypassing AWS CloudFormation.