resource-naming
AWS Resource Naming Conventions
This is a reference pattern. Learn from the approach, adapt to your context — don't copy verbatim.
Status: 🔴 CRITICAL PATTERN
Category: Infrastructure
Applies To: All AWS resources across all projects
Overview
This document defines the standard naming conventions for AWS resources. Following these patterns ensures:
- Clear project ownership
- Environment separation and safety
- Consistent resource identification
- Easy filtering and management in AWS Console
- Prevention of resource conflicts and data corruption
More from loxosceles/ai-dev
static-frontend-hosting
S3 + CloudFront + Lambda@Edge for low-cost global hosting with edge authentication. Apply when setting up frontend hosting infrastructure.
65github-actions-oidc-aws
Secure GitHub Actions to AWS authentication using OIDC without long-lived credentials. CRITICAL PATTERN. Apply when setting up CI/CD pipelines that deploy to AWS.
54code-review
Multi-perspective code review strategy covering architecture, security, performance, and quality. Follow when reviewing code or analyzing changes.
52frontend-code-quality
Essential guidelines for clear, maintainable frontend code. Follow when writing or reviewing frontend components, composables, or pages.
52command-execution
Guidelines for executing commands and running scripts. Follow when running shell commands, installing packages, or using project scripts.
52cdk-bootstrap-configuration
CDK synth-time configuration pattern without context caching. Apply when working on CDK infrastructure code or adding new configuration parameters.
51