Topic: AWS Certified SysOps Administrator - Associate topic 1 question 27

A SysOps administrator is using AWS CloudFormation StackSets to create AWS resources in two AWS Regions in the same AWS account. A stack operation fails in one Region and returns the stack instance status of OUTDATED.
What is the cause of this failure?

A.
The CloudFormation template changed on the local disk and has not been submitted to CloudFormation.
B.
The CloudFormation template is trying to create a global resource that is not unique.
C.
The stack has not yet been deployed to the Region.
D.
The SysOps administrator is using an old version of the CloudFormation API.

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

B as this is listed in https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacksets-troubleshooting.html

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

agree with haxaffee,
Common reasons for stack operation failure
Problem: A stack operation failed, and the stack instance status is OUTDATED.
Cause: There can be several common causes for stack operation failure.
The template could be trying to create global resources that must be unique but aren't, such as S3 buckets.

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

not sure what this means : "reate global resources that must be unique but aren't"

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

if Cloudformation want´s to create a new S3 Bucket with a name but this name is always in use by another S3 Bucket. Bucket Names must be unique globaly.

  • tgv
  • New member
  • Offline

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

This can happen if CloudFormation tries to create a resource that already exists.

  • tamng
  • New member
  • Offline

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

B. The CloudFormation template is trying to create a global resource that is not unique.

Re: AWS Certified SysOps Administrator - Associate topic 1 question 27

B

Cause: There can be several common causes for stack operation failure.

Insufficient permissions in a target account for creating resources that are specified in your template.

The AWS CloudFormation template might have errors. Validate the template in AWS CloudFormation and fix errors before trying to create your stack set.

The template could be trying to create global resources that must be unique but aren't, such as S3 buckets.

A specified target account number doesn't exist. Check the target account numbers that you specified on the Set deployment options page of the wizard.

The administrator account does not have a trust relationship with the target account.

The maximum number of a resource that is specified in your template already exists in your target account. For example, you might have reached the limit of allowed IAM roles in a target account, but the template creates more IAM roles.

You have reached the maximum number of stacks that are allowed in a stack set. See AWS CloudFormation limits for the maximum number of stacks per stack set.