mcpField
E
ec2-backend-deployer

ec2-backend-deployer

github.com/shipshitdevCloud & DevOps38172 installsUpdated 2d ago
Repository

About ec2-backend-deployer

A skill for planning and carrying out authorized backend deployments to AWS EC2. It covers Docker-based builds, registry and CI/CD setup, secure host access, health checks, and approval boundaries for external changes.

Key features

  1. 01Plan scoped EC2 deployments
  2. 02Configure Docker and CI pipelines
  3. 03Use registries and secure SSH access
  4. 04Verify deployments with health checks
  5. 05Require approval for specified changes

Use cases

  1. 01Setting up backend CI/CD for EC2
  2. 02Preparing a Docker-based deployment
  3. 03Reviewing a deployment plan before execution

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/shipshitdev/skills --skill ec2-backend-deployer

After installing, type/ec2-backend-deployerin Claude Code to confirm it loaded.

Bundled filesplugin.jsonreferences/full-guide.md

Details

From the project README

EC2 Backend Deployer

Authorized Scope

Act only within the user's request and existing approval; loading this skill grants no new authority. Keep report-only requests report-only, honor the caller's target, host, provider, and cost limits, ask before expanding scope, and forward these limits to delegates.

Contract

Inputs:

  • Target repository, deployment goal, and approved AWS account/environment
  • Existing Docker, registry, CI, and host-access configuration

Outputs:

  • Scoped deployment configuration or a reviewed deployment plan
  • Health-check evidence when deployment is authorized

Creates/Modifies:

  • Docker and CI configuration within the requested setup
  • Remote deployment state only when the target and operation are authorized

External Side Effects:

  • Registry, CI, SSH, and AWS calls required for the approved deployment

Confirmation Required:

  • Before creating billable infrastructure, changing secrets, or deploying outside the explicitly approved target and action
  • Before replacing existing deployment configuration beyond the requested change

Delegates To:

  • deploy-app for the repository's release and deployment gates

When to Use

Use when you're:

  • Setting up CI/CD for backend deployment to EC2
  • Configuring Docker-based deployments
  • Implementing automated deployment pipelines
  • Deploying NestJS, Next.js, or Express backends
  • Setting up container registries and image management
  • Configuring secure EC2 access (Tailscale)

Quick Workflow

  1. Dockerfile: Multi-stage build (base → builder → production)
  2. Registry: GitHub Container Registry (ghcr.io) recommended
  3. CI/CD: GitHub Actions with Tailscale for secure SSH
  4. Deploy: Docker Compose on EC2 with health checks
  5. Verify: Health endpoint + deployment verification

Key Components

Docker
  • Multi-stage builds for smaller images
  • Non-root user for security
  • HEALTHCHECK for container orchestration
  • BuildKit secrets for sensitive data
GitHub Actions
  • docker/build-push-action for image building
  • tailscale/github-action for secure access
  • appleboy/ssh-action for deployment
EC2
  • Docker Compose v2 required
  • Health check verification
  • Rollback procedures

References

Comments

Markdown supported