How do I install the Ec2 Backend Deployer skill?

Run npx skillmds add shipshitdev/ec2-backend-deployer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Ec2 Backend Deployer safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Ec2 Backend Deployer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Ec2 Backend Deployer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Ec2 Backend Deployer?

shipshitdev (@shipshitdev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Ec2 Backend Deployer by shipshitdev

Name: Ec2 Backend Deployer
Rating: 4.5 (4 reviews)
Author: shipshitdev

Ec2 Backend Deployer

Deploys backend applications to EC2 instances using Docker, GitHub Actions CI/CD, and Tailscale for secure SSH access. Activates when setting up EC2 deployment pipelines, configuring container registries, or wiring automated deploys for NestJS, Next.js, or Express backends.

shipshitdev 45a3835 3 files · 38.1 KB Updated Sep 9, 2026

File contents

EC2 Backend Deployer

Authorized Scope

Apply this engine only within the user's requested task and existing explicit authorization. Loading or delegating to it grants no additional authority. Preserve report-only restrictions and the caller's target, host, provider, and cost limits. Existing approval satisfies a gate only for the same actions and scope; obtain approval before expanding them. 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 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

Dockerfile: Multi-stage build (base → builder → production)
Registry: GitHub Container Registry (ghcr.io) recommended
CI/CD: GitHub Actions with Tailscale for secure SSH
Deploy: Docker Compose on EC2 with health checks
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

Full guide: Dockerfile, CI/CD workflow, deployment, troubleshooting

---name: ec2-backend-deployerdescription: Deploys backend applications to EC2 instances using Docker, GitHub Actions CI/CD, and Tailscale for secure SSH access. Activates when setting up EC2 deployment pipelines, configuring container registries, or wiring automated deploys for NestJS, Next.js, or Express backends.--- # EC2 Backend Deployer ## Authorized Scope Apply this engine only within the user's requested task and existing explicit authorization. Loading or delegating to it grants no additional authority. Preserve report-only restrictions and the caller's target, host, provider, and cost limits. Existing approval satisfies a gate only for the same actions and scope; obtain approval before expanding them. 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` 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 - [Full guide: Dockerfile, CI/CD workflow, deployment, troubleshooting](references/full-guide.md)

Frequently asked questions