Generate an AWS CDK Stack from a Plain-English Description
The AWS CDK lets you define cloud infrastructure in real code, but the API surface is enormous. Describe what you need in plain English and let Claude translate it into a deployable stack.
Generate an AWS CDK stack in TypeScript for a serverless API. I need an API Gateway backed by a Lambda function and a DynamoDB table. The Lambda should have read/write access to the table. Enable CORS for https://myapp.com only.
Claude produces a complete CDK stack with proper constructs, automatic IAM grants, and environment variable wiring — no manual policy documents required:
const table = new dynamodb.Table(this, 'UsersTable', {
partitionKey: { name: 'id', type: dynamodb.AttributeType.STRING },
billingMode: dynamodb.BillingMode.PAY_PER_REQUEST,
removalPolicy: RemovalPolicy.RETAIN,
});
const fn = new lambda.NodejsFunction(this, 'ApiHandler', {
environment: { TABLE_NAME: table.tableName },
});
table.grantReadWriteData(fn); // IAM policy generated automatically
Add more resources incrementally without reading through pages of AWS docs:
Add an SQS queue that triggers the Lambda asynchronously for background jobs. The queue should have a dead-letter queue after 3 failed attempts.
Ask Claude to include S3 buckets with lifecycle rules, CloudFront distributions, RDS instances in a VPC, or EventBridge rules — each described in plain English, generated as idiomatic CDK.
cdk diff # preview changes before deploying
cdk deploy
Describe your cloud architecture in English; deploy it in code.
Log in to leave a comment.
Set up Claude Code as an automated reviewer in your CI pipeline — on every pull request, it reads the diff, checks for bugs, security issues, missing tests, and convention violations, then posts its findings as a PR comment. Your human reviewers get a head start because the obvious issues are already flagged before they look.
Before deploying, tell Claude to read your project — migrations, environment variables, queue workers, scheduled tasks, caching, third-party integrations — and generate a deployment checklist that's specific to your app. Not a generic "did you run migrations?" list, but one that knows YOUR infrastructure and catches the things YOUR deploy can break.
Instead of writing a README from memory or copying a template, tell Claude to read your project and generate one that's actually accurate — real setup instructions from your config, real architecture from your directory structure, real API examples from your routes, and real prerequisites from your dependency files.