To create private and non-private subnets in AWS CloudFormation, you should use the AWS CloudFormation Template Language (CFT) to outline your community configuration. Right here’s an instance CloudFormation template that demonstrates find out how to create private and non-private subnets inside a Digital Non-public Cloud (VPC) in AWS:
Sources:
MyVPC:
Kind: AWS::EC2::VPC
Properties:
CidrBlock: 10.0.0.0/16
Tags:
- Key: Identify
Worth: my-vpc
PublicSubnet:
Kind: AWS::EC2::Subnet
Properties:
VpcId: !Ref MyVPC
CidrBlock: 10.0.0.0/24
AvailabilityZone: us-west-2a
Tags:
- Key: Identify
Worth: public-subnet
PrivateSubnet:
Kind: AWS::EC2::Subnet
Properties:
VpcId: !Ref MyVPC
CidrBlock: 10.0.1.0/24
AvailabilityZone: us-west-2b
Tags:
- Key: Identify
Worth: private-subnet
On this instance, the AWS::EC2::VPC useful resource creates a VPC with the desired CIDR block. The AWS::EC2::Subnet sources create the private and non-private subnets inside the VPC, utilizing totally different CIDR blocks and availability zones.
It can save you this CloudFormation template in a file with a .yaml or .yml extension. Then, you should use the AWS Administration Console, AWS CLI, or AWS SDKs to create a CloudFormation stack from the template. The stack creation course of will provision the VPC and subnets based on the template.
Be sure you have the required permissions to create VPCs and subnets in your AWS account. You should use the AWS Administration Console’s CloudFormation service or the AWS CLI command aws cloudformation create-stack to create the stack from the template.
This instance assumes you’ve already configured the AWS CLI with applicable credentials and the required permissions for creating VPCs and subnets.
