AWS Infrastructure Coding Rules

awscloudinfrastructuredevops

Standards for writing and managing AWS infrastructure code and configurations

Целевые файлы

Файл	Формат
.cursorrules	plaintext
CLAUDE.md	markdown

Содержимое

Define all AWS resources as Infrastructure as Code (CDK, Terraform, or CloudFormation). Never create or modify resources manually in the AWS Console in production. Apply least-privilege IAM: grant only the specific actions and resources required. Never use wildcard (*) actions or resources in production IAM policies. Enable CloudTrail in all regions to audit API calls and detect unauthorized changes. Store secrets in AWS Secrets Manager or SSM Parameter Store (SecureString), not env vars. Tag all resources with at minimum: Environment, Project, Owner, and CostCenter tags. Use VPC with private subnets for databases and internal services; only expose what is needed. Enable versioning and replication on S3 buckets storing critical data. Use AWS WAF in front of public-facing ALBs and CloudFront distributions. Set lifecycle policies on S3 buckets and CloudWatch Logs to manage storage costs. Use multi-AZ deployments for RDS and ElastiCache in production environments. Enable GuardDuty and Security Hub in the ${aws_account} account for threat detection. Review and rotate IAM access keys every ${rotation_days} days; prefer IAM roles over keys.

Переменные

ID	Метка	По умолчанию	Варианты
aws_account	AWS account name or ID	production	—
rotation_days	Key rotation period in days	90	—

CLI

npx mindaxis apply aws-rules --target cursor --scope project

Используется в паках

IaC Automation

Infrastructure defined in code

Открыть пак →

← Правила