How do I deploy CMS on Amazon Web Service (AWS)?

03/26/2020 9 8481

DESCRIPTION:

This article covers how to deploy SonicWall's Secure Mobile Access (SMA) Central Management Server (CMS) via Amazon AWS.

NOTE: SMA firmware version 12.2 and later support deployment of CMS on Cloud. This deployment is similar to the deployments on HyperV and VMware Esxi.

RESOLUTION:

Once your account has been granted access to the AMI you are ready to create an ‘instance’ of the CMS.
This is done in the ‘EC2’ service (‘Services’ menu, then select ‘EC2’ under the ‘Compute’ heading.

Procedure to deploy  CMS on AWS:

1. Create an AWS account.   Note:  Users have to comply with policies and procedures required by * https://aws,amazon.com.  for moving further in deployments. 
2. User's  planning to deploy CMS on one of the datacenters  provided by *Amazon 
   eg:
   Northern California (us-west-1)
   Northern Virginia (us-east-1)
   EU Paris (eu-west-3)
   EU Ireland (eu-west-1)
   Mumbai (ap-south-1)
   
   
3. Your account ID should have access to CMS AMI. If you do not have access please contact SonicWall Sales for having access granted.
4. Once logged into AWS and your account has been granted access to the CMS AMI you are ready to create an ‘instance’ of CMS.
5. Navigate to Services | Compute | EC2
   
6. Click Launch Instance
   
7. Search for CMS and click My AMIs. Click Shared with me. Choose the AMI to launch =  SonicWall CMS 12.2.0-<build number>
   
8. Choose the Instance Type of T2 Micro/Medium/Large.
9. Click Configure Instance Details | Advanced Details | User Data: Type the CMS console password that you will use.
   
10. Configure Security Group. You need to specify ports to open. Check  if there is a shared group that you can use. Otherwise create a Security Group with the following and select it: (Security Note -  This is will allow access from any Source Address)
    Ports Recommended for access to CMS are:
    1. SSH 22/tcp
    2. Custom 8443/tcp
    3. HTTPS 443/tcp
       
11. Launch the AMI   (Choosing Private Key file is more secure)
    
12. Wait for the instance to start running and to proceed for  configuration
13. You should be able to log in to the console of the launched instance using the IP address of the instance and port number https://<CMS IP Address>:8443 using the password you specified in Step 9.