A CloudFormation template deploys an encrypted Amazon Machine Image (AMI). The AMI was copied into another AWS account so the template can be used there, but when creating the stack in the target account the deployment fails. What should the SysOps administrator do to fix the problem?

When an AMI is copied to a different AWS account, it receives a new, unique AMI ID in the destination account. The CloudFormation template, however, still references the original AMI ID from the source account. To resolve the deployment failure, the SysOps administrator must update the CloudFormation template to use the new AMI ID that was assigned to the copied AMI in the target account. Modifying AMI permissions to public is unnecessary and a security risk; the issue is the AMI ID, not its accessibility. Deregistering the original AMI in the source account would not affect the copied AMI in the destination account. Re-encrypting the copied AMI with a destination account KMS key might be necessary if the original encryption key wasn't shared, but the primary and immediate cause of the deployment failure is the incorrect AMI ID in the template.