Skip to content

Cloudformation template error solely in my AWS account, not another account?

0

Hello, I am not sure what is going on but if I try to deploy a CF template specifically from here (https://catalog.workshops.aws/mpseller/en-US/saas/integration-with-quickstart), the 'Deploy, but don't update product' I always get an error, "The following resource(s) failed to create: [FulfillmentURL, EntitlementSQSHandlerMySQSEvent, SubscriptionSQSHandlerMySQSEvent]." Even though my AWS User account is a full admin with the administratoraccess permission set. I even tried creating a new IAM user with that permission set and with full access for the Marketplace. But I always get that same error and have to rollback.

My questions is why? I was working with a friend to do this and he screenshared his AWS account and he could run through the CF template with NO ERROR, even though he had the SAME PERMISSIONS. I am totally stumped.

2 Answers
0

Hello.

Why not check the details of the error by looking for the AWS resource creation event where the error occurred in the CloudTrail event history?
https://docs.aws.amazon.com/awscloudtrail/latest/userguide/view-cloudtrail-events-console.html

Also, are there any other error messages output in the CloudFormation event?

EXPERT

answered 2 years ago

  • Honestly there isn't anything more useful in the CloudTrail history. I am completely stumped. I was going to try and open a AWS Support ticket just to see if by chance they could dig around and see anything.

-1

The issue you're experiencing with the CloudFormation template deployment failing in your AWS account, while it works in your friend's account with the same permissions, could be due to several factors:

  1. Resource Limits: You might have reached the maximum number of certain resources in your account. For example, there could be limits on the number of IAM roles, SQS queues, or other resources that the template is trying to create.

  2. Existing Resources: The template might be attempting to create resources with names that already exist in your account. This is particularly relevant for global resources like S3 buckets that must have unique names across all AWS accounts.

  3. Regional Differences: If you and your friend are deploying in different AWS regions, there might be region-specific issues or limitations.

  4. Account-Specific Settings: Your account might have certain settings or restrictions that are preventing the creation of specific resources.

  5. Service Quotas: There could be service quotas in your account that are preventing the creation of certain resources.

To troubleshoot this issue:

  1. Check the CloudWatch Logs for more detailed error messages.
  2. Verify that you don't have existing resources with the same names as those being created by the template.
  3. Ensure that you haven't reached any service quotas or limits in your account.
  4. Try deploying the template in a different region to see if it's a region-specific issue.
  5. Double-check your IAM permissions to ensure you have all necessary permissions, including those for CloudFormation, SQS, and any other services used in the template.

If the issue persists, you may need to contact AWS support for further assistance, as there might be account-specific factors that are not immediately apparent.
Sources
Troubleshooting AWS CloudFormation StackSets - AWS CloudFormation
How CloudFormation works - AWS CloudFormation

answered 2 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.