mirror of
https://github.com/fleetdm/fleet
synced 2026-05-22 16:39:01 +00:00
458dcfd366
This is the last of three PRs to migrate the deployment guides into the docs. Changes: - Moved content from `/articles/deploying-fleet-on-hetzner-cloud.md` to `/docs/deploy-on-hetzner-cloud.md`. - Removed `/articles/deploy-fleet-on-hetzner-cloud.md`. - Moved images from the guide to `/docs/images` and renamed. - Deleted redundant images and article cover image. - Set up a redirect `/deploy/deploying-fleet-on-hetzner-cloud` => `/docs/deploy/deploy-on-hetzner-cloud`. - Set up a redirect `/deploy` => `/docs/deploy` to redirect "Deployment guides" in the main nav to the docs. - Updated display names (in the docs nav) for existing deployment guides in the docs to match the naming convention (E.g., "Deploy Fleet on CentOS" => "CentOS") - Removed the deployment guides article category from the blog. # Checklist for submitter - [ ] Manual QA for all new/changed functionality --------- Co-authored-by: Eric <eashaw@sailsjs.com> Co-authored-by: Rachael Shaw <r@rachael.wtf>
1.8 KiB
1.8 KiB
Deploy Fleet on AWS ECS
Terraform reference architecture can be found here
Infrastructure dependencies
MySQL
In AWS we recommend running Aurora with MySQL Engine, see here for terraform details.
Redis
In AWS we recommend running ElastiCache (Redis Engine) see here for terraform details
Fleet server
Running Fleet in ECS consists of two main components the ECS Service & Load Balancer. In our example the ALB is handling TLS termination
Fleet migrations
Migrations in ECS can be achieved (and is recommended) by running dedicated ECS tasks that run the fleet prepare --no-prompt=true db command. See terraform for more details
Alternatively you can bake the prepare command into the same task definition see here for a discussion, but this not recommended for production environments.