A CloudFormation create fails with a message that the named resource already exists. The same name works in a template in another account. Health Dashboard shows no Regional event. What is the failure?
Select an answer to reveal the explanation.
Short Explanation
Already exists means the name is taken in this account, not that the Region is down. You saw the same template succeed elsewhere, and Health Dashboard is quiet. You change the name or adopt the existing resource, and you do not wait out an outage that is not happening.
Full Explanation
CloudFormation reports that a resource already exists when the physical name is taken by something the stack does not own. That is a collision, and a quiet Health Dashboard plus success in another account fits a local name, not a Regional outage. Pick a new name or import the existing resource. An AMI id and a Route 53 failover do not rename resources during create or produce this message. Caveat: some names, such as S3 buckets, are global in the partition, so the collision might be outside the account; the error is still a taken name, not an outage. Operational check: find the existing resource with that name, then either import it or change the template and recreate. The status reason names the resource type and the physical name. Search this account for that name before you declare an outage. Health Dashboard being quiet supports a collision. Import the resource if the stack should own it, or change the name property if the existing one must stay independent. A retry with the same name fails again in seconds, which is not how a Regional outage behaves.