1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Such a problem may happen when your AWS::RDS::DBSecurityGroup resource is incorrectly defined: are you are specifying both EC2SecurityGroupName and EC2SecurityGroupId for an ingress / egress rule ?
If yes, you will encounter this problem: specify just one of them
Best,
Didier
Relevant content
- Accepted Answerasked 7 months ago
- asked a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 4 years ago