aws-serverless-deployment
Audited by Runlayer on Mar 6, 2026
Tool passed security scan
Risky tool definition detected
--- ## Best Practices ### Do - Use TypeScript — type checking catches errors at synthesis time, before any AWS API calls - Prefer L2 constructs and `grant*` methods over L1 and raw IAM statements - Never hardcode resource names — always reference generated names (`table.tableName`, `queue.queueUrl`) - Separate stateful and stateless resources into different stacks; enable termination protection on stateful stacks - Commit `cdk.context.json` to version control — it caches VPC/AZ lookups for deter
Tool passed security scan
Risky tool definition detected
Tool: aws-serverless-deployment/references/sam-project-setup.md [2/2] Description: for images larger than 250 MB to reduce cold starts ## Configuration Management ### samconfig.toml Use environment-specific sections: ```toml [default.deploy.parameters] stack_name = "my-serverless-app" region = "us-east-1" capabilities = "CAPABILITY_IAM" [dev.deploy.parameters] stack_name = "my-app-dev" parameter_overrides = "Environment=dev LogLevel=DEBUG" [prod.deploy.parameters] stack_name = "my-app-prod" para
Risky tool definition detected
**Start with one new stack in CDK** — a supporting resource (DynamoDB table, SQS queue, event bus) that your SAM functions reference via SSM parameters or CloudFormation exports 2.
Tool passed security scan
Passed Files (2)Click to expand
Tool passed security scan
Tool passed security scan