A Virtual Network represents a Virtual Private Cloud (VPC). A VPC is your piece of the cloud and allows you to declare the range of IP addresses that will hold your cloud resources.
You control access to your resources by hosting them in the VPC's public or private subnets. A public subnet has access to the internet while a private subnet does not. A private subnet can allow SSH or internet access by configuring a NAT Gateway, NAT Instance, or Bastion.
When deploying a Virtual Network to an AWS Account using Stackery, the type of VPC being created is a Custom (non-default) VPC. By default, the Virtual Network resource in your
template.yaml file is set up with 4 Subnets (2 public, 2 private). Specify configurations for your VPC can be performed by working with the
template.yaml file directly.
VPC Built with Stackery
A VPC configured with a default IP Range of
10.0.0.0/16 will consist of the following
- 2 Public Subnets
- 1 NAT Gateway inside each Public Subnet (2 total)
- 1 Shared Route Table associated with the Public Subnets
- 2 Private Subnets
- 1 Route Table associated with each Private Subnet (2 total)
- 1 Main Route Table (not associated to any subnets by default)
- 1 Internet Gateway (IGW)
Human readable name for this resource that is displayed on the Stackery Dashboard and Stackery CLI output.
The range of IP addresses that resources may be assigned. The range is specified using CIDR notation.
Use Existing VPC
When enabled, this feature provides you with a field to specify an existing Virtual Private Cloud and it's public and private subnets for your application to reference.
When connected by a reference wire (dotted wire), a Function or Docker Task will add the following IAM policy to its role and gain permission to access this resource.
No Permissions Added
When connected by a reference wire (dotted wire), a Function or Docker Task will automatically populate and reference the following environment variables in order to interact with this resource.
No Environment Variables Added.
Related AWS Documentation
AWS Documentation: AWS::EC2::VPC