2 Answers
- Newest
- Most votes
- Most comments
0
- Identify and review the duplicate rule in the security group.
- Check and update the Lambda function handling the Custom::VpcRestrictDefaultSG.
- Verify the CloudFormation template for any misconfigurations or duplicates.
- Retry updating your stack after making the necessary changes.
0
Hello, The error indicates that the security group rule you're trying to add already exists. To resolve this, first identify the security group and remove the conflicting rule, then update the CloudFormation stack with the modified template.
**Refer this article: **
- When you create a resource that has the same name and is set to the same value as another resource, AWS CloudFormation can't differentiate between them. You then receive the error message, "Resource already exists in stack." Each resource has a unique physical ID. You can't reuse the physical ID for most resources that are defined in CloudFormation.
[+] https://repost.aws/knowledge-center/cloudformation-stack-resource-failure
answered a month ago
Relevant content
- asked 3 months ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago