Vpc Peering Reference Security Group

Support for security group references in a peered vpc simplifies configuration by controlling peering traffic via security group membership instead of cidr ranges.

Vpc peering reference security group. When a security group rule becomes stale it s not automatically removed from your security group you must manually remove it. For more information see reference peered vpc security groups. You can delete stale security group rules as you would any other security group rule.

Vpc peering can be used to create secure connectivity and resource sharing between two vpcs. As an added security feature aws is pleased to announce that users may now reference security groups of their choice in a peered virtual private cloud vpc. Setup vpc peering connection.

The peering connection should be in the active state. You cannot reference the security group of a peer vpc that s in a different region. A stale security group rule is a rule that references a security group in a peer vpc where the vpc peering connection has been deleted or the security group in the peer vpc has been deleted.

I setup a vpc peering connection between two regions us west 2 eu central 1 in a single aws account. In the documentation i see. Security group rule can reference security groups in peered vpcs if these following conditions are met.

You can reference security group from a peered vpc using the aws management console aws cli through sdks. Read the next post in this series where i ve looked at aws s identity access manager service iam and how to create and manage users groups and roles as well as mfa multi factor authentication. To reference a security group in another aws account include the account number in source or destination field.

You may start. If the peered vpc is in another account then the reference should include the account number as a prefix. The peer vpc can be a vpc in your account or a vpc in another aws account.