AWS is the Amazon public cloud, offering a full range of services and features across the globe in various datacenters. AWS provides businesses with a flexible, highly scalable, and low-cost way to deliver a variety of services using open standard technologies as well as proprietary solutions. This section of documentation will help you get Morpheus and AWS connected to utilize the features below:


  • Instance, Service, Infrastructure Provisioning & Synchronization
  • EKS Cluster Creation & Synchronization
  • Morpheus Kubernetes, Docker & KVM Cluster Creation
  • ELB Classic Load Balancer Creation & Synchronization
  • ELB Application Load Balancer (ALB) Creation & Synchronization
  • Security Group Creation & Synchronization
  • Security Group Rule Creation & Synchronization
  • Network Synchronization
  • VPC Creation & Synchronization
  • CloudFormation Provisioning & Resource Synchronization
  • Terraform Provisioning & Resource Synchronization
  • Pricing & Costing Synchronization
  • MetaData Tag Creation & Synchronization
  • S3 Bucket Creation & Synchronization
  • Route53 Automation & Synchronization
  • IAM Profile Synchronization and Assignment
  • RDS Support
  • Backups / Snapshots
  • Migrations
  • Auto Scaling
  • Remote Console (SSH & RDP)
  • Lifecycle Management and Resize
  • Restore from Snapshots
  • Elastic IP Assignment
  • Network Pools
  • Enhanced Invoice Costing


AWS IAM Security Credentials
Access Key Secret Key Sufficient User Privileges (see MinimumIAMPolicies section for more info)
Security Group Configuration for Agent Install, Script Execution, and Remote Console Access
  • Typical Inbound ports open from Morpheus Appliance: 22, 5985, 3389 (22 & 3389 required for Console. 22 & 5985 required for agent-less comms)
  • Typical Outbound to Morpheus Appliance: 443 (Required for Agent install & comms)


These are required for Morpheus agent install, communication, and remote console access for windows and linux. Other configurations, such as docker instances, will need the appropriate ports opened as well. Cloud-init Agent Install mode does not require incoming access for port 22.

IP assignment required for Agent install, Script Execution, and Console if the Morpheus Appliance is not able to communicate with AWS instances private ip’s.


Each AWS Cloud in Morpheus is scoped to an AWS Region and VPC. Multiple AWS Clouds can be added and even grouped if different region and VPC combinations are needed. It’s also recommended you verify Security Groups are properly configured in all regions Morpheus Clouds will scope to.

Adding an AWS Cloud

  1. Navigate to Infrastructure -> Clouds
  2. Select + Create Cloud
  3. Select AWS
  4. Enter the following:

Cloud Configuration

Name of the Cloud in Morpheus
Unique code used for api/cli, automation and policies.
Description field for adding notes on the cloud, such as location.
For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.

When enabled, Morpheus will maintain the expected powered on state of managed VM’s and power on any managed VM’s in the cloud that have been shut down for unknown reasons (not powered off by Morpheus) to ensure availability of services.


When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VM’s should be maintained in Morpheus. This setting is not applicable to discovered/unmanaged resources.


Select AWS Region for the Cloud
Access Key ID from AWS IAM User Security Credentials.
Secret Access Key associate with the Access Key ID.
Check to use use Host IAM Credentials
Supports security token service (STS) to AssumeRole by entering an AWS Role ARN
Morpheus will sync information on all EC2 Instances in the selected VPC the IAM user has access to, including Name, IP Addresses, Platform Type, Power Status, and overall resources sizing for Storage, CPU and RAM, every 5 minutes. Inventoried EC2 Instances will appear as Unmanaged VM’s.
In addition to the information synced from Basic Inventory level, Morpheus will gather Resource Utilization metrics for Memory, Storage and CPU utilization per VM.
Existing EC2 Instances will not be inventoried


Cloud Watch must be configured in AWS for Morpheus to collect Memory and Storage utilization metrics on inventoried EC2 instances.

Specify if the target account is using EC2-VPC or EC2-Classic Platform. In almost all cases, VPC should be selected, and then select the target VPC from the synced available VPC’s list, or All VPC’s.
  1. The AWS cloud is ready to be added to a group and saved. Additional configuration options available:
S3 bucket for Image transfers, required for migrations into AWS.
Enable or disable encrytion of EBS Volumes
For Gov Cloud pricing only, key for standard managing cost account
For Gov Cloud pricing only, secret for standard managing cost account

Advanced Options

