Create AWS Site with TGW

• Log into Console.

• Click Cloud and Edge Sites.

• Click Manage > Site Management > AWS TGW Sites.

• Click Add AWS TGW Site.

• In the Metadata section, enter a name for your TGW site object.

• In the AWS Configuration section, perform the following:

  • Click Configure.

  • From the AWS Region menu, select the region based on your AWS account.

Step 2.1: Configure services VPC.

• From the Select Services VPC menu, select an option and configure per the following guidelines:

  • For the New VPC Parameters option, select an option from the AWS VPC Name menu. The Autogenerate VPC Name option is selected by default. If you select the Choose VPC Name option, enter a VPC name in the Choose VPC Name field.

  • Enter the Classless Inter-Domain Routing (CIDR) block in the Primary IPv4 CIDR block field.

• For the Existing VPC option, enter an existing VPC name in the Existing VPC field. If you use this option, you are required to enable the enable_dns_hostnames field in the existing VPC configuration.

Step 2.2: Configure the TGW settings.

• In the Transit Gateway section, select an option from the Select Transit Gateway menu, and configure per the following guidelines:

  • For the New TGW Parameters option, select an option for the Select BGP ASN field. If you select Automatic, Distributed Cloud Services assign the ASNs for the TGW and site. For the User will assign ASN for TGW and Volterra Site option, enter the ASNs for Enter TGW ASN and Enter Volterra Site ASN fields. The supported ASN range is from 64513 to 65534.

  • For the Existing TGW option, enter the TGW ID in the Existing TGW ID field. Enter the ASNs for Enter TGW ASN and Enter Volterra Site ASN fields.

• In the VPC attachments section, click Configure.

• Click Add Item.

• Enter the VPC ID in the VPC ID field. Select labels from the Labels For VPC ID menu.

• Click Add Item.

• Click Apply.

Note: You can add multiple VPC attachments using the Add Item button. You can add VPC attachments during AWS TGW site creation, or you can edit an existing TGW site configuration to add VPC attachments.

• In the Network Configuration section, click Configure.

• Click Show Advanced Fields to enable the advanced options.

• From the Manage Static Routes for Inside Network menu, select Manage Static Routes and perform configuration per the following guidelines for the List of Static Routes field:

  • Click Add Item.

  • Select Simple Static Route and enter a static route in the Simple Static Route field. Or, select Custom Static Route and then click Configure and perform the following steps:

    • In the Subnets section, click Add Item and then select IPv4 or IPv6 from the Version menu. Enter a prefix and prefix length for your subnet. Click Add Item to set more subnets.

    • In the Nexthop section, select a next-hop type from the Type menu. Select IPv4 or IPv6 from the Version menu in the Address section, and enter an IP address accordingly.

    • From the Network Interface menu, select a network interface or click Create new network interface to create and apply a new network interface.

    • In the Static Route Labels section, select supported labels from the Static Route Labels menu. You can select more than one from this list.

    • In the Attributes section, select supported attributes from the Attributes menu. You can select more than one from this list.

    • Click Apply to add the custom route.

• Select Manage Static routes from the Manage Static Routes for Outside Network menu, and click Add Item for the Static route list field. Follow the same procedure as that of managing the static routes for inside network.

• Click Apply.

Note: You can use the Add Item button to add multiple inside and outside networks.

• Select Connect Global Networks from the Select Global Networks to Connect menu.

• Click Add Item.

• Select an option for the Select Network Connection Type menu.

• Select a global network object from the displayed list or select Create new global vn option from the Global Virtual Network menu. If you select Create new virtual network, the global network creation form opens. Create a global network using the guided form and click Continue to apply the network to the global network connection configuration.

• Click Apply to apply the TGW network configuration.

• In the Security Configuration section, click Configure.

• From the Manage Forward Proxy menu, select a forwarding policy:

  • Disable Forward Proxy: This is the default option and will not forward traffic.

  • Enable Forward Proxy with Allow All Policy: This option forwards all traffic.

  • Enable Forward Proxy and Manage Policies: This option forwards traffic based on the policy you select or specify. In the List of Forward proxy policy menu, select an existing proxy or select Create new forward proxy policy to create a new policy.

• From the Manage Network Policy menu, select Active Network Policies.

• Select an existing network policy or select Create new network policy view. After creating the policy, click Continue to apply.

• In the Manage East-West Service Policy section, select an existing policy from the Manage East-West Service Policy drop-down menu:

  • Disable East-West Service Policy: This is the default option and will not use a proxy for East-West traffic.

  • Enable East-West Service Policy: This option uses a proxy for East-West traffic. Click Add item to select an existing policy or select Create new service policy from the menu for a new policy.

  • Enable East-West traffic Proxy with Allow All Policy: This option sends all East-West traffic through a proxy for monitoring.

• Click Apply.

• In the Software Configuration section, click Show Advanced Fields.

• Enter the geographical address and/or latitude and longitude for the site location.

• In the Advanced Configuration section, click Show Advanced Fields.

• From the Logs Streaming menu, select Enable Logs Streaming and then select a log receiver or create a new log receiver.

• From the Select Volterra Software Version menu, select an option.

• From the Select Operating System Version menu, select an option.

• Optionally, add a site to site tunnel IP and additional AWS tags.

• Click Save and Exit to complete creating the AWS TGW site object.

The Status field for the AWS TGW object displays Generated.

Perform this procedure if you created the TGW object with the Automatic Deployment option.

• Navigate to the AWS TGW site object by clicking Manage > Site Management > AWS TGW Sites.

• Find your AWS TGW site object and click Apply under the Actions column. The Status field for your AWS TGW site object changes to Apply Planning.

Note: Optionally, you can perform terraform plan activity before deployment. Find your AWS TGW site object and click ... > Plan to start the action of terraform plan. This creates the execution plan for terraform.

• Wait for the apply process to complete and the status to change to Applied.

Note: You can check the status for the apply action. Click ... > Terraform Parameters for your AWS TGW site object and then click the Apply Status tab.

• Navigate to Sites > Sites List.

• Find your site from the displayed list and verify that the status is ONLINE. It may take a few minutes for the site to deploy and status to change to ONLINE.

Perform this procedure if you created the AWS TGW object with the Assisted Deployment option.

• Download the terraform variables for assisted deployment.

• Navigate to the created AWS VPC site object by clicking Manage > Site Management > AWS TGW Sites.

• Find your AWS TGW site object and click ... > Terraform Parameters for it.

• Copy the parameters to a file on your local machine.

• Download the volt-terraform container:

docker pull gcr.io/volterraio/volt-terraform

• Run the terraform container:

docker run --entrypoint tail --name terraform-cli -d -it \
-w /terraform/templates \
-v ${HOME}/.ssh:/root/.ssh \
gcr.io/volterraio/volt-terraform:latest \
-f /dev/null

• Copy the downloaded terraform variables file to the container. The following example copies to the /var/tmp folder on the container:

docker cp /Users/ted/Downloads/system-aws-tgw-a.json terraform-cli:/var/tmp

• Download the API certificate from Console and copy it to the container:

docker cp /Users/ted/Downloads/playground.console.api-creds.p12 terraform-cli:/var/tmp

Note: See the Generate API Certificate guide for information on API credentials.

• Enter the terraform container:

docker exec -it terraform-cli sh

• Configure AWS API access and secret key:

aws configure

Note: For more information, refer to AWS documentation.

• Change to the AWS TGW template directory:

cd /terraform/templates/views/assisted/aws-tgw-volt-node

• Set the environment variable needed for the Distributed Cloud Services provider:

  • VOLT_API_P12_FILE: This is for the path to API certificate file.

  • VES_P12_PASSWORD: This variable is for the API credentials password. This is the password which you set while downloading the API certificate.

  • VOLT_API_URL: This is for the tenant URL.

Change the values per your setup. See the following examples:

export VOLT_API_P12_FILE="/var/tmp/playground.console.api-creds.p12"
export VES_P12_PASSWORD=<api_cred_password>
export VOLT_API_URL="https://playground.console.ves.volterra.io/api"
export TF_VAR_akar_api_url=$VOLT_API_URL

• Deploy the nodes by executing the terraform commands:

terraform init
terraform apply -var-file=/var/tmp/system-aws-tgw-a.json

Note: The terraform init command downloads the terraform providers defined in the module. When the terraform apply command is executed, it prompts the user for input to proceed.

• Enter yes to begin deploying the node(s) and wait for the deployment to complete.

• Navigate to Sites > Sites List.

• Find your site from the displayed list and verify that the status is ONLINE. It may take a few minutes for the site to deploy and the status to change to ONLINE.

• Navigate to the AWS TGW site object by clicking Manage > Site Management > AWS TGW Sites.

• Find your AWS TGW site object and click ... > Delete.

• Click Delete in the confirmation window.

Note: Deleting the AWS TGW site object deletes the sites and nodes from the VPC and deletes the VPC. If the delete operation does not remove the object and returns any errors, check the errors from the status, fix the errors, and then re-attempt the delete operation. If the problem persists, contact technical support. You can check the status using the ... > Terraform Parameters > Apply status option.