is now a part of Cisco. Learn More

About Cisco

Custom AMI

Step 1: Login to your cmpute Console Application ( using registered Email Id and Password.

Step 2: You will be redirected to cmpute Dashboard. Next, click on the App Store located in the header.


Step 3: You will be redirected to the App store which has the apps supported on cmpute. To run Custom AMI app, click the Run A Job button.

Step 4: Now, to run Custom AMI job, fill all the required given text fields. There are following text fields to be filled:

Account: Select your AWS Account where you want to run the job.

Cloud Region: The Cloud region will be selected automatically.

Job Name: You can give any desired name to your job.

AMI ID: Specify the AMI ID to be used to launch instances by either providing the AMI ID or selecting an AMI from the list.

On AMI Update do not replace Instances: Select ‘On AMI Update do not replace Insatnces’ by clicking on the checkbox. If selected, on AMI ID update do not replace instances.

Security Group: Specify the security group(s) to be associated with instances.

Restrict to Selected Instances: Select by clicking on the ‘Restrict to selected Instances’ radio button. If selected, the same instance types will be launched else similar instances with the same vcpu will be launched.


Use Similar Instances: Select by clicking on the ‘Use Similar Instances’ radio button. If selected , cmpute will launch similar instance types if the selected instance type is unavailable.

Instance Type: Select an EC2 instance type.

  • If the user selects ‘Restrict to selected Instances’ radio button then more than one Instance Type can be selected
  • If the user selects ‘Use Similar Instances’ radio button then only one instance type can be selected


Launch script: Specify the user data script to be used while launching the instances.

Min On-demand Instance Count: Specify the minimum number of on-demand instances that should run as part of the Custom AMI environment.

Max Instance Count: Specify the maximum number of instances that should run as part of the Custom AMI environment.

Desired Count: Specify the desired number of instances. Auto Scaling ensures that your group has this many instances.

Elastic Load Balancer: Select one or more ELB, if you want to include it.

HealthCheck Grace Period: Specify the grace period. (It will be taken in seconds, For Example: 30)

Instance Profile: Select the Instance Profile type.

Key Pair: Select the Key Pair.

Replace Unhealthy Instance: Select by clicking on the ‘Replace Unhealthy Instance’ checkbox. If selected, an unhealthy instance will be replaced with another instance.

Associate Public IP Address: Select by clicking on the ‘Associate Public IP Address’ checkbox. If selected, the ‘Public IPs’ text box will be displayed.

Public IPs: Specify one or more public IP’s to be associated with instances. The number of IP’s to be provided should be greater than or equal to the ‘Max Instance Count’.

Enable Dedicated Placement Tenancy: Select by clicking on the ‘Enable Dedicated Placement Tenancy’ checkbox. If selected, then the instances will be placed in the dedicated infrastructure.

Launch Script: Specify the launch script. The launch script is executed before an instance is launched

Shutdown Script: Specify the shutdown script. The shut down script will execute before an instance is terminated. In order to execute the shutdown script follow the below link:

Registration Delay: Specify after how many seconds should the instances be attached to the Load balancer (Elastic Load Balancer) after the 22 instance status check is completed.

Additional Tags: Specify one or more tags

Scaling Rule: Specify the metric on which scale, upper threshold , lower threshold and scale down factors.


Step 5: Click on the Save/Run button once you are done with filling all the details. This action will save your job and is available to see later on the Jobs page.

Step 6: On successful job addition, you would get a popup where you can either start your job immediately (by clicking Run Now) or schedule your job to run later (by clicking on the button Schedule the Job).

Step 7: You can monitor the job progress using the Job Run Details page.