Slack engineering
Read post

Shipyard: How We Built Slack’s Next-Generation EC2 Platform

Slack's engineering team describes Shipyard, their next-generation EC2 platform built around immutable infrastructure principles. Rather than continuously updating long-lived instances with Chef, Shipyard treats EC2 instances as deployable artifacts using layered AMIs. A shared 'slack-zero' golden base image provides OS hardening, networking, monitoring, and security agents, while service teams build on top of it. AWS Image Builder replaces Packer for baking images, with EventBridge and Lambda triggering downstream pipelines automatically. Deployments use progressive rollouts via Gondola, their internal orchestrator, with metrics-based automated rollback. A component called The Reaper enforces instance lifecycle by replacing tainted or aged instances. An inventory system called Peekaboo provides real-time fleet visibility via AWS EventBridge, OpenSearch, and Lambda. The platform also includes Ship Quick, a developer testing workflow that validates cookbook changes on real infrastructure before merging. Secrets remain dynamic via Consul Template and Vault, making the system semi-immutable. Future work targets long-lived instances like data nodes and singleton services.

    #aws-ec2#chef
Jul 14•15m read time•From slack.engineering
Post cover image
Table of contents
What Shipyard ProvidesGolden Base Images: Introducing slack-zeroDeployments and Fleet UpdatesShared ResponsibilityA Caveat on ImmutabilityThe ReaperHow Do We Test Changes?What’s Next?
4.9K Impressions
Slack engineering's image
Slack engineering

The Slack Blog serves as a resource for teams and developers looking to make the most out of Slack, ...

98 Followers

•

239 Upvotes

Would you recommend this post?

Copy link
WhatsApp
Facebook
X
New Squad
  • © 2026 Daily Dev Ltd.
  • Guidelines
  • Explore
  • Tags
  • Sources
  • Squads
  • Leaderboard