--- title: "Shipyard: How We Built Slack’s Next-Generation EC2 Platform" url: https://daily.dev/posts/shipyard-how-we-built-slack-s-next-generation-ec2-platform-gu06w8ca0 source_url: https://slack.engineering/shipyard-how-we-built-slacks-next-generation-ec2-platform type: article source: "Slack engineering" published: 2026-07-14T16:15:48.542Z updated: 2026-07-15T12:24:17.268Z tags: ["aws-ec2", "chef"] reading_time: 15 upvotes: 2 comments: 0 language: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Shipyard: How We Built Slack’s Next-Generation EC2 Platform **[Slack engineering](https://daily.dev/sources/slack)** · 15 min read · 2 upvotes · 0 comments ## Summary 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. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Similar posts on daily.dev - [Slack Enhances Chef Infrastructure to Improve Safety and Reduce Blast Radius in Deployments](https://daily.dev/posts/slack-enhances-chef-infrastructure-to-improve-safety-and-reduce-blast-radius-in-deployments-bbqstolyp) · InfoQ · 0 upvotes · 0 comments - [The Pipeline That Thinks: Building an AI-Powered DevSecOps Pipeline on AWS EKS](https://daily.dev/posts/the-pipeline-that-thinks-building-an-ai-powered-devsecops-pipeline-on-aws-eks-kztltafof) · Cloud Native Now · 0 upvotes · 0 comments --- Tags: [#aws-ec2](https://daily.dev/tags/aws-ec2), [#chef](https://daily.dev/tags/chef) [View this post on daily.dev](https://daily.dev/posts/shipyard-how-we-built-slack-s-next-generation-ec2-platform-gu06w8ca0)