sagerstack:deploy-aws

Automate AWS infrastructure deployment with Terraform and GitHub Actions.

Updated Feb 9, 2026

Search Tags:#ci/cd #deployment #aws #infrastructure as code #cloud #terraform

Ready to run

npx skills add https://github.com/sagerstack/agentic-sdlc --skill sagerstack-deploy-aws

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: sagerstack:deploy-aws
Source: https://github.com/sagerstack/agentic-sdlc/tree/main/.claude/skills/sagerstack-deploy-aws
Command: npx skills add https://github.com/sagerstack/agentic-sdlc --skill sagerstack-deploy-aws

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the deployment and management of AWS infrastructure using Terraform, ensuring consistency and repeatability across environments.

Core Features & Use Cases

Infrastructure as Code: Define and manage your AWS resources (Lambda, S3, SQS, Secrets Manager, EKS) using Terraform.
Environment Management: Supports separate configurations for local development (LocalStack) and production (AWS).
CI/CD Integration: Facilitates setting up automated deployment pipelines with GitHub Actions.
Use Case: You need to deploy a new microservice to AWS, including its Lambda functions, S3 buckets for storage, and an SQS queue for asynchronous processing. This Skill can set up all the necessary Terraform configurations and even generate a basic GitHub Actions workflow for deployment.

Quick Start

Use the sagerstack:deploy-aws skill to set up a Terraform project structure for AWS.

Frequently Asked Questions about sagerstack:deploy-aws

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

FAQPage Schema

How do I deploy AWS infrastructure with Terraform using GitHub Actions?▼

You can deploy AWS infrastructure with Terraform by using this Skill to generate configurations and integrate GitHub Actions workflows, automating the management of services like Lambda, S3, SQS, and EKS through CI/CD pipelines.

What is the best way to manage environment separation for local and production AWS deployments in Terraform?▼

Managing environment separation for AWS deployments is handled by enforcing infrastructure-as-code principles with distinct configurations, supporting local development via LocalStack and production environments on AWS.

Can I use this to set up AWS resources like S3, SQS, and Secrets Manager together?▼

Yes, you can set up AWS resources like S3, SQS, and Secrets Manager together. The Skill uses reusable Terraform modules to define and manage these services while following specific resource and variable naming conventions.

Does this Terraform configuration support deploying microservices to AWS Lambda and EKS?▼

Yes, the Terraform configuration supports deploying microservices to AWS Lambda and EKS. It automates the setup of necessary resources including compute, storage like S3, and asynchronous processing components like SQS.

How do I enforce infrastructure-as-code naming conventions for AWS resources in Terraform?▼

To enforce infrastructure-as-code naming conventions for AWS resources, the Skill utilizes reusable Terraform modules that follow specific naming rules for resources and variables, ensuring consistency across your deployments.