You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you do not specify an egress rule, we add egress rules that allow IPv4 and IPv6 traffic on all ports and protocols to any destination.
We do not add these rules if you specify your own egress rules.
Deploying a security group with no egress rule with CloudFormation results with only one IPv4 egress rule:
Expected Behavior
I expect the default IPv6 egress rule to be present once CloudFormation has deployed a security group template with no egress.
Observed Behavior
See the screenshot in the issue description, no default IPv6 egress rule is deployed.
Test Cases
Here is a template extract of the failing security group:
Name of the resource
AWS::EC2::SecurityGroup
Resource Name
No response
Issue Description
While the AWS::EC2::SecurityGroup documentation says:
Deploying a security group with no egress rule with CloudFormation results with only one IPv4 egress rule:
Expected Behavior
I expect the default IPv6 egress rule to be present once CloudFormation has deployed a security group template with no egress.
Observed Behavior
See the screenshot in the issue description, no default IPv6 egress rule is deployed.
Test Cases
Here is a template extract of the failing security group:
Other Details
No response
The text was updated successfully, but these errors were encountered: