Enforce Consistent Resource Naming in AWS SAM Templates

The problem If you've worked with AWS SAM templates long enough, you've probably run into messy or inconsistent resource names. These inconsistencies aren’t just an eyesore — they can cause confusion in large teams and complex deployments. The solution That’s why I created sam-resource-name-linter — a simple CLI tool to enforce consistent, configurable naming conventions for your AWS SAM resources. It's a tool written in Javascript that scans your template.yaml files and checks the logical resource names against a naming convention that you define. It was built to help teams maintain readable, standardized CloudFormation templates — especially in larger serverless projects where consistency can quickly fall apart. Key Features ✅ Works out of the box with sensible defaults ⚙️ Fully configurable naming conventions (regex-based)

May 2, 2025 - 04:13

Enforce Consistent Resource Naming in AWS SAM Templates

The problem

If you've worked with AWS SAM templates long enough, you've probably run into messy or inconsistent resource names. These inconsistencies aren’t just an eyesore — they can cause confusion in large teams and complex deployments.

The solution

That’s why I created sam-resource-name-linter — a simple CLI tool to enforce consistent, configurable naming conventions for your AWS SAM resources.

It's a tool written in Javascript that scans your template.yaml files and checks the logical resource names against a naming convention that you define.

It was built to help teams maintain readable, standardized CloudFormation templates — especially in larger serverless projects where consistency can quickly fall apart.

Key Features

✅ Works out of the box with sensible defaults
⚙️ Fully configurable naming conventions (regex-based)