A company's disaster recovery plan requires launching its hardened web server image in a second Region within minutes of a decision to fail over. The AMI currently exists only in us-east-1, and the DR Region's launch template is still empty. What should a CloudOps engineer do now to meet the plan?
Choose one.
AMIs are Regional resources: to launch an image in another Region you copy it there, which creates a new AMI with a new ID.
An AMI and its snapshots live in one Region, so launching the same image elsewhere needs a copy there, and the copy gets a new AMI ID. Because a copy moves all the snapshot data and can take a long time, it must be done ahead of a failover, not at the moment of it. A foreign AMI ID does not resolve in another Region, and copied snapshots are not a launchable image until an AMI is registered from them.
- Recognise that AMI IDs are scoped to a single Region.
- Note the time constraint: a copy is not instant, so it must exist before failover.
- Copy the AMI into the DR Region now (CopyImage, or an EC2 Image Builder distribution setting for every new build).
- Reference the new Regional AMI ID in the DR launch template and re-copy whenever the golden image changes.
Exam tip: One AMI, one Region - copy it to every Region that must launch it.
CloudFormation, StackSets, and golden images: provisioning for SOA-C03 — the lesson that teaches this.