Specify a default domain for instances provisioned to this Cloud.
Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
Alternate Appliance url for scenarios when the default Appliance URL (configured in admin -> settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
Configures the time zone on provisioned VM’s if necessary.
Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
Unmanaged or select a Network Integration (NSX, ACI etc)
On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
Security Server setting is for Security Service Integrations such as ACI
Select Internal (Morpheus) or an existing Trust Provider Integration
Single Disk, LVM or Clustered
Select Internal Backups (Morpheus) or a Backup Integration
Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
Enable Guidance recommendations on cloud resources.
Enable for Morpheus to sync Costing data from the Cloud provider, when available. If your organization utilizes reserved instances and you want to pull in related pricing data, select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the AWS Cost Explorer API or similar service for other clouds.
Records for instances provisioned in this cloud will be added to selected DNS integration.
Services for instances provisioned in this cloud will be added to selected Service Registry integration.
Select a Chef, Salt, Ansible or Puppet integration to be used with this Cloud.
Select CMDB Integration to automatically update selected CMDB.
Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
  • SSH / WINRM: Morpheus will use SSH or WINRM for Agent install.
  • Cloud Init / Unattend (when available): (DEFAULT) Morpheus will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. Morpheus will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
Set a proxy for outbound communication from the Morpheus Appliance to the Cloud endpoints. Proxies can be added in the Infrastructure -> Networks -> Proxies tab.
Enable to have Agent Installation on by default for all provisioning into this Cloud. Disable for Agent Installation to be off by default for all provisioning into this Cloud.

Provisioning Options

Set a proxy for inbound communication from Instances to the Morpheus Appliance. Proxies can be added in the Infrastructure -> Networks -> Proxies tab.
Bypass Proxy for Appliance URL
Enable to bypass proxy settings (if added) for Morpheus Agent communication to the Appliance URL.
Add cloud-init user data. Morpheus 4.1.0 and earlier assumes bash syntax. Morpheus 4.1.1 and later supports all User Data formats. Refer to for more information.

Enhanced Invoice Costing Configuration

In addition to standard AWS costing data (Enabled by editing the AWS cloud integration and setting the COSTING value to “Costing” or “Costing and Reservations”), Morpheus can utilize highly-granular data from AWS Costing and Utilization Reports (CUR) in its integration. Once enabled, this data can be consumed by accessing Invoice endpoints of Morpheus API and eventually through the UI after a future update. Continue on with this section to enable these reports in the AWS web console and configure the Morpheus cloud integration to work with this report data.

Begin by logging into the AWS Billing Console, then click Create report.


Include a name for your report and mark the box to “Include resource IDs”. Morpheus uses these resource IDs to map costs to various resources. Click Next.


On the following page, begin by identifying an S3 bucket to house reports. Click Configure near the top of the page and select an existing bucket or create a new one.


After identifying the bucket, you must mark the box to accept the default policy being applied to the bucket. Click Save.


The default policy applied to the bucket is below:

  "Version": "2008-10-17",
  "Id": "SomeID",
  "Statement": [
      "Sid": "SomeStmtID",
      "Effect": "Allow",
      "Principal": {
        "Service": ""
      "Action": [
      "Resource": "arn:aws:s3:::bucket-name"
      "Sid": "SomeStmtID",
      "Effect": "Allow",
      "Principal": {
        "Service": ""
      "Action": [
      "Resource": "arn:aws:s3:::bucket-name/*"

After choosing a bucket, accepting the default policy, and saving the change, you’re brought back to the report delivery page. By default, CUR reports are saved to a folder at the path my-report-name/date-folder. If this bucket already contains CUR reports, you may want to specify a prefix path in the “Report path prefix” field. Outside of this field, use the default values as shown in the screenshot below, then click Next.


On the following page, make your final review and click Review and Complete. Following this, you will see your newly configured report in the list of CUR report(s).

In addition, the AWS cloud user associated with the integration in Morpheus needs IAM policy permission to access Cost Explorer. Attach a policy like the one below to this cloud user:

  "Version": "2012-10-17",
  "Id": "SomeID",
  "Statement": [
      "Sid": "SomeStmtID",
      "Effect": "Allow",
      "Action": [
      "Resource": [


If the Cost Explorer permissions are granted at the master account level, the user will see all costs for each member account; if granted at the member account, only the costs for that member account are available.

With the AWS console configuration steps complete, we can move back into Morpheus. Keep in mind it is only necessary to set up one AWS cloud for Costing since we process all records in the CUR report.

Once back in Morpheus, add or edit the relevant AWS cloud integration (Infrastructure > Clouds > + ADD OR click the pencil icon in the row for the chosen AWS integration). Expand the Advanced Options drawer and complete the following fields:

  • COSTING BUCKET: The S3 bucket name
  • COSTING REGION: The region the bucket was created in
  • COSTING FOLDER: This is the report path prefix if you configured one earlier
  • COSTING REPORT NAME: The name given to your CUR report
  • COSTING KEY: If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
  • COSTING SECRET: If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
  • LINKED ACCOUNT ID: If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in


If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.


Save changes to your cloud integration.


It may take as long as one hour for Morpheus to process the next CUR report.

Minimum AWS IAM Policies

Below are the AWS IAM Permissions covering the minimum access for Morpheus applying to all resources and services.

See for more information.

    "Version": "2012-10-17",
    "Statement": [
            "Sid": "VisualEditor0",
            "Effect": "Allow",
            "Action": [
            "Resource": "*"

If you need to limit actions based on filters you have to pull out the action and put it in a resource based policy since not all the actions support resource filters.

See for more info on limiting resources by filter.

Resource filter example:

  "Effect": "Allow",
  "Action": [
  "Resource": *
  "Effect": "Allow",
  "Action": "ec2:TerminateInstances",
  "Resource": "arn:aws:ec2:us-east-1:123456789012:instance/*",
  "Condition": {
    "StringEquals": {
       "ec2:ResourceTag/purpose": "test"