Below are the prerequisites for deploying Cloud VMS on the customer’s AWS infrastructure.
Access to AWS console
VXG will need administrator-level access to the customer’s AWS console to set up all necessary components of Cloud VMS. This access can be temporary for deployment only, then it can be switched to read-only access.
Sometimes, there is a need to limit the access of this administrator account to certain resources running in AWS, in this case, please follow this guide - https://docs.aws.amazon.com/medialive/latest/ug/setting-up-restricted-admin.html
AWS Region
Please let us know which AWS Region we should use for deployment - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-regions-availability-zones.html
Domain names
Approach #1 - Use your domain names.
If you prefer to use your own domain names for all endpoints, we will need the following.
a. Two sub-domains
product_name.example.com - used for AWS instances, acts as a “backend” address
public_name.example.com - used for customer-facing web frontend based on VXG Cloud One
b. Domain delegation
A new domain name can be created in AWS Route53 or you can use an existing domain name. If you use the existing domain, the responsibility for the subdomain must be delegated to Route 53 - https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/CreatingNewSubdomain.html#UpdateDNSParentDomain
Approach #2 - Use no-name domain names provided by VXG.
VXG can provide domain names of the following format your_company_name.cloud-svcp.com and configure everything on our end.
Company information for the certificate
The following information is required in order to generate a certificate for the Super Admin API:
Country Name (2 letter code) [AU]:
State or Province Name (full name) [Some-State]:
Locality Name (eg, city) []:
Organization Name (eg, company) [Internet Widgits Pty Ltd]:
Organizational Unit Name (eg, section) []:
Common Name (e.g. server FQDN or YOUR name) []:
Email Address []: