When an AWS RH is created, CloudBolt provides a choice of regions to be imported, and one CB environment will be created for each. Additionally, VPCs can be specified for each CB AWS environment to build & manage instances within a specific VPC.


Each AWS environment comes with out of the box parameters and options to allow for easeful deployment and customization of AWS instances from CloudBolt. These are all shown under the “AWS Parameters” tab on the environment and include the following:

  • Instance Type *
  • Elastic IP Allows you to specify an Elastic IP at provision time.
  • Key pairs *
  • Security Groups *
  • Availability Zone Allows you to optionally launch new AWS instances into a specific availability zone within a region to protect an application from the failure of a single Amazon data center.
  • EBS Volume Type A required parameter for specifying volume type when provisioning or adding a disk to an existing server
  • IOPS Input/Output Operations per second. This parameter is dependent on EBS Volume Type and is needed for creating io1 volumes.
  • Auto-delete EBS Volumes on termination True by default, this sets your volumes to be deleted automatically when deleting the attached instance.

*An AWS environment will discover which instance types, keypairs, and security groups are available.

Networks and AMIs may also be imported for each environment.

For information about passwords on AWS Windows Instances, see the remote scripts section.


When you import AMIs in CloudBolt, CloudBolt will create an OS Build for that AMI. If you import the corresponding AMI in other regions, CloudBolt will automatically reuse the pre-existing OS Build, and associate the newly imported AMI with it. This will only happen if the name of the OS Build has not been altered and matches the name of the AMI. However, CB Admins can edit the OS Build for an AMI to override that default behavior.

Importing and Viewing AWS Billing Data

In CloudBolt, you can import your AWS billing data and view billed costs for individual servers and CloudBolt groups.

Set Up

There are a few steps required to get started:

  1. First, set up an s3 bucket to have billing reports exported as .csv files. Refer to these instructions for Setting Up an Amazon S3 Bucket for AWS Cost and Usage Reports
  2. In CloudBolt, go to the detail view of the AWS Resource Handler associated with the account for which billing is being exported. Click the Edit Settings button and enter the name of the s3 bucket under s3 billing bucket.
  3. The recurring job Import Public Cloud Billing Data is set to automatically run once a month. You can configure its cron schedule to run at an opportune time after bills come in, or just run the job manually to sync existing billing data.
  4. Congrats! You’re all set up.


You can view billing summaries from AWS servers’, AWS resource handlers’, and groups’ Billing tabs. Groups Billing tabs will display a graph with data aggregated per-resource handler, where you’ll see the charges for EC2 instances within each resource handler for that group. Servers will show billed charges for the instance only, excluding charges for any associated resources. CloudBolt will also recommend reserved instances that could be purchased through the EC2 portal which would save money for individual instances. You can view these recommendations from the Billing tab on your Resource Handlers.

Modifying or Adding Volumes

Azure has some specific parameters associated with volumes that other resource handlers do not have. In addition to Disk Size, you also may need to specify parameters around EBS Volumes. If you do not specify an EBS Volume Type it will default to gp2. If adding an io1 volume, you will also need to specify an amount of IOPS which must be greater than 100. When creating a gp2 volume, the size must be greater than 4GB. When creating sc1 or st1 volumes, the size must be greater than 500GB. You can also specify if you want the Volume to be encrypted with AWS standard encryption.

When placing a modification order to add or change disks in the API, these are the accepted parameters:

disk_size: The size to change the original volume to
new_disk_size: The size for the new volume to be added
ebs_volume_type: The ebs volume type for the new volume, currently accepted values are [io1, gp2, st1, sc1, standard]
iops: Accepted when using io1 volume type
aws_volume_encryption: Submitted with True or False Boolean Value to encrypt the additional volume

AWS GovCloud (US) and AWS China

AWS GovCloud (US) and AWS China resource handlers can currently connect to all GovCloud Regions. Similar to AWS resource handlers, CloudBolt will create one environment for each imported region. They do not currently support billing information.