Optional ReadonlyegressOutbound traffic rules added to the existing security group. Supports ipv4 CIDR, prefix list, and security group destinations.
Use cases: Allowing this group to reach an externally-owned peer group
AWS: EC2 SecurityGroupEgress
Validation: Optional; valid MdaaSecurityGroupRuleProps
Optional ReadonlyingressInbound traffic rules added to the existing security group. Supports ipv4 CIDR, prefix list, and security group sources.
Use cases: Allowing an externally-owned peer group to reach this group
AWS: EC2 SecurityGroupIngress
Validation: Optional; valid MdaaSecurityGroupRuleProps
ReadonlysecurityId of the existing security group to which the rules will be added.
Use cases: Cross-module security group wiring; Connectivity to externally-owned groups
AWS: EC2 SecurityGroupIngress/SecurityGroupEgress GroupId
Validation: Required; existing security group id (supports ssm: references)
Ingress/egress rules added to a security group that already exists (created by another module). Unlike securityGroups, this does not create a security group; it only authorizes additional rules on an existing one referenced by id. This is the declarative way to wire connectivity between two security groups owned by different modules without creating a circular cross-stack dependency, since each rule references the peer group only by id.