database-migration-service-expertise
AWS Database Migration Service (DMS) operational review and troubleshooting
aws · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add aws/tools-for-devops-agent --skill database-migration-service-expertise技能说明
name: database-migration-service-expertise description: AWS Database Migration Service (DMS) operational review and troubleshooting skill. Conducts best practices validation, health assessments, performance diagnostics, cost optimization reviews, and migration cutover guidance. Triggers on requests like "DMS review", "DMS health check", "DMS troubleshooting", "migration assessment", "DMS best practices audit", "DMS cost optimization", "replication instance review", "CDC latency issue", or "DMS task failure". metadata: author: tabhiman version: "1.0.0" aws-devops-agent-skills.agent-types: "Chat tasks, Evaluation" aws-devops-agent-skills.aws-services: "AWS Database Migration Service" aws-devops-agent-skills.technical-domains: "Database"
AWS DMS Operational Review & Troubleshooting
Conduct comprehensive operational reviews, best practices validation, troubleshooting, and cost optimization assessments for AWS Database Migration Service (DMS) environments aligned with AWS Well-Architected principles.
When to Use
Activate this skill when the user asks to:
- Review, audit, or assess DMS configurations
- Check DMS best practices compliance
- Troubleshoot DMS task failures, latency, or connectivity issues
- Evaluate DMS cost optimization opportunities
- Plan or execute a database migration cutover
- Assess DMS version deprecations and upgrade paths
- Run a pre-migration assessment
- Evaluate DMS Serverless vs provisioned suitability
- Investigate data validation mismatches
- Review DMS homogeneous data migration options
Step 1: Identify Target Resources
Ask the user which DMS resources to review. Accept:
- Specific replication instance names and regions
- Specific replication task identifiers
- "all instances" in a specific region
- "all instances in all regions"
Query AWS APIs to discover DMS resources:
- List replication instances across the configured account regions
- List replication tasks and their states
- List endpoints and connectivity status
Step 2: Collect DMS Configuration
For EACH replication instance and its associated tasks, gather the following data using AWS APIs.
2.1 Replication Instance Config
Engine version, instance class, Multi-AZ, storage, public accessibility, KMS encryption, auto-upgrade, VPC/subnet configuration, pending maintenance actions.
aws dms describe-replication-instances --profile <profile> --region <region>
aws dms describe-pending-maintenance-actions --profile <profile> --region <region>
2.2 Replication Tasks
Task identifiers, status, migration type, table mappings, task settings, CDC start positions, last failure messages, stop reasons, replication task statistics.
aws dms describe-replication-tasks --profile <profile> --region <region>
2.3 Endpoints
Endpoint identifiers, types (source/target), engine names, SSL mode, connection status, Secrets Manager integration, security group configurations.
aws dms describe-endpoints --profile <profile> --region <region>
aws dms describe-connections --filter Name=endpoint-arn,Values=<endpoint-arn> --profile <profile> --region <region>
2.4 Table Statistics
Per-table state, row counts, validation state, error rows, DDL counts.
aws dms describe-table-statistics --replication-task-arn <task-arn> --profile <profile> --region <region>
2.5 DMS Serverless (if applicable)
Replication configs, serverless replications, DCU utilization.
aws dms describe-replication-configs --profile <profile> --region <region>
aws dms describe-replications --profile <profile> --region <region>
2.6 Version and Deprecation Data
Available engine versions, pending maintenance actions, AWS Health events.
aws dms describe-orderable-replication-instances --query "OrderableReplicationInstances[*].EngineVersion" --profile <profile> --region <region>
aws health describe-events --filter '{"services":["DMS"],"eventTypeCategories":["scheduledChange"]}' --profile <profile> --region us-east-1
Note: AWS Health API is a global service and must be called with
--region us-east-1regardless of where DMS resources are deployed.
Step 3: Collect Observability Data (7-Day Historical)
3.1 CloudWatch Metrics (7 days)
Replication Instance Metrics (namespace: AWS/DMS):
- CPUUtilization (Average, Maximum)
- FreeableMemory (Average, Minimum)
- SwapUsage (Average, Maximum)
- DiskQueueDepth (Average, Maximum)
- ReadIOPS / WriteIOPS (Average, Maximum)
- ReadLatency / WriteLatency (Average, Maximum)
- NetworkTransmitThroughput (Average)
- NetworkReceiveThroughput (Average)
Task Metrics (namespace: AWS/DMS):
- CDCLatencySource (Average, Maximum)
- CDCLatencyTarget (Average, Maximum)
- CDCIncomingChanges (Average, Maximum)
- CDCChangesMemorySource (Average, Maximum)
- CDCChangesDiskSource (Maximum)
- CDCChangesDiskTarget (Maximum)
- FullLoadThroughputBandwidthTarget (Average)
- FullLoadThroughputRowsTarget (Average)
DMS Serverless (namespace: AWS/DMS, if applicable):
- ServerlessTotalCapacityUnits (Average, Maximum)
3.2 CloudWatch Logs (7 days)
Query task logs for error patterns:
ERROR— general errors (count)- Network/connectivity errors (
Network error,Connection lost,timeout) - Memory/resource errors (
out of memory,OOM,swap) - CDC-specific errors (WAL, binlog, LogMiner patterns)
- Data/constraint errors (
truncation,constraint,duplicate key)
3.3 AWS Health Events
Query DMS scheduled changes and deprecation notices:
- Upcoming engine version deprecations
- Pending mandatory maintenance actions
- Certificate expirations
Step 4: Analyze Against Best Practices
Evaluate ALL collected data against these categories. Assign severity to every finding: CRITICAL, HIGH, MEDIUM, LOW, or INFO.
Reference: references/dms-best-practices.md for detailed best practices.
Reference: references/dms-validation-checklist.md for validation criteria and thresholds.
Referenc