Castle On A Cloud: The Github Story
summary
GitHub runs most internal apps across roughly 350 AWS instances and about 250 Heroku dynos and balances EC2, RDS, EBS and S3 with concrete tooling: IAM roles plus STS and instance profiles for per‑env credentials, VPCs with Direct Connect to the colo, resource tagging for cost reporting, and a Campfire+Hubot driven chat ops surface that can provision or terminate servers. The urgent problem is S3 bucket limits solved by consolidating environments into single buckets with prefixes and cross‑account write‑only dropboxes.
AI-written summary · about
chapters (4)
related talks
01h 06mHow GitHub delivers GitHub using GitHub
45mHow Github uses GitHub to develop GitHub
20mKeynote: Kubernetes at GitHub
31mGitHub as a self-sustaining product for large-scale environments
38mBuilding a Cloud Native Culture in an Enterprise - Deep Kapadia & Tony Li
21mAvoiding That $1M Dollar AWS Bill - Mark Michael, Glenn Oppegard
18mShipping at Scale: ChatOps at GitHub #bbuzz
03mAWS Community Spotlight: Amazon CodeCatalyst
