All skills

Advises on Amazon RDS open-source engines (MySQL, MariaDB, PostgreSQL) for instance creation, upgrade planning, commitment pricing, proxy evaluation, and Blue/Green deployments. Handles any RDS MySQL, MariaDB, or PostgreSQL question, including create a production-ready RDS MySQL instance, provision an RDS PostgreSQL database, run the RDS upgrade advisor for my RDS MySQL instance, what are my upgrade options, upgrade RDS MariaDB from 10.6 to the latest version, should I buy reserved instances or a savings plan for db.r7g.2xlarge RDS MySQL, change a VARCHAR to INT column on RDS MySQL 8.0 with Blue/Green, and does RDS Proxy help when PgBouncer already runs in transaction mode. Covers instance creation with production best practices, describe-db-instances and describe-db-engine-versions upgrade-target workflow, live prechecks via SSM or direct connection, RI versus DSP commitment pricing, RDS Proxy versus PgBouncer, and Blue/Green lifecycle with binlog replay compatibility.

Use this Skill: https://skilld.dev/gh/aws/agent-toolkit-for-aws/rds-oss

This session only. Nothing lands on disk.

referencesbluegreen-ddl-mysql.md

≈574 tokens on demand. Your agent reads this file only when SKILL.md points to it.

MySQL/MariaDB DDL Compatibility with Blue/Green Replication

Blue/Green uses binlog replication (ROW format) to keep green in sync with blue. Some DDL operations break this replication.

Safe Operations (replication continues)

Operation Notes
ADD COLUMN at end of table Replication continues. New column is NULL on blue rows.
ADD INDEX / DROP INDEX Index-only changes don't affect row format.
OPTIMIZE TABLE Internally does ALTER TABLE FORCE + ANALYZE. Safe on green.
ANALYZE TABLE Statistics refresh only. No schema change.
ALTER TABLE ... ENGINE=InnoDB Table rebuild. Safe on green.
Partition reorganization Safe if partitioning schema remains compatible.

Replication-Breaking Operations (proceed to switchover immediately)

Operation Why It Breaks What To Do
MODIFY COLUMN (type change) Row format changes. Binlog events can't be applied. Apply DDL, then switchover immediately. Do NOT wait.
CHANGE COLUMN (rename + type) Same as MODIFY — row format mismatch. Apply DDL, then switchover.
ADD COLUMN ... AFTER col Column position changes. Binlog column index mismatch. Use ADD COLUMN at end instead, or switchover immediately.
RENAME TABLE Binlog references old table name. Switchover immediately after rename.
RENAME COLUMN Binlog uses column index, but metadata mismatch can cause issues. Switchover immediately.

Operations That May Fail Switchover

Operation Risk
DROP COLUMN on green Blue still writes to that column. Replication fails. Switchover may fail.
Change AUTO_INCREMENT value Sequence gaps or conflicts during switchover.
Add UNIQUE constraint on green Blue may have duplicates that violate the constraint.

Foreign Key Handling

Blue/Green handles foreign keys natively — no need to drop/recreate them as with gh-ost. DDL on tables with foreign keys works as expected on the green environment.

Best Practice

  1. Apply all DDL changes on green in a single session
  2. If any change breaks replication, proceed to switchover immediately
  3. Do NOT apply further changes on blue after replication breaks
  4. Verify schema on green before initiating switchover

Source: SKILL.md on GitHub

No alerts3mo3 checks · Risk SAFE
  • Gen Agent Trust Hub3mo

    This skill is a specialized advisor for Amazon RDS open-source engines, providing workflows for resource provisioning, upgrades, and cost optimization. It adheres to security best practices by enforcing encryption, multi-factor availability, and secure credential management via AWS Secrets Manager. No malicious patterns were identified.

  • Socket3mo

    No alerts

  • Snyk3mo

    Risk: LOW · No issues

Signed by skilld at aea59f3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 3 months ago
version
1

README badge

README badge for aws/agent-toolkit-for-aws/rds-oss