umac-ai-ecs-migration

Run Prisma migrations against production RDS via ECS Fargate tasks.

2|Updated May 10, 2026
One-click install
npx skills add https://github.com/freedomw1987/tree_monstor --skill umac-ai-ecs-migration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: umac-ai-ecs-migration
Source: https://github.com/freedomw1987/tree_monstor/tree/main/skills/devops/umac-ai-ecs-migration
Command: npx skills add https://github.com/freedomw1987/tree_monstor --skill umac-ai-ecs-migration

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the issue of being unable to run Prisma migrations against a production RDS instance directly from local development machines due to security group or VPC restrictions, which blocks standard local migration workflows.

Core Features & Use Cases

  • ECS Fargate One-off Task Execution: Uses the existing UMAC AI backend task definition to run a temporary Fargate container for migration, eliminating the need to set up new infrastructure.
  • Secure Credential Management: Retrieves database connection strings from AWS Secrets Manager, avoiding hardcoded credentials or exposing the production database to external access.
  • Pre-defined Production Configuration: Includes exact, pre-validated parameters for the UMAC AI production stack (cluster, subnets, security groups, region) to eliminate configuration errors.
  • Use Case: When deploying a new version of the UMAC AI backend that requires a database schema update, use this Skill to run the required Prisma migration directly against the production RDS without compromising network security.

Quick Start

Use this skill to execute the required Prisma migration against the UMAC AI production RDS via an ECS Fargate task when local database access is unavailable.

Frequently Asked Questions about umac-ai-ecs-migration

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

FAQPage Schema
How do I run Prisma migrations on a production RDS instance without local access?

You can run Prisma migrations on production RDS without local access by executing a one-off ECS Fargate task within the same VPC. This approach applies database schema changes securely using pre-defined infrastructure parameters and AWS Secrets Manager for credentials.

Why does Prisma migration fail when my local machine cannot connect to the production RDS database?

Prisma migration fails locally because VPC or security group restrictions block external network access to the production RDS instance. To resolve this, you must execute the migration from within the VPC using an ECS Fargate one-off task.

How to execute a Prisma database schema update securely using ECS Fargate?

To execute a Prisma schema update securely using ECS Fargate, run a temporary container using the existing backend task definition. The container retrieves the database connection string from AWS Secrets Manager and applies the migration directly.

Can I use ECS Fargate to run database migrations if my production RDS is in a private subnet?

Yes, you can use an ECS Fargate one-off task to run Prisma migrations against an RDS instance in a private subnet. The task operates within the VPC using pre-configured subnets and security groups to ensure secure access.

Do I need to set up new AWS infrastructure to run a one-off Prisma migration task?

No, you do not need to set up new AWS infrastructure for a one-off Prisma migration task. The process utilizes the existing ECS backend task definition along with pre-validated parameters for the cluster, subnets, and security groups.

What is the best way to apply database schema changes to RDS without exposing the database to external networks?

The best way to apply schema changes without exposing the database is deploying an ECS Fargate one-off task. It executes Prisma migrations internally within the VPC, retrieving credentials from AWS Secrets Manager to maintain network security.