Follow this procedure if you are using public IP or public DNS addresses to log onto a VM.
- From the SSH client console, log in to the VM using the same authentication type you chose either when you deployed the VM using the solution template or the single VM from an image.
Authentication type Action SSH public key Enter the following: # ssh -i ssh-private-key.pem azureuser@VM-public-IP-address or VM-public-DNS-address
where:- The ssh-private-key is the private key file (.pem) specified when you deployed the VM.
- The azureuser is the user name specified when you deployed the VM.
- The VM-public-IP-address or VM-public-DNS-address is the DNS host name or public IP address of the VM.
Password Enter the following: # ssh azureuser@VM-public-IP-address or VM-public-DNS-address Password: password
where:- The azureuser is the user name specified when you deployed the VM.
- The VM-public-IP-address or VM-public-DNS-address is the DNS host name or public IP address of the VM.
- The password is the password specified when you deployed the VM.
To comply with CIS hardening requirements, VantageCloud Enterprise (DIY) uses a predefined OS user account during provisioning.
The default OS username is azureuser. This username is fixed at provisioning time and cannot be changed. This approach is used to align with CIS hardening security baseline by default.
Managing Additional Users
You can add additional usernames after provisioning by adding them explicitly to the Allow Users list.Adding or removing users does not require reprovisioning the site.This helps you with Strong CIS aligned security baseline by default and avoids unintented users to sign-in into the systems.