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

DevFeed: [Shipyard: How We Built Slack's Next-Generation EC2 Platform](<https://devfeed.tech/articles/shipyard-how-we-built-slack-s-next-generation-ec2-platform-150.md>)

Original publisher: [Read original article](<https://slack.engineering/shipyard-how-we-built-slacks-next-generation-ec2-platform/>)

Author: Archie Gunasekara

Published: 2026-07-14T16:10:08Z

Content type: article

Language: en

Sources: [Engineering at Slack](<https://devfeed.tech/sources/engineering-at-slack.md>)

Topics: [Amazon EC2](<https://devfeed.tech/topics/amazon-ec2.md>)

Tags: [aws](<https://devfeed.tech/tags/aws.md>), [containers](<https://devfeed.tech/tags/containers.md>), [deployment](<https://devfeed.tech/tags/deployment.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [migration](<https://devfeed.tech/tags/migration.md>), [platform](<https://devfeed.tech/tags/platform.md>), [slack](<https://devfeed.tech/tags/slack.md>), [uncategorized](<https://devfeed.tech/tags/uncategorized.md>)

## AI overview

Slack describes Shipyard, its next-generation EC2 platform, which uses deployable infrastructure artifacts, service-level deployment primitives, progressive rollouts, and automated safety mechanisms to modernize EC2 operations.

## Source excerpt

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...