Capabilities of VPC Sharing


VPC Sharing using the AWS Resource Access Manager
1m 25s
Start course

In this course, we look at the benefits of sharing a Virtual Private Cloud, a VPC, from a centralized networking AWS account using AWS Resource Access Manager (RAM). We discuss the capabilities of VPC sharing and the role RAM plays in VPC sharing.

Learning Objectives

By the end of this course, you will have a greater understanding of:

  • The benefits of sharing VPCs
  • The role of RAM in sharing VPCs
  • The capabilities and restrictions of VPC sharing

Intended Audience

Anyone working with AWS Networking will benefit from this course, as well as those who are:

  • Studying for the AWS Networking Specialty certification
  • Studying for the AWS Solutions Architect certifications

If you want to increase your AWS knowledge, this course is for you.


Before attending this course, you should be familiar with Amazon VPCs and how they are configured. Experience with AWS Organizations and how they are used to manage multiple AWS Accounts is also desirable.


In this section, we will discuss some of the capabilities of VPC sharing. When working with VPC sharing, we have to be aware of the following limitations. The VPC owner can only share VPCs with other AWS accounts in their own organization. The default VPC in each region cannot be shared. VPC sharing participants cannot launch resources using the default VPC security group or security groups created by other participants. They must use their own security groups. 

VPC sharing participants can create application load balancers and network load balancers, and can register targets they deployed to their shared subnets. Only the VPC owner can deploy gateway load balancers to shared subnets. When working with VPC sharing, each participant pays for the resources that they deploy. For example, if they deploy EC2 Instances, RDS databases, or Redshift clusters, then they would expect to see these resources on their bill at the end of the month. VPC sharing participants are also charged for their Inter-Availability Zone data transfer, VPC peering data transfer, and data transfer over AWS direct connect gateways. This is not a complete list. 

You must consult the AWS documentation for a complete list of charges that you might incur when a VPC is shared with your AWS account and you deploy resources to it. The owner of VPC might incur charges for NAT Gateway data processing and data transfer, data transfer costs for Virtual private gateways and Transit gateways, and data transfer costs associated with VPC Endpoints and Endpoint services. The VPC owner can unshare a subnet at any time. If this happens, VPC participants will not be able to create new resources in the subnet, existing deployed resources will continue to run. VPC participants can still modify, view, and delete their deployed resources, and the VPC owner will not be able to delete the unshared subnet or the shared subnets VPC until the VPC participant deletes all their deployed resources.


About the Author

Mike has worked in IT since 1997, specializing in networking, storage, and architecture. He's been in cloud computing for the last 8 years, working across several cloud platforms but specializing in AWS. He's been involved in many cloud projects over the years covering migrations, hybrid connectivity, security optimization, networking, and storage architecture.

He gained his first training qualification in 1998 and, about 3 years ago, became an AWS Authorized Champion Instructor. He's delivered AWS cloud courses across Europe for a range of clients, with a focus on Architecture, Security, and Networking. He currently holds certifications for the four biggest cloud vendors, including the AWS Solutions Architect Professional, AWS DevOps Engineer, and AWS Advanced Networking specialty certifications.

He lives in the North of England with his wife Frances and their dog Inca.