Use an Amazon Web Services (AWS) destination to deploy application components to your AWS cloud environment. It’s important to note that a deployment pipeline can have only one public cloud destination (AWS, GCP or Azure).


Before you add an AWS destination, make sure you've created an AWS connection.


Click the Deploy tab. Clickto create a new deployment pipeline or click Edit on an existing pipeline. 


Add an AWS destination step or click and existing AWS step. Complete the following steps to select a deployment environment and configure your instances. When you’re done, click away to close the step.

Select a Deployment Environment and Configure Environments

Select a deployment environment, such as development or production, for your virtual servers. Your EC2 instances will be launched to the Virtual Private Cloud (VPC) and subnet for this environment.

ShuttleOps creates an initial “dev” environment for your default AWS connection. This environment uses the default VPC and subnet for the connection. You can change the environment name; if you want to delete the environment, you must delete the deployment pipeline associated with it. You can also create additional environments with different VPC/subnet combinations.

Tip If you’d like ShuttleOps to automatically create an environment, click on a deployment pipeline card on the Deploy tab, then click Create New Environment. ShuttleOps creates a copy of the pipeline and assigns a new environment. You can modify the environment name, VPC and subnet using the following instructions.


To select or configure an environment, click .


To select a deployment environment for your virtual servers, select an AWS connection in the Credentials list, then select an environment. The environment’s VPC and subnet are shown. If you want to create a new environment, select an AWS connection in the Credentials list, then click . To change the name, VPC or subnet for an environment, click .

Configure Your Virtual Servers

Configure the virtual servers you want to deploy. To add a virtual server, click Click to Add.

Tip  To ensure your application components are automatically added to your virtual servers, add your application components to the pipeline first. If you add a component after you create your virtual servers, you’ll need to manually add it to the servers.


Enter the following information to configure the virtual server.

Select the Instance Type

Use the Instance tab to select the Amazon EC2 instance type and configure the instance.

Instance Type  Select an EC2 instance type from the list. Use the search bar to find an instance type or filter the list to show a specific category.

Instance Name  ShuttleOps automatically creates an instance name. Once the instance has been launched, this name will appear in the AWS Console.

Instances  Enter the number of copies of the instance to launch.

Size (GB)  Enter the instance storage size.

SSH Key  Enter the name of a public SSH key you’ve already created with (or imported into) the AWS Console. If you don’t enter a key name, ShuttleOps will create an SSH key for you. Be aware that SSH keys created by ShuttleOps can only be accessed by AWS. ShuttleOps doesn’t retrieve or save these keys. This means you won’t be able to access the SSH key in the AWS Console or in ShuttleOps.

Create Security Rules

Use the Security Rules tab to create virtual firewall rules to control inbound and outbound traffic. For each rule, click Add new rule and enter the protocol, port, Classless Inter-Domain Routing (CIDR) block, and description. You can also create a copy of a rule and modify it. You’ll notice there’s a default security rule; you can change or delete this rule.

Configure DNS Records

Use the DNS tab to add DNS records. For each record, click Add new record and enter the subdomain, domain, and type. You’ll see that the instance name is shown in the Resource field. You can also create a copy of a record and modify it.

Configure Load Balancing

Use the Load Balancer tab to enable and configure AWS Elastic Load Balancing for your instances. If load balancing is enabled, an Application Load Balancer will be used to distribute incoming application traffic across your EC2 instances. Click the toggle to enable load balancing, then enter the following information.

VPC  The load balancer VPC is shown. The load balancer will use the deployment environment VPC.

Subnet  Select one or more subnets in the VPC. These subnets will be used to configure the load balancer.

Health Check  Select an application component to use as the health check target for the instance.

SSL Certificate  (Optional) Select the SSL certificate for the load balancer. Be sure you’re already added or imported the certificate in AWS.

Listeners  Add listeners to check for connection requests from clients. For each listener, click Add new listener and enter the source protocol and port (used for front-end connections from the client to the load balancer), and the instance protocol and port (used for back-end connections from the load balancer to the instance). You’ll notice there’s a default listener; you can change or delete this listener.

Add a Startup Script

Use the Startup Script tab to define a custom bash script. This script will be executed on each instance when the instance is first created.

Save Your Settings

Click Save. The virtual server is added to the AWS destination.


Select the Operating System

To select the operating system to run on the virtual server, click the banner of the virtual server card. Use the Platform list to select an operating system. You’ll notice that you can also change the number of instances and the server size.


Add Application Components to Your Virtual Servers

By default, all application components in your deployment pipeline are added to the virtual servers you’ve configured in your AWS destination. You can modify each virtual server to add or remove application components.

Tip  To ensure your application components are automatically added to your virtual servers, add your application components to the pipeline first. If you add a component after you create your virtual servers, you’ll need to manually add it to the servers.

Click beside a component to remove it from a virtual server. To add an application component to a server, click  and select a component.


Clone a Virtual Server

You can quickly create a virtual server by cloning an existing server. Just click the banner of the virtual server card, then click Clone.


Modify Virtual Server Settings or Delete a Virtual Server

To modify a virtual server, click on the server card. You can also click the banner to quickly change common settings such as the number of instances, platform, and server size. To delete a virtual server, click the banner, then click Delete.