886: AWS and IAC for Dummies with SST

Episode Summary

Executive Summary: The episode explores SST as a modern infrastructure-as-code platform that simplifies deploying and managing AWS and other cloud services using TypeScript, with automatic provisioning, environment handling, and a polished console. Scott shares real-world experience moving an app to AWS, while Wes probes scaling, dev workflow, and comparisons to traditional clickops and managed platforms. The discussion also highlights SST’s broad provider support, strong docs, and runtime resource linking.

Main Topics: What SST is and why it matters: SST is presented as a friendlier infrastructure-as-code layer that uses code to define cloud architecture, replacing manual AWS dashboard work with declarative configuration. Scott’s migration of Habit Path to AWS: Scott explains moving a real app from hobby hosting to AWS using SST, including VPCs, ECS, RDS, Lambda, SES, and Cloudflare DNS management. Developer experience and TypeScript-based config: The hosts emphasize that SST uses TypeScript, allowing normal JavaScript logic, secret handling, dev/prod branching, and direct resource composition in one config file. Console, logs, deploys, and GitHub automation: SST’s console provides visibility into resources, logs, issues, and deploys, and can auto-deploy from GitHub branches with minimal manual intervention. Runtime resource linking and tunneling: Beyond infrastructure definition, SST can expose resources to application code and provide secure shell/tunnel access to private services such as databases. Ecosystem breadth and provider support: The episode stresses SST’s support for many AWS services, Cloudflare, and 150+ providers, making it useful well beyond AWS-only workflows. Docs and onboarding: Both hosts praise SST’s documentation for walking users through AWS account setup, IAM, and environment configuration in a highly approachable way.

Key Arguments: SST reduces AWS complexity by letting developers define infrastructure in code instead of using the AWS console for every service and setting. Using TypeScript for infrastructure is a major advantage because it allows file reads, conditionals, env handling, and other normal programming patterns inside infra config. SST can provision many services from a single config, including VPCs, ECS clusters, RDS databases, Lambda apps, SES email, and Cloudflare DNS. The platform’s console improves observability by showing logs, issues, deploy history, and resource inventory in one place. Auto-deploy via GitHub and environment-specific behavior make SST practical for real applications, not just demos. Runtime resource linking lets app code safely access infrastructure resources across dev, staging, and production without hardcoding credentials or endpoints. SST’s provider ecosystem is broad enough to support AWS, Cloudflare, and even non-cloud products like Stripe, making it more flexible than a single-provider tool.

Data Points: Users on Habit Path: about 800 - Scott says the app now has real users, which motivates the move to more robust infrastructure. Cloud providers / providers supported: 150+ providers - Wes and Scott discuss SST’s broad ecosystem beyond AWS, including Cloudflare and other integrations. AWS services count in docs: 39 services - Scott notes he counted 39 AWS services listed in SST’s AWS docs. Pricing threshold: 350 active resources - SST console pricing begins charging above 350 active resources. Resource charge rate: 8.6 cents per resource - Scott cites SST console pricing for resources above the included threshold. Sentry trial offer: 2 months free - Sponsor mention for using Sentry via the Syntax referral link. Sentry coupon code: tasty treat - Sponsor promotion code mentioned during the ad read. YouTube subscriber milestone: 500,000 subscribers - Scott jokes the hosts will switch to NeoVim when the Syntax channel reaches this target. Aquaphor tub size: 14 oz - Wes references the size of the Aquaphor jar he uses for dry skin/lips. Aquaphor price: $15 - Scott mentions the U.S. price for a 14-ounce jar.

Pivotal Quotes: "It makes it way easier than ever having to deal with AWS services." — Scott Tolinsky: Scott summarizes his experience using SST to deploy on AWS and reduce dashboard complexity. "This is a nicer way to work with something like Terraform." — Wes Boss: Wes frames SST as an approachable infrastructure-as-code layer for developers who want to avoid manual AWS setup. "I feel very powerful with this." — Scott Tolinsky: Scott describes the confidence and flexibility SST gives him to manage real infrastructure without becoming an AWS specialist.

Implications: For listeners, SST lowers the barrier to serious cloud deployment, especially for JavaScript/TypeScript developers. It suggests infrastructure work is becoming more programmable, observable, and accessible without sacrificing control or portability.