AWS VPC Peering the way it should be done

Standard VPC peering mechanism from AWS has some limitations. IT Svit has developed a solution to make the AWS VPC peering request handling a simple and easy task.
There is a detailed description of the VPC peering mechanism available on the AWS website. What it does not mention outright is that the connection is instantaneous and should be approved at once after issuing, because the request will disappear from the list shortly afterward. The other limitation is that peering is possible only within the subnets of one VPC.

VPC Peering solution from IT Svit

We used two Terraform manifests that can work in two modes:

1. If the user has admin rights for both VPCs, the process is essentially identical to the AWS functionality, with the exception that our solution allows creating a transparent roaming between the subnets of VPC from different accounts.
2. If the user does not have sufficient admin rights, the system creates a pending request that remains in the requests list until the admin of the requester VPC approves or cancels it.

Thus said, using our two Terraform manifests allows turning a somewhat cumbersome VPC peering procedure into a simple and convenient workflow. Feel free to get the code from our DevOps solution and use it to streamline your AWS VPC peering handling. Don’t forget to share the news with your colleagues and stay put, as there are more great DevOps tools from IT Svit coming soon!