Go to the AWS account for the Cloud APIC infra tenant.

Click the Services link at the top of the screen, then click the EC2 link.

In the EC2 Dashboard screen, you should see text displaying the number of running instances in the Resources area (for example, 1 Running Instances). Click this running instances link.

Choose the Cloud APIC instance named Capic-1 and copy the IP address that is shown in the IPv4 Public IP column.

In the AWS site, get the Cloud APIC IP address.

Open a browser window and, using the secure version of HTTP (https://), paste the IP address into the URL field, then press Return to access this Cloud APIC.

Enter the following information in the login page for the Cloud APIC:

Click Login at the bottom of the page.

Click Begin Set Up.

In the DNS Servers row, click Edit Configuration.

In the DNS and NTP page, add the DNS, if necessary, and NTP servers.

1. If you want to use a specific DNS server, under the DNS Servers area, click +Add DNS Provider.

2. Enter the IP address for the DNS servers and, if necessary, check the box next to Preferred DNS Provider.

3. Click the check mark next to the DNS server, and repeat for any additional DNS servers that you want to add.

4. Under the NTP Servers area, click +Add Providers.

5. Enter the IP address for the NTP servers and, if necessary, check the box next to Preferred NTP Provider.

6. Click the check mark next to the NTP server, and repeat for any additional NTP servers that you want to add.

When you have finished adding the DNS and NTP servers, click Save and Continue.

In the Region Management row, click Begin.

Determine if you want to use AWS Transit Gateway.

In the Regions to Manage area, verify that the Cloud APIC home region is selected.

Select additional regions if you want the Cloud APIC to manage additional regions, and to possibly deploy CSRs to have inter-VPC communication and Hybrid-Cloud, Hybrid Multi-Cloud, or Multi-Cloud connectivity on those other regions.

To deploy cloud routers locally to this region, click to place a check mark in the Cloud Routers check box for that region.

When you have selected all the appropriate regions, click Next at the bottom of the page.

Enter the following information on the General Connectivity page.

1. In the Hub Network area, click Add Hub Network.

   The Add Hub Network window appears.

2. In the Name field, enter a name for the hub network.

3. In the BGP Autonomous System Number field, enter a zero for AWS to choose a number, or enter a value between 64512 and 65534, inclusive, for each hub network, and then click the check mark next to the field.

   To configure your own BGP autonomous number, enter a value between 64512 and 65534 for each hub network.

   We recommend that you use different numbers for different instances of AWS Transit Gateway.

4. In the TGW Connect field, click the checkbox if you want to enable the AWS Transit Gateway Connect feature.

   For more information on the AWS Transit Gateway Connect feature, see the Increasing Bandwidth Between VPCs by Using AWS Transit Gateway or AWS Transit Gateway Connect document.

5. In the CIDRs area, click Add CIDR.

   This will be the AWS Transit Gateway Connect CIDR block, which will be used as the connect peer IP address (the GRE outer peer IP address) on the Transit Gateway side.

   1. In the Region field, select the appropriate region.

   2. In the CIDR Block Range field, enter the CIDR block that will be used as the connect peer IP address on the Transit Gateway side.

   3. Click the checkmark to accept these values for this CIDR block.

   4. For every managed region that will be using the AWS Transit Gateway Connect feature, repeat these steps to add CIDR blocks to be used for each of those managed regions.

6. To add a subnet pool for the CSRs, click Add Subnet Pool for Cloud Router and enter the subnet in the text box.

   The first subnet pool for the first two regions is automatically populated. If you selected more than two regions, you will need to add a subnet for the cloud router to the list for the additional two regions. Addresses from this subnet pool will be used for inter-region connectivity for any additional regions that are added that need to be managed by the Cloud APIC after the first two regions. This must be a valid IPv4 subnet with mask /24.

   Note	The /24 subnet provided during the Cloud APIC deployment would be sufficient for up to two cloud sites. If you need to manage more than two cloud sites, you need to add more subnets.

7. Enter a value in the BGP Autonomous System Number for CSRs field.

   The BGP ASN can be in the range of 1 - 65534.

   Note	Do not use 64512 as the autonomous system number in this field.

8. In the Assign Public IP to CSR Interface field, determine if you want to have a public or a private IP address assigned to the CSR interfaces.

   • To have a public IP address assigned to the CSR interfaces, leave the check in the Enabled check box. By default, the Enabled check box is checked.

   • To have public IP disabled to the CSR interfaces, uncheck the Enabled check box. A private IP address is used for connectivity in this case.

   Note	Disabling or enabling a public IP address is a disruptive operation and can result in traffic loss.

   Beginning with release 5.2(1), both the public and private IP addresses assigned to a CSR are displayed with the other details of the router in the Cloud Resources area. If a public IP is not assigned to a CSR, only the private IP is displayed.

9. Under the Cloud Router Template area, in the Number of Routers Per Region field, choose the number of Cisco Cloud Services Routers that will be used in each region.

   See Understanding Limitations for Number of Sites, Regions and CSRs for more information on any limitations on the number of CSRs per region.

10. In the Username, enter the username for the Cisco Cloud Services Router.

11. In the Password field, enter the password for the Cisco Cloud Services Router.

12. In the Throughput of the routers field, choose the throughput of the Cisco Cloud Services Router.

    Changing the value in this field changes the size of the CSR instance that is deployed. Choosing a higher value for the throughput results in a larger VM being deployed.

    Note	If you wish to change this value at some point in the future, you must delete the CSR, then repeat the processes in this chapter again and select the new value that you would like in the same Throughput of the routers field.

    In addition, the licensing of the CSR is based on this setting. You will need the equivalent or higher license in your Smart account for it to be compliant. See Requirements for the AWS Public Cloud for more information.

    Note	Cloud routers should be undeployed from all regions before changing the router throughput or login credentials.

13. Enter the necessary information in the TCP MSS field, if applicable.

    Beginning with Release 5.0(2l), the TCP MSS option is available to configure the TCP maximum segment size (MSS). This value will be applied all cloud router interfaces, including VPN tunnels towards the cloud and external tunnels towards the on-premises site or other cloud sites. For VPN tunnels towards the cloud, if the cloud provider's MSS value is less than the value that you enter in this field, then the lower value is used; otherwise, the value that you enter in this field is used.

    The MSS value affects only TCP traffic, and has no impact on other types of traffic, such as ping traffic.

14. In the License Token field, enter the license token for the Cisco Cloud Services Router.

    This is the Product Instance Registration token from your Cisco Smart Software Licensing account. To get this license token, go to http://software.cisco.com, then navigate to Smart Software Licensing > Inventory > Virtual Account to find the Product Instance Registration token.

    Note

    If the public IP addresses are disabled to the CSRs in 15.h, the only supported option is AWS Direct Connect or Azure Express Route to Cisco Smart Software Manager (CSSM) when registering smart licensing for CSRs with private IP addresses (available by navigating to Administrative > Smart Licensing). You must provide reachability to the CSSM through AWS Direct Connect or Azure Express Route in this case. When the public IP addresses are disabled, public internet cannot be used because private IP addresses are being used. The connectivity should therefore use Private Connection, which is AWS Direct Connect or Azure Express Route.

Click the appropriate button, depending on whether you are configuring inter-site connectivity or not.

Enter the following information in the Inter-Site Connectivity page:

When you have entered all the necessary information on this page, click Save and Continue at the bottom of the page.

In the Smart Licensing row, click Register.

Enter the necessary information in the Smart Licensing page.

Click Register at the bottom of the page if you entered the necessary licensing information on this page, or click Continue in Evaluation Mode if you want to continue in evaluation mode instead.

Verify the information on the Summary page, then click Close.

In Cisco Cloud APIC, verify the following settings: