Vpc Peering Best Practices
Dudicoco opened this issue jun 14 2020 1 comment labels.
Vpc peering best practices. Best practices for vpc in mixed chassis mode m1 f1 ports in same system or vdc best practices for attaching a device to vpc domain best practices for data center interconnect and encryption best practices for spanning tree protocol interoperability best practices for layer 3 and vpc best practices for hsrp vrrp and vpc. Create a vpc network for each autonomous team with shared services in a common vpc network. A key quality of vpc peering connections is that they are neither a vpn connection nor a gateway and thus does not depend on any physical hardware.
Create a single vpc network per project to map vpc network quotas to projects. During the design phase decide which switch should be the primary. This makes the state primary secondary predictable which makes troubleshooting easier.
Instead aws uses the current infrastructure of a vpc for creating a vpc peering connection. Vpc peering connectivity allows you to connect two amazon vpcs and which would then allow you to route traffic between them with the aid of private ip addresses. Ensure that the amazon vpc peering connection configuration is compliant with the desired routing policy.
Ensure that amazon network acl deny rules are effective within the vpc configuration. If you create a vpc with a 24 cidr block which has 256 addresses you can t put more than 256 resources into that vpc. We recommend that you use tags.
The very first amazon vpc best practice is to organize your aws environment. The following best practices are general guidelines and don t represent a complete security solution. Best practices for vpc peering 1218.
In any diagrams depict the left switch as the primary and the right as the secondary. And the simple use of tags will make life so much easier when it comes to troubleshooting. Because these best practices might not be appropriate or sufficient for your environment treat them as helpful considerations rather than prescriptions.