CMP

Connect an AWS account

Manage your Amazon EC2 instances here, next to your other servers. You can see them in one list, start, stop and reboot them, and create new ones. One connection covers every region enabled in your AWS account.

The portal signs in with the access key of an IAM user that is allowed to do only what the portal needs. Never use your root account's keys.

1. Create an IAM user with the portal's policy

  1. Sign in to the AWS console and open IAM › Policies › Create policy.
  2. Choose JSON, paste the policy below, and save it as cmp-portal.
  3. Open IAM › Users › Create user, name it, for example, cmp-portal, and leave console access off.
  4. Under Permissions, choose Attach policies directly and select cmp-portal.
  5. Open the new user, then Security credentials › Create access key. Choose Third-party service and copy the access key ID and secret access key. AWS shows the secret only once.
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "ListAndManageInstances",
      "Effect": "Allow",
      "Action": [
        "ec2:DescribeRegions",
        "ec2:DescribeInstances",
        "ec2:DescribeInstanceTypes",
        "ec2:DescribeImages",
        "ec2:DescribeKeyPairs",
        "ec2:DescribeSecurityGroups",
        "ec2:StartInstances",
        "ec2:StopInstances",
        "ec2:RebootInstances"
      ],
      "Resource": "*"
    },
    {
      "Sid": "CreateAndDeleteInstances",
      "Effect": "Allow",
      "Action": [
        "ec2:RunInstances",
        "ec2:TerminateInstances",
        "ec2:CreateTags",
        "ec2:ImportKeyPair",
        "ec2:CreateSecurityGroup",
        "ec2:AuthorizeSecurityGroupIngress"
      ],
      "Resource": "*"
    },
    {
      "Sid": "StartMigrationAgents",
      "Effect": "Allow",
      "Action": [
        "ec2-instance-connect:SendSSHPublicKey"
      ],
      "Resource": "*"
    }
  ]
}

2. Connect it here

  1. Go to Cloud accounts › Connect account and choose Amazon Web Services (EC2).

  2. Enter an Account name, for example "AWS – production", then paste the Access key ID and Secret access key.

  3. Enter a Default region, for example ap-south-1 (Mumbai) or us-east-1 (N. Virginia). The key is checked there. Instances are listed from every enabled region.

    AWS accounts created since 2025 are often set up as a project with one home region, and AWS itself blocks servers everywhere else. Find yours at settings.aws.com under Projects: open the project and look at Region under Additional info. Use that region as the default region. The portal then lists and creates servers only there.

  4. Select Test and connect.

Your instances appear on the Instances page within a minute, and the list refreshes every few minutes. Terminated instances are not listed.

What you can do

Feature Notes
Start, Shut down, Reboot, Power off Shut down stops the instance gracefully; Power off forces it to stop. A stopped instance keeps its disk, which AWS still charges for.
Details Instance ID and type, availability zone, launch date, key pair and public DNS name.
Create Create instances in any enabled region. See below.

Usage graphs, backups, the console and rescue mode are not available for AWS yet. Use the AWS console for those.

Creating instances

If it fails

Message What to do
AWS refused the access key The key was mistyped, deactivated or deleted. Create a new access key for the IAM user.
The IAM user may not use EC2 Instance Connect Add the third block of the policy above, or enter a login for the source on the migration's page.
The IAM user is not allowed to do this Attach the cmp-portal policy above to the user. The message names the IAM user AWS refused (…:user/name) and the action. If that isn't the user with the policy, the access key belongs to another user: create the key on the right one.
Your AWS account belongs to an AWS Organization whose service control policy blocks this Your account is managed by an organization that restricts it: AWS itself for new accounts set up as a project (see above), or a course, company or reseller. Use a region it allows, such as us-east-1, as the default region, or ask the organization's owner. The IAM policy can't override it. Regions the organization blocks are skipped when listing instances and aren't offered when creating one.
This region is not enabled for your AWS account Enable it under Account › AWS Regions, or choose another region.
This region has no default VPC In the VPC console, choose Actions › Create default VPC.
Your AWS account has reached its instance limit Request a higher quota in Service Quotas › Amazon EC2.

The secret access key is encrypted when stored and never shown again. Actions are recorded in the audit log.