Shipyard: How We Built Slack’s Next-Generation EC2 Platform
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…
Score breakdown
- Technical depth52
- Practical value90
- Originality100
- Writing quality100
- Source reputation85
- Recency7
- External engagement0
- On-site engagement0
More like this
Stripe Engineering53
Effectively using AWS Reserved Instances
unknown·11 min read
Slack Engineering72
From SSH to REST: A Security-Driven Modernization of Slack’s EMR Data Pipelines
Mahendran Vasagam·unknown·14 min read
Slack Engineering65
Slack AI: The Path to Multi-Cloud
Shaurya Kethireddy·unknown·15 min read
Slack Engineering53
From Custom to Open: Scalable Network Probing and HTTP/3 Readiness with Prometheus
Carlo Preciado·unknown·4 min read
Engradar shows a summary and links to the original article. The full article is hosted on slack.engineering.