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.