This article explains how to create a CMS (Central Management Server) in AWS DR Datacenter.
- User must have an AWS account and permissions to deploy a server in the DR subnet.
- Internet access on CMS in AWS once is is deployed.
It is assumed here that the user has an AWS account and a VPC created which has accessibility to CenturyLink Cloud Production Datacenter.
Create a Security Group
- Click on Security Groups from the navigation tree, then click on Create Security Group button on the right.
- Name the security group and select the default VPN, click on Add Rule button.
a. Add Custom TCP Rule, Port Range 20080-20084, Source Restricted
b. Add Custom UDP Rule, Port Range 20080-20084, Source Restricted
c. Add All ICMP Rule IPv4, Source Restricted
d. Add SSH, Port Range 22, Source Restricted
- Click on Create.
Create CMS in AWS
- Go to Services > EC2.
- Click on Launch Instance.
- Select Community AMIs, and search for SafeHaven. Select SafeHaven-5 Base OS.
- Select t2.small resource type, and click Configure Instance Details.
- Select a subnet on your VPC which has reachability to CLC Production datacenter. Rest of the options can be left as default.
- Proceed with default 30GB storage.
- Click Next: Add Tags.
- Click Next: Configure Security Group. Click on Select existing Security Group. Select the security group that was created for the setup.
- Click on Review and Launch.
- Click on Launch.
- Select Proceed without a key pair.
- Click on Launch Instances.
- Once the Instance is created, user can name the instance as CMS and add tags if required.
NOTE: The default root password for the CMS will be provided upon SafeHaven License Request. It is STRONGLY recommended to change the default root password for security purposes.
Next Step is to Create DR SRN in AWS