Below are the The list of prerequisites for deploying the deployment of Cloud VMS on the customer’s AWS infrastructure.
...
AWS:
AWS Account ID
Admin level Access Key and Secret Key, or Username and Password.
AWS region (e.g. us-east-1, us-east-2, eu-central, etc.).
1. Access to AWS account
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.
To keep your existing AWS infrastructure securely isolated, we recommend creating a separate AWS account and making it a part of your AWS Organization for centralized management and billing consolidation. Please follow the official AWS guide to add a new AWS account under your Organization - https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_accounts_create.html
If you do not have an AWS Organization created yet - please follow this guide - https://docs.aws.amazon.com/organizations/latest/userguide/orgs_manage_org_create.html
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
You can either provide a Username and Password to an admin-level user on your AWS account or create an Access Key and Secret Key as described in the following article Creating AWS Access Key
2. 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 #1 - 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 for them.
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) []:
...