note: VPCs (or more specifically a VPCs Subnets) can only be shared with AWS accounts in the same organization. To complete this lab use AWS Organizations. If you are given access by AWS at an AWS Event this is take care of for you.
Attaching VPCs in other Accounts is super useful and has its place. But many times, we don’t need things to be in separate networks, we just need to separate out who can manage the resources we put in the network. Customer’s in the past often created this isolation by using Resource Tags, IAM polices, and IAM roles. Many times, creating a new account and VPC just for this separation. Now with Resource Access Manager and the ability to share Subnets in a VPC, multiple accounts can place resources into the same VPC. Each account having the ability to define its own account limits, security policy, and IAM roles. It also makes the for a cleaner and easier to use network. To be clear, having multiple VPCs still has its place such as isolating security tiers, limiting audit scope, etc.) Lets take a look.
In the AWS Management Console change to the region you plan to work in and change. This is in the upper right-hand drop-down menu.
Lets determine the scope of the share. If you are pairing up with someone, choose Option 1 below, we will use their Account number. If you are working in your Organization, you can also use Option 2 and share with all of the account in your AWS organization.
In the AWS Management Console choose Services then select Resource Access Manager.
From the left-hand menu select Resource Shares (you may have to open the Burger menu). Click the Create a resource share button in the upper right of the main panel.
Fill out the Create Resource Share details: