CPM Configuration process hangs or fails
The CPM Configuration process is pretty simple and straightforward. IF it hangs or fails it probably means that wither there was a connectivity problem (CPM could not access the Internet): this usually causes a long hang and failure at the end, or a problem with the AWS credentials.
- Connectivity problem - CPM uses the AWS API and therefore need access to the AWS endpoint (see Regions & Endpoints). A connectivity issue can happen only in a VPC: All regular EC2 instances have outbound access to the Internet be default. When launching your CPM Server in a VPC, you need to allow it access by connecting the instance to the Internet: This is usually done by attaching an Elastic IP to the instance or by using NAT configuration (see NAT instances). Besides that, VPC security groups also define outbound rules, so you need to make sure you have outbound connectivity using the HTTPS protocol to the Internet, or at least to the AWS endpoints.
- Credentials problem: If you mis-pasted the AWS credentials that can cause the process to fail. Also if you are using IAM credentials for the CPM configuration process, you need all the permissions for the configuration operations, mainly creating and attaching EBS volumes. To see the required permission, see our users guide Chapter 11.4 - Using IAM.