aws-deployment

Automate AWS deployments across EC2, ECS, S3, and CloudFront with a six-phase lifecycle.

11|2|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/porcupine-md/jonggrang --skill aws-deployment-porcupine-md
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aws-deployment
Source: https://github.com/porcupine-md/jonggrang/tree/main/skills/library/deploy/aws-deployment
Command: npx skills add https://github.com/porcupine-md/jonggrang --skill aws-deployment-porcupine-md

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Deploying applications to AWS can be error-prone and hard to scale without a disciplined, repeatable process. This Skill provides a structured six-phase Deployment Lifecycle Contract to ensure authentication, building artifacts, provisioning resources, deploying changes, validating outcomes, and handling rollbacks across AWS services (EC2, ECS, S3, CloudFront, Cloud Run).

Core Features & Use Cases

  • Six-phase deployment lifecycle guidance for AWS (Authentication, Build, Provisioning, Deploy, Checking, Update/Rollback).
  • Support for common resources such as EC2, ECS, S3, and CloudFront, including containerized and static-site deployments.
  • Guardrails and checklists that enforce secure credentials, proper artifact handling, and reliable rollback strategies.

Quick Start

Review the six deployment phases and start by verifying AWS credentials, then progress through Build, Provisioning, Deploy, and Validation to deploy your app to AWS.

Frequently Asked Questions about aws-deployment

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

FAQPage Schema
How do I automate AWS deployments for EC2 and ECS without manual errors?

Automate AWS deployments using a structured six-phase lifecycle with built-in guardrails. This enforces authentication, artifact preparation, resource provisioning, deployment execution, health checks, and rollback capabilities for EC2 and ECS environments.

What is the best way to deploy a static site to AWS S3 and CloudFront with rollback support?

Deploy static sites to AWS S3 and CloudFront using a structured lifecycle that includes built-in rollback strategies. The process enforces secure credential checks, resource provisioning, and health validations to ensure reliable static site delivery.

Can I use this deployment process for staging and production environments across containerized apps?

Containerized app deployments are supported across development, staging, and production environments. The deployment lifecycle applies consistent guardrails, artifact handling, and health checks to ensure reliable rollouts for containerized workloads.

Why should I use a structured lifecycle for AWS cloud deployments instead of ad-hoc scripts?

A structured AWS deployment lifecycle prevents scaling issues and manual errors by enforcing checklists across authentication, provisioning, and validation phases. Built-in guardrails ensure secure credentials and reliable rollback strategies for cloud infrastructure.

How do I handle rollbacks when an AWS deployment fails health checks?

Handle AWS deployment failures through the built-in update and rollback phase. If health checks fail during the validation phase, the lifecycle guardrails trigger rollback capabilities to restore the previous stable state.

Do I need to prepare artifacts before provisioning resources for an AWS cloud deployment?

Artifact preparation is required before resource provisioning in the AWS deployment lifecycle. The structured process enforces a strict phase order: authentication, build, provisioning, deploy, checking, and update or rollback.