There are a myriad of issues that can come up before, during, and after the provisioning process. This article will attempt to detail common issues/errors encountered and how to resolve them.
This will primarily focus on the cloud aspects and will lightly touch on, if at all, anything regarding platform usability and/or issues. This is also written from the perspective of AWS & Linux but the concepts broadly cover what you would experience when provisioning Windows machines or on Azure.
- Correct username must be used for basic auth credentials attached to OS profile record
- MID servers must have 443 access to REST API endpoints for AWS/Azure
- MID servers must be in the allow-liste (public IP) for SSH and ICMP for whichever Security Group the provisioned EC2 is in (default SG if not defined)
- MID servers must be in the allow-list on their internal firewalls to allow SSH/ICMP inbound/outbound to the EC2
- Make sure the user attempting to SSH to the EC2 is allowed in the correct Security Group list
- Make sure to use the correct default username when attempting to SSH. Be sure to verify that the username is correct for the Basic Auth credentials attached to the OS Profile record. This varies by Linux distribution (RHEL: ec2-user, Ubuntu: ubuntu):
- When trying to provision with a custom Security Group (ComputeFirewall variable) a subnet must be defined or the provisioning will not properly apply the Security Group and will use the default SG. Take note of this if attempting to provision with a specific SG.
- Since provisioning activities can use any MID server with defined Cloud capabilities, ensure that networking configurations are valid for all Cloud Management MID servers
- Private images can have a pre-defined SSH key. This prevents the system from infusing the default management key from sn_cmp_preference and prevents the Instance from being able to access the EC2 at all. This is a limitation on AWS' end. The workaround here would be to change sn_cmp_preference to the default SSH key in the private image so that the Instance can access the server post provisioning.