# Application Account \$1 Create VPC Additional CIDR and Subnets
Create an additional VPC CIDR, or subnets, or both, for an existing application account VPC. Add up to five public and twenty private subnet tiers to the additional CIDR, or to existing CIDRs under the VPC. A subnet tier is a set of subnets provisioned in two or three Availability Zones (AZ).
**Full classification:** Deployment \$1 Managed landing zone \$1 Application account \$1 Create VPC Additional CIDR and Subnets
## Change Type Details
****
| | |
| --- |--- |
| Change type ID | ct-2ha68tpd7nr3y |
| Current version | 1.0 |
| Expected execution duration | 360 minutes |
| AWS approval | Required |
| Customer approval | Not required |
| Execution mode | Automated |
## Additional Information
### Create VPC CIDRs and subnets
#### Application account: creating VPC CIDRs or Subnets with the Console
Screenshot of this change type in the AMS console:
![\[Form for creating additional VPC CIDR or subnets for an application account VPC.\]](http://docs.aws.amazon.com/managedservices/latest/ctref/images/guiMalzAppAcctCreateVpcCidrSubnetsCT.png)
How it works:
1. Navigate to the **Create RFC** page: In the left navigation pane of the AMS console click **RFCs** to open the RFCs list page, and then click **Create RFC**.
1. Choose a popular change type (CT) in the default **Browse change types** view, or select a CT in the **Choose by category** view.
+ **Browse by change type**: You can click on a popular CT in the **Quick create** area to immediately open the **Run RFC** page. Note that you cannot choose an older CT version with quick create.
To sort CTs, use the **All change types** area in either the **Card** or **Table** view. In either view, select a CT and then click **Create RFC** to open the **Run RFC** page. If applicable, a **Create with older version** option appears next to the **Create RFC** button.
+ **Choose by category**: Select a category, subcategory, item, and operation and the CT details box opens with an option to **Create with older version** if applicable. Click **Create RFC** to open the **Run RFC** page.
1. On the **Run RFC** page, open the CT name area to see the CT details box. A **Subject** is required (this is filled in for you if you choose your CT in the **Browse change types** view). Open the **Additional configuration** area to add information about the RFC.
In the **Execution configuration** area, use available drop-down lists or enter values for the required parameters. To configure optional execution parameters, open the **Additional configuration** area.
1. When finished, click **Run**. If there are no errors, the **RFC successfully created** page displays with the submitted RFC details, and the initial **Run output**.
1. Open the **Run parameters** area to see the configurations you submitted. Refresh the page to update the RFC execution status. Optionally, cancel the RFC or create a copy of it with the options at the top of the page.
#### Application account: creating VPC CIDRs or Subnets with the CLI
How it works:
1. Use either the Inline Create (you issue a `create-rfc` command with all RFC and execution parameters included), or Template Create (you create two JSON files, one for the RFC parameters and one for the execution parameters) and issue the `create-rfc` command with the two files as input. Both methods are described here.
1. Submit the RFC: `aws amscm submit-rfc --rfc-id ID` command with the returned RFC ID.
Monitor the RFC: `aws amscm get-rfc --rfc-id ID` command.
To check the change type version, use this command:
```
aws amscm list-change-type-version-summaries --filter Attribute=ChangeTypeId,Value=CT_ID
```
**Note**
You can use any `CreateRfc` parameters with any RFC whether or not they are part of the schema for the change type. For example, to get notifications when the RFC status changes, add this line, `--notification "{\"Email\": {\"EmailRecipients\" : [\"email@example.com\"]}}"` to the RFC parameters part of the request (not the execution parameters). For a list of all CreateRfc parameters, see the [AMS Change Management API Reference](https://docs.aws.amazon.com/managedservices/latest/ApiReference-cm/API_CreateRfc.html).
*INLINE CREATE*:
**Note**
Run this change type from your Application account.
Issue the create RFC command with execution parameters provided inline (escape quotes when providing execution parameters inline), and then submit the returned RFC ID. For example, you can replace the contents with something like this:
To create only additional VPC CIDRs:
```
aws amscm create-rfc --change-type-id "ct-2ha68tpd7nr3y" --change-type-version "1.0" --title "Additional VPC CIDR Creation" --execution-parameters "{\"VPCId\": \"VPC_ID\", \"Parameters\": { \"VPCCIDR\": \"X.X.X.X/X\"}}"
```
To create only additional subnets:
```
aws amscm create-rfc --change-type-id "ct-2ha68tpd7nr3y" --change-type-version "1.0" --title "Additional VPC Subnet Creation" --execution-parameters "{\"VPCId\": \"VPC_ID\", \"Parameters\": {\"PrivateRouteTableAZ1ID\": \"Transit Gateway Route Table AZ1 Name\", \"PrivateRouteTableAZ2ID\": \"Transit Gateway Route Table AZ2 Name\", \"PrivateSubnet1AZ1CIDR\": \"X.X.X.X/X\",\"PrivateSubnet1AZ2CIDR\": \"X.X.X.X/X\"}}"
```
To create additional VPC CIDR and subnets:
```
aws amscm create-rfc --change-type-id "ct-2ha68tpd7nr3y" --change-type-version "1.0" --title "Additional VPC CIDR and subnet Creation" --execution-parameters "{\"VPCId\": \"VPC_ID\", \"Parameters\": { \"VPCCIDR\": \"X.X.X.X/X\", \"PrivateRouteTableAZ1ID\": \"Transit Gateway Route Table AZ1 Name\", \"PrivateRouteTableAZ2ID\": \"Transit Gateway Route Table AZ2 Name\", \"PrivateSubnet1AZ1CIDR\": \"X.X.X.X/X\",\"PrivateSubnet1AZ2CIDR\": \"X.X.X.X/X\"}}"
```
*TEMPLATE CREATE*:
1. Output the execution parameters JSON schema for this change type to a file; this example names it CreateAppAcctVpcCidrSubnetParams.json:
```
aws amscm get-change-type-version --change-type-id "ct-2ha68tpd7nr3y" --query "ChangeTypeVersion.ExecutionInputSchema" --output text > CreateAppAcctVpcCidrSubnetParams.json
```
1. Modify and save the CreateAppAcctVpcCidrSubnetParams file. For example, you can replace the contents with something like this:
To create only additional VPC CIDRs:
```
{
{
"VPCId": "VPC_ID",
"Parameters": {
"VPCCIDR": "x.x.x.x/x",
}
}
}
```
To create only additional subnets:
```
{
"VPCId": "VPC_ID",
"Parameters": {
"PrivateRouteTableAZ1ID": "Transit Gateway Route Table AZ1 Name",
"PrivateRouteTableAZ2ID": "Transit Gateway Route Table AZ2 Name",
"PrivateSubnet1AZ1CIDR": "x.x.x.x/x",
"PrivateSubnet1AZ2CIDR": "x.x.x.x/x"
}
}
```
To create additional VPC CIDR and subnets:
```
{
"VPCId": "VPC_ID",
"Parameters": {
"VPCCIDR": "x.x.x.x/x",
"PrivateRouteTableAZ1ID": "Transit Gateway Route Table AZ1 Name",
"PrivateRouteTableAZ2ID": "Transit Gateway Route Table AZ2 Name",
"PrivateSubnet1AZ1CIDR": "x.x.x.x/x",
"PrivateSubnet1AZ2CIDR": "x.x.x.x/x"
}
}
```
1. Output the RFC template JSON file to a file; this example names it CreateAppAcctVpcCidrSubnetRfc.json:
```
aws amscm create-rfc --generate-cli-skeleton > CreateAppAcctVpcCidrSubnetRfc.json
```
1. Modify and save the CreateAppAcctVpcCidrSubnetRfc.json file. For example, you can replace the contents with something like this:
```
{
"ChangeTypeVersion": "1.0",
"ChangeTypeId": "ct-2ha68tpd7nr3y",
"Title": "App-Acct-Vpc-Cidr-Subnets-RFC"
}
```
1. Create the RFC, specifying the CreateAppAcctVpcCidrSubnetRfc file and the CreateAppAcctVpcCidrSubnetParams file:
```
aws amscm create-rfc --cli-input-json file://CreateAppAcctVpcCidrSubnetRfc.json --execution-parameters file://CreateAppAcctVpcCidrSubnetParams.json
```
You receive the ID of the new RFC in the response and can use it to submit and monitor the RFC. Until you submit it, the RFC remains in the editing state and does not start.
#### Tips
+
**Important**
To create an additional public subnet in a new availability zone (AZ), a private subnet must already be present.
+ To use this CT to create additional public subnets in an already-provisioned VPC, the VPC must already have public subnets inside it. If this is not the case, contact AMS to deploy those public subnets inside the VPC first.
+ To learn more about AMS multi-account landing zone, see [ VPC sharing: A new approach to multiple accounts and VPC management](https://aws.amazon.com/blogs/networking-and-content-delivery/vpc-sharing-a-new-approach-to-multiple-accounts-and-vpc-management/).
## Execution Input Parameters
For detailed information about the execution input parameters, see [Schema for Change Type ct-2ha68tpd7nr3y](schemas.md#ct-2ha68tpd7nr3y-schema-section).
## Example: Required Parameters
```
Example not available.
```
## Example: All Parameters
```
Example not available.
```