ameritas-cloudformation

Generate and standardize CloudFormation and SAM templates with Ameritas naming conventions.

Updated Aug 26, 2025
One-click install
npx skills add https://github.com/ksinha49/mcp-server --skill ameritas-cloudformation
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ameritas-cloudformation
Source: https://github.com/ksinha49/mcp-server/tree/main/.claude/skills/cloudformation-engg
Command: npx skills add https://github.com/ksinha49/mcp-server --skill ameritas-cloudformation

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires PyYAML, and includes scripts (resource) and assets (resource) components.

What problem does it solve?

This skill provides standardized generation and editing of CloudFormation and SAM templates that align with Ameritas naming conventions and architectural patterns, reducing drift and accelerating secure deployments.

Core Features & Use Cases

  • Template scaffolding that enforces header, Globals, and resource naming conventions
  • Support for CloudFormation and SAM templates, including nested stacks, Lambda, Step Functions, EC2, ALB, Auto Scaling, SQS, SNS, DynamoDB, and EventBridge
  • Consistent patterns for resource names and deployments across environments (development to production)
  • Use Case: Create a new SAM template for a Lambda-backed API with proper VPC configuration and tags

Quick Start

Create a new CloudFormation/SAM template using the standard header, then validate against Ameritas conventions.

Frequently Asked Questions about ameritas-cloudformation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a SAM template for a Lambda function that follows strict naming conventions?

To create a SAM template with strict naming conventions, you can use a scaffolding skill that automatically applies standardized headers, Globals, and resource naming patterns for Lambda and other AWS resources. This enforces architectural guidelines during initial template generation.

Can I use CloudFormation nested stacks with standardized parameter blocks and metadata?

Yes, CloudFormation nested stacks can be generated with standardized parameter blocks and metadata requirements. The skill ensures nested stack configurations align with specific architectural patterns, reducing configuration drift across development and production environments.

What is the best way to refactor existing CloudFormation templates to comply with corporate naming standards?

The best way to refactor existing CloudFormation templates is to apply an automated standardization process that validates and updates header formats, naming patterns, and resource definitions. This ensures existing stacks align with required architectural guidelines without manual editing.

Does this CloudFormation scaffolding tool support infrastructure resources like DynamoDB, SQS, and EventBridge?

Yes, this CloudFormation scaffolding tool supports infrastructure resources including DynamoDB, SQS, SNS, EventBridge, Step Functions, EC2, ALB, and Auto Scaling. It enforces consistent naming conventions and template structures across all supported AWS resource types.

Why do my infrastructure-as-code templates have configuration drift across different environments?

Infrastructure-as-code templates experience configuration drift when they lack enforced standardization for naming conventions and parameter blocks. Generating templates with predefined architectural patterns ensures consistent deployments from development through production environments.

Do I need PyYAML installed to generate CloudFormation templates with standardized headers?

Yes, PyYAML is a required dependency to generate and standardize CloudFormation templates. It processes the YAML structure to apply consistent header formats, Globals, and naming patterns during template scaffolding and refactoring.