Terraform aws provider multiple profiles

This relationship is required since I am using AWS-roles to apply the configuration changes across accounts. (a) both the VPCs exist, (b) do not have a CIDR block overlap, and (c) there is a trust relationship between the user account I am using in the trusted-account and the roles in the trusting-account.

VPC peering would be possible only if the CIDR blocks have no overlap.Д«efore I go into explaining the code, there are three prerequisites to enable vpc-peering:

Hence, I allocated separate CIDR blocks to both the VPCs with no overlap. While creating these separate VPCs in these individual AWS accounts, I was aware that I would have to create a peering relationship between the two later down the line. Here is the link to VPC Peering at AWS Docs. It is a relationship that allows two-way communication between components hosted in separate VPCs. I was working on a use case to create a bridge between two VPCs belonging to separate AWS accounts so that communication could take place. Per AWS, вЂњAmazon Virtual Private Cloud (Amazon VPC) is a service that lets you launch AWS resources in a logically isolated virtual network that you define.вЂќ Hence resources created inside a particular VPC cannot communicate with the outside world unless specified.

But before I do so, let me briefly give an overview of VPC peering and then walk through the process of creating one. This note captures my learning from that exercise. A few weeks ago, I created a peering relationship between two VPCs that belonged to separate AWS accounts using Terraform.

Terraform aws provider multiple profiles