Discover · slack.engineering

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

Slack Engineering slack.engineering

Over the past few years, we’ve been on a journey to modernise how we run Amazon Elastic Compute Cloud (EC2) instances at Slack.

In our first post, Advancing Our Chef Infrastructure, we shared how we moved from a single Chef stack to a resilient, multi-stack setup with versioned cookbook deployments and safer promotion workflows. This afforded us far more reliability and operational control across tens of thousands of EC2 instances.

More ways to use this
Open on another device
Scan this QR code to open the same public page

Scan to open this page. Your saved notes and account access are not included.

Download QR code

Open the page link

Names and references

  1. Generation — person
  2. Platform — person

In the piece

Keep going

Each of these is read from what this estate already kept: the feed a piece came through, the publisher behind it, the credits and topics the publisher printed. None of it is a recommendation, an identity or a record kept anywhere else.

Also from Slack Engineering

  1. Agentic Testing: Where Agents Fit in the E2E Testing StackSergii Gorbachov slack.engineering
  2. Slack AI: The Path to Multi-CloudShaurya Kethireddy slack.engineering
  3. From SSH to REST: A Security-Driven Modernization of Slack’s EMR Data PipelinesMahendran Vasagam slack.engineering
  4. Managing context in long-run agentic applicationsDominic Marks slack.engineering
  5. From Custom to Open: Scalable Network Probing and HTTP/3 Readiness with PrometheusCarlo Preciado slack.engineering
  6. How Slack Rebuilt Notifications 📣Frances Coronel slack.engineering