SST Framework (Ion)

SST Ion: SST v3 (Ion) replaced the AWS CDK backend with Pulumi/Terraform. Configuration is in sst.config.ts using a simpler component-based API. Ion supports Cloudflare Workers alongside AWS, has no CloudFormation, and benefits from Pulumi's state management. Deployments are typically faster than v2's CloudFormation-based approach.

sst.config.ts: Example: export default $config({ app(input) { return { name: 'my-app', removal: input.stage === 'production' ? 'retain' : 'remove' } }, async run() { const bucket = new sst.aws.Bucket('MyBucket'); const api = new sst.aws.Function('MyApi', { handler: 'src/api.handler', link: [bucket] }); return { api: api.url }; } }). The run() function uses SST's component primitives.

SST Live Lambda: Run sst dev — SST deploys a stub Lambda that tunnels invocations to your local machine via IoT Core. Your local code handles the request and returns the response. Full IDE debugger support, instant code changes, and real AWS services (actual DynamoDB, S3, etc.) rather than emulators. This is a key SST differentiator versus LocalStack.

SST link: new sst.aws.Function('Api', { handler: 'src/handler.ts', link: [bucket, table] }). SST automatically creates IAM policies granting the function access to the bucket and table, and injects typed environment bindings accessible via import { Resource } from 'sst' — Resource.MyBucket.name is typed and available at runtime with no manual env var setup.

SST Console: Available at console.sst.dev. Connects to your AWS account via the SST app. Features: live log streaming from Lambda functions, error tracking with source maps, function invocation UI, and multi-stage/multi-account views. In sst dev mode, logs from local Live Lambda also appear in the Console. It replaces manual CloudWatch log searching.