New Release

Deploy to Amazon ECS with our guided UI step

Octopus Deploy Documentation

AWS

Last updated

Octopus Deploy includes dedicated integration with Amazon Web Services (AWS) to help you achieve repeatable, recoverable, secure, and auditable deployments:

Where do AWS Steps execute?
All AWS steps execute on a worker. By default, that will be the built-in worker in the Octopus Server. Learn about workers and the different configuration options.

Get started with ECS or deploy a new service

The Deploy Amazon ECS Service step makes it easier to get started or deploy a new service through Octopus.

The step guides you through the configuration of the task definition and service with built-in validation. Octopus generates and executes the CloudFormation templates, so you don't have to write any YAML or JSON.

A rocket links the Deploy Amazon ECS Service step in Octopus with tasks performed by Octopus in AWS to deploy the Octo Pet Shop website. Octopus generated the CloudFormation template and created and deployed the CloudFormation stack.

With the UI step, you can:

  • Monitor the deployment and service status, feedback, and error messages from Octopus. You don't need to open the AWS Console.
  • Deploy updates to your containerized apps without changing the deployment process. Create a release with the new version, and Octopus updates the task definition and service for you.
  • Set a timeout duration so you're not waiting hours to learn a deployment is stuck.

When you outgrow the guided UI step or need more flexibility, you can expose the underlying CloudFormation YAML and paste it into the Deploy an AWS CloudFormation Template step.

Centralize and secure your ECS deployments with Octopus

Octopus offers a central platform to manage your AWS resources, including account credentials, ECS clusters, certificates, configuration, and scripts.

The ECS deployment target and steps integrate with other Octopus features, including built-in AWS service accounts, runbooks, variables, channels, and lifecycles.

Octopus projects and runbooks share the same variables and accounts, making it easier to capture shared procedures, automate routine maintenance and respond quickly to emergencies.

Flexible, role-based security allows you to decide who can deploy to production and trigger runbooks against specific clusters. You can view the history of significant events and changes in the Octopus audit log.

Learn more

Need support? We're here to help.