Service Catalog Provisioning Through Cloud Formation Template issue
Hello Everyone,
I am provisioning Service Catalog Products from cloud formation template using AWS::ServiceCatalog::CloudFormationProvisionedProduct
All of of the products are getting provisioned, but one of them is giving Resource handler returned message: "Invalid request provided: AWS::ServiceCatalog::CloudFormationProvisionedProduct".
This behavior is observed sometimes where the Cloud formation provision fails. The same CFT has been provisioned successfully in production as well, this issue is randomly occurring.
- 최신
- 최다 투표
- 가장 많은 댓글
The error was provisioned product name for one of the product was identical. Cloud formation has given the error Invalid request provided: AWS::ServiceCatalog::CloudFormationProvisionedProduct
This issue may be due to
- Limitations on the number of resources that can be created in a single stack
- Duplicate/identical resource names or resource conflicts
Perform the following checks below
- Review the AWS Service Limits : If the stack creation failed due to limitations on the number of resources that can be created in a single stack, the next step is to review the AWS service limits. You can do this by navigating to the AWS service documentation and checking the limits for the specific service that you are trying to create resources for.
- Check for Duplicate Resource Names or Conflicts : If the stack creation failed due to duplicate resource names or resource conflicts, the next step is to review the CloudFormation template and ensure that all resource names are unique. You can also check for any resource conflicts that may be preventing the creation of the stack.
- Verify Resource Dependencies : If the stack creation failed due to dependencies between resources that are not defined in the CloudFormation template, the next step is to review the template and ensure that all dependencies are defined. You can do this by checking the resource dependencies in the template or by reviewing the AWS documentation for the specific service.
[Reference]
관련 콘텐츠
AWS 공식업데이트됨 일 년 전
In all the above mentioned instances, the stack will never get created, But in our case we have the stack created successfully in multiple instances. This error starting occurring recently with no template change. My Cloud formation hardly have 50 resources defined for provisioning various products and there are no duplicate Logical Ids or dependencies.