• Secure Mobile Access
• Overview
• Before You Begin
• Installing SMA 8200v-Standalone or CMS on AWS
  • Configuring Settings on the Appliance Web Interface
  • Connecting to the Web Interface
  • Connecting to the Command Line Interface
• Licensing and Registering SMA 8200v-Standalone or CMS Appliance
  • Registering the SMA 8200v-Standalone or CMS
• Using the 30-day Trial Version
  • Deployment Considerations
  • Registering the 30-day Trial Virtual Appliance
  • Converting a Free Trial License to Full License
  • Exporting a Copy of Your Configuration Settings
• SonicWall Support
  • About This Document

Installing SMA 8200v-Standalone or CMS on AWS

This section explains how to deploy the SonicWall SMA 8200v-standalone or CMS for AWS image in AWS environment.

Installation of SMA 8200v-standalone or CMS on AWS is applicable only from SMA 12.4 firmware version and above.

Installing Guidelines

• To install the SMA 8200v-Standalone or CMS for AWS from the AWS console

• To Start, Stop, Reboot, or Terminate the instance

For details on deployment guidelines, refer SMA 8200v Azure/AWS Deployment Guidelines | SonicWall

To install the SMA 8200v-Standalone or CMS for AWS from the AWS console

1. Log into the AWS management console at https://aws.amazon.com.

2. From the EC2 Dashboard, click Launch instance which allows you to create virtual machines or instances, that run on the AWS.

   

3. In the Name and tags section, enter a descriptive name for the SMA 8200v appliance in the name field.

   

4. Click on the Application and OS Images (Amazon Machine Image) section and In search enter SonicWall SMA 8200v.

   .

5. Select SonicWall SMA 8200v Virtual Appliance 12.4.3-xxxxx (released build).

   

6. Click on the Instance type section and In search enter c5. Select the instance type you want to.

   

   The following recommendations are intended as guidelines to instance type selection, derived from extensive lab-based testing and analysis. It is extremely important to keep in mind that inherent differences in deployment-specific usage patterns may necessitate use of larger, or smaller, instance types than these general-purpose recommendations.

   Expected User Count	Recommended Instance Type	Specifications
   Up to 600	c5.large*	2 vCPU, 4GB RAM
   Up to 1000	c5.xlarge	4 vCPU, 8GB RAM
   Up to 3000	c5.2xlarge	8 vCPU, 16GB RAM

7. Configure the instance type settings and you can compare instance types.

   

   

8. Click on the Key Pair (login) section to assign a key pair for the instance.

   

   1. Select an existing key pair from the drop-down.

      Or

      Proceed without a key pair from the drop-down

      Or

      Click Create new key pair and follow the below steps.

      • Enter the Key pair name.
      • Select the key pair type and the private key file format.
      • Click Create key pair.

      

   2. After you create a new key pair, store the private key file in a secure and accessible location before continuing.

9. Click on the Network settings section, Select an existing security group.

   

   Or

   Select Create Security Group.

   .

10. The following steps to be followed for creating security group:

    

    1. Create the Security Group Rules and ensure to select the following rules:

       1. Allow SSH traffic from anywhere.

       2. Allow HTTPS traffic from the internet.

       3. Allow HTTP traffic from the internet.

    2. Enter the security group name and the Description.

    3. Enter the Security Group Rules.

       1. Security group rule 1 (by default)

          • Type - ssh
          • Protocol - TCP
          • Port range - 22

       2. Security group rule 2 (by default)

          • Type - HTTPS
          • Protocol - TCP
          • Port range - 443

       3. Security group rule 3

          For security group rule 3 by default Type (HTTP), Protocol (TCP), and Port range (40) to be changed.

          Change the default values as follows:

          • Type - Custom TCP
          • Protocol - TCP
          • Port range - 8443

11. Click on the Configure storage, configure the disk size and your desired Root volume.

    

12. Select Advanced Details > User Data and fill the form user data with YAML input.

    • For SMA 8200v-standalone:

      

    • For CMS:

      

    If the YAML input is invalid, the deployment leads to inconsistent state.

13. Check the Summary details and If required, click left pane sections to make changes.

    Number of instances can be changed in the summary details before launching instance.

    

14. Click Launch Instance to launch SonicWall SMA 8200v-standalone or CMS.

    After the SMA 8200v-standalone or CMS instance is launched, you can access the appliance from a browser. To know how to access the appliance through a browser, see Connecting to the Web Interface.

You are now ready to begin using your appliance. See:

• Configuring Settings on the Appliance Web Interface
• Using the 30-day Trial Version

To Start, Stop, Reboot, or Terminate the instance

1. In the EC2 console, click Instances in the AWS left pane.

   All your Amazon machine instances are displayed, along with their EC2 Instance IDs.

   The <EC2 Instance ID> is the default password for the administrator account.

2. Select and right-click on the SMA 8200v-standalone or CMS deployed instance and select the required action:

   • Start instance
   • Stop instance
   • Hibernate instance
   • Reboot instance
   • Terminate instance

   

   For more information on how to start or stop an instance, refer to http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html.