Cloud Deployment Guides for Advanced Server Access
With Advanced Server Access, Admins can deploy cloud servers as well as on-premise servers for their projects and teams. Each Cloud Provider has certain features that are supported with Advanced Server Access, so use the following tables below for guides on deploying cloud servers and as a reference for what features are supported with their respective environments.
|Amazon Web Services Deployment Guides|
|Google Cloud Platform Deployment Guides|
|Azure Deployment Guides|
Supported Features with Advanced Server Access
- An environment is a Cloud Provider for virtual machines.
- Auto Enrollment is the process of enrolling the virtual machines you've created within an Environment with your Advanced Server Access team.
- IP Configuration is the method of setting a concrete IP address for your team's servers.
- De-Duplication is the method of differentiating between new servers that are cloned from existing servers.
Note: Each Project within your Advanced Server Access team has a default limit of 10 linked Cloud Accounts.
|Environment||Auto Enrollment||IP Configuration||De-Duplication|
|AWS||Servers automatically enroll using an AWS account retrieved from EC2 Metadata Service and correlate with Advanced Server Access Platform configurations||In the absence of an explicit configuration in the Agent's
A Scaleft-enrollment-token is used as an instance or as project metadata that contains and enrollment token (instead of it being in a file)
|Must be either explicitly configured or selected by heuristic||
|Azure||-||Must be either explicitly configured or selected by heuristic||Cloned Virtual Machines are deduplicated using VMID. If the VMID is changed by an action, we will detect it as a new machine. If the VMID is the same, it is considered as the same machine.|
|On-Premise||-||Must be either explicitly configured or selected by heuristic||-|