About ASAv Deployment On the AWS Cloud
AWS is a public cloud environment that uses a private Xen Hypervisor. The ASAv runs as a guest in the AWS environment of the Xen Hypervisor. ASAv on AWS supports the following instance types:
- c3.large—2 vCPUs, 3.75 GB, 2 interfaces, 1 management interface
Note: Both the ASAv10 and ASAv30 are supported on c3.large, but we do not recommend the ASAv30 on c3.large due to resource under-provisioning.
- c3.xlarge—4 vCPUs, 7.5 GB, 3 interfaces, 1 management interface
Note: Only the ASAv30 is supported on c3.xlarge.
Note: The ASAv does not support the Xen Hypervisor outside of the AWS environment.
You create an account on AWS, set up the ASAv using the AWS Wizard, and chose an Amazon Machine Image (AMI). The AMI is a template that contains the software configuration needed to launch your instance.
Note: The AMI images are not available for download outside of the AWS environment.
Deploy the ASAv on AWS
The following procedure is a top-level list of steps to set up AWS on the ASAv. For detailed steps for setup, see Getting Started with AWS.
1. Log into aws.amazon.com and choose your region.
AWS is divided into multiple regions that are isolated from each other. The region is displayed in the upper right corner of your screen. Resources in one region do not appear in another region. Check periodically to make sure you are in the intended region.
2. Click My Account > AWS Management Console, and under Networking, click VPC > Start VPC Wizard, and create your VPC by choosing a single public subnet, and set up the following (you can use the default settings unless otherwise noted):
–Inside and outside subnet—Enter a name for the VPC and the subnets.
–Internet Gateway—Enables direct connectivity over the Internet (enter the name of the Internet gateway).
–outside table—Add entry to enable outbound traffic to the Internet (add 0.0.0.0/0 to Internet Gateway).
3. Click My Account > AWS Management Console > EC2, and then click Create an Instance.
–Select your AMI (for example Ubuntu Server 14.04 LTS).
Use the AMI identified in the your image delivery notification.
–Choose the instance type supported by the ASAv (for example, c3.large).
–Configure the instance (CPUs and memory are fixed).
–Under Advanced Details, add the Day 0 Configuration if desired. For more information on how to configure the Day 0 configuration with more information, such as Smart Licensing, see Prepare the Day 0 Configuration File.
Sample Day 0 Configuration
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
crypto key generate rsa modulus 2048
username admin nopassword privilege 15
username admin attributes
! example dns configuration
dns domain-lookup management
DNS server-group DefaultDNS
! where this address is the.2 on your public subnet
! example ntp configuration
name 126.96.36.199 time-a.nist.gov
name 188.8.131.52 time-b.nist.gov
name 184.108.40.206 time-c.nist.gov
ntp server time-c.nist.gov
ntp server time-b.nist.gov
ntp server time-a.nist.gov
–Storage (accept the defaults).
–Tag Instance—You can create a lot of tags to classify your devices. Give it a name you can use to find it easily.
–Security Group—Create a security group and name it. The security group is a virtual firewall for an instance to control inbound and outbound traffic.
By default the Security Group is open to all addresses. Change the rules to only allow SSH in from addresses you will be using to access your ASAv.
–Review your configuration and then click Launch.
4. Create a Key Pair.
Give the key pair a name you will recognize and download the key to a safe place; the key can never be downloaded again. If you lose the key pair, you must destroy your instances and redeploy them again.
5. Click Launch Instance to deploy your ASAv.
6. Click My Account > AWS Management Console > EC2 > Launch an Instance > My AMIs.
7. Make sure that the Source/Destination Check is disabled per interface for the ASAv.
AWS default settings only allow an instance to receive traffic for its IP address and only allow an instance to send traffic from its own IP address. To enable the ASAv to act as a routed hop, you must disable the Source/Destination Check on each of the ASAv's traffic interfaces (inside, outside, and DMZ).