Fleet logo
Menu An icon indicating that interacting with this button will open the navigation menu.
Fleet logo An 'X' icon indicating that this can be interacted with to close the navigation menu.
Solutions A small chevron
Device management

Device management

Remotely manage, and protect laptops and mobile devices.

Orchestration

Orchestration

Automate tasks across devices, from app installs to scripts.

Software management

Software management

Inventory, patch, and manage installed software.

Extend Fleet

Extend Fleet

Integrate your favorite tools with Fleet.

Customers A small chevron
Stripe + Fleet

Stripe + Fleet

Stripe consolidates multiple tools with Fleet.

Foursquare + Fleet

Foursquare + Fleet

Foursquare quickly migrates to Fleet for device management.

What people are saying

What people are saying

Stories from the Fleet community.

Pricing
More A small chevron
Try it yourself Get a demo
{{thisPage.meta.articleTitle}}
search

Deploy Fleet on AWS ECS

{{articleSubtitle}}

| The author's GitHub profile picture

Ben Edwards

Share

Share this article on Hacker News Share this article on LinkedIn Share this article on Twitter
Docs Docs REST API REST API Guides Guides Get a demoGet a demo

Deploy Fleet on AWS ECS

{{articleSubtitle}}

| The author's GitHub profile picture

Ben Edwards

Deploy Fleet on AWS ECS

An icon indicating that this section has important information

Archived. While still usable, this guide has not been updated recently. See the Deploy Fleet docs for supported deployment methods.

Deploy Fleet on AWS ECS

A Terraform reference architecture can be found in the fleetdm/terrqform repository.

Infrastructure dependencies

MySQL

In AWS we recommend running Aurora with MySQL Engine.

Redis

In AWS we recommend running ElastiCache (Redis Engine).

Fleet server

Running Fleet in ECS consists of two main components the ECS service & load balancer.

Fleet migrations

Migrations in ECS can be achieved by running dedicated ECS tasks that run the fleet prepare --no-prompt=true db command.

Alternatively you can bake the prepare command into the same task definition see here for a discussion, but this is not recommended for production environments.