[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7AA4SWVDM84567D8KGP9A7C":3,"skill-same:01M7AA4SWVDM84567D8KGP9A7C":143},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":6,"ownerHtmlUrl":48,"ownerBlogUrl":6,"ownerDescription":49,"updatedAt":50,"install":51,"resources":64},"01M7AA4SWVDM84567D8KGP9A7C","migration-hub-strategy-deployer",null,"Deploys AWS Migration Hub Strategy Recommendations assessments: assessment creation and group-by-application analysis, data collection via Application Discovery Service (agent-based for dependency telemetry vs agentless Collector VM for inventory), the 6R strategy classification (rehost, replatform, refactor, repurchase, retain, retire) from runtime telemetry, anti-pattern detection (EOL OS, deprecated DB engines), TCO analysis, right-sizing from utilization percentiles, migration wave planning from dependency mapping, and handoff to Application Migration Service (MGN) for rehost and Database Migration Service (DMS) for replatform. Emits READY_TO_DEPLOY with a Collector deployment plan and assessment schedule or PREREQUISITES_MISSING with the specific gap. Use when planning a migration assessment, deploying the Collector, interpreting 6R results, or sequencing migration waves.","jhkchan\u002Faws-agent-skills","jhkchan","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1083902?v=4","01M7A2SVQYP9GQTPTDXP5JKYQ4","Jacky Chan","01M7A2SVS117YWCTZABB75HZR1",4,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: migration-hub-strategy-deployer\ndescription: 'Deploys AWS Migration Hub Strategy Recommendations assessments: assessment creation and group-by-application analysis, data collection via Application Discovery Service (agent-based for dependency telemetry vs agentless Collector VM for inventory), the 6R strategy classification (rehost, replatform, refactor, repurchase, retain, retire) from runtime telemetry, anti-pattern detection (EOL OS, deprecated DB engines), TCO analysis, right-sizing from utilization percentiles, migration wave planning from dependency mapping, and handoff to Application Migration Service (MGN) for rehost and Database Migration Service (DMS) for replatform. Emits READY_TO_DEPLOY with a Collector deployment plan and assessment schedule or PREREQUISITES_MISSING with the specific gap. Use when planning a migration assessment, deploying the Collector, interpreting 6R results, or sequencing migration waves.'\nlicense: Apache-2.0\ncompatibility: Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline assessment planning. Live deployment uses aws migrationhub-strategy start-assessment, get-assessment, list-assessment, aws discovery describe-agents, describe-configurations, list-configurations, start-import-task, get-import-task, aws migrationhuborchestrator create-workflow, and aws mgn create-launch-template-template — AWS CLI v2, SSO or key-based credentials, Discovery and...\nmetadata:\n  domain: aws-cloudops\n  complexity: high\n  requires_llm: 'true'\n  phase: '1'\n  supports_pipeline: 'true'\n  entry_point: 'false'\n  family: Migration\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  when_to_use: Planning a Migration Hub Strategy Recommendations assessment, deploying the Application Discovery Service Collector (agent-based or agentless), interpreting 6R strategy classifications from runtime telemetry, detecting anti-patterns (end-of-life OS, deprecated DB engines), running a TCO analysis, right-sizing instances from utilization data, planning migration waves from dependency maps, or handing off to Application Migration Service (MGN) and Database Migration Service (DMS) for execution.\n  activation_triggers: create Migration Hub Strategy assessment, deploy Discovery Collector, agent-based vs agentless discovery, 6R strategy classification, rehost replatform refactor repurchase retain retire, anti-pattern detection end-of-life OS, deprecated DB engine migration, TCO analysis migration, right-sizing recommendations, migration wave planning, dependency mapping migration, Application Migration Service MGN handoff, Database Migration Service DMS replatform\n  invocation_schema: 'Input shape (one of): (a) a migration assessment specification including data source (agent-based, agentless import, or existing Discovery data), target applications or servers, assessment duration, and strategy preferences; (b) a partial spec for interactive refinement (\"assess 200 vCenter VMs for 6R strategy\"); (c) existing assessment results for interpretation and wave planning. Output shape: { ASSESSMENT_SPEC, VERDICT, COLLECTOR_PLAN, ASSESSMENT_SCHEDULE, STRATEGY_GROUPS[], ANTI_PATTERNS[], WAVE_PLAN, FINDINGS[] } where VERDICT is READY_TO_DEPLOY (Collector plan and assessment ready) or PREREQUISITES_MISSING (specific gap cited).'\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  keywords: AWS Migration Hub, Strategy Recommendations, Application Discovery Service, ADS, Agent-based discovery, Agentless discovery, Collector VM, vCenter, 6R strategy, rehost, replatform, refactor, repurchase, retain, retire, anti-pattern detection, end-of-life OS, deprecated DB engine, TCO analysis, right-sizing, migration wave planning, dependency mapping, Application Migration Service, MGN, Database Migration Service, DMS\n  tags: aws-migration-hub, strategy-recommendations, application-discovery-service, collector, 6r-strategy, wave-planning, mgn, dms, deploy\n---\n\n# Migration Hub Strategy Deployer\n\n## Mindset\n\n**One-line takeaway:** a migration strategy assessment is a three-stage\npipeline — **collect** (Application Discovery Service gathers inventory,\nperformance, and network dependency telemetry via agent-based Collectors\nor agentless import) → **classify** (Strategy Recommendations derives\nthe 6R strategy per application from runtime data and anti-pattern\ndetection) → **sequence** (wave planning groups applications by\ndependency proximity and risk into deployable migration waves). A gap\nin ANY stage produces a silent failure: the Collector is deployed but\nnever reports data, the assessment runs but classifies everything as\n\"rehost\" because utilization data is missing, or the wave plan ignores\na hard dependency and the first wave breaks a downstream application.\n\n→ Extended Mindset rationale moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Quick navigation\n\n| You want to... | Go to |\n|---|---|\n| Pick between agent-based and agentless discovery | Step 1 + trade-off table |\n| Deploy the Collector VM on vCenter | Step 2 + worked CLI |\n| Configure the assessment scope and duration | Step 3 |\n| Interpret the 6R strategy classification | Step 4 + Appendix A |\n| Detect anti-patterns (EOL OS, deprecated DB) | Step 5 |\n| Run TCO analysis and right-sizing | Step 6 |\n| Plan migration waves from dependency data | Step 7 |\n| Hand off to MGN for rehost execution | Step 8 |\n| Hand off to DMS for database replatform | Step 9 |\n| Avoid common Collector and assessment pitfalls | Anti-Patterns |\n| Recent features (Strategy Recommendations API, MGN wave builder) | Recent AWS features |\n\n## Critical rules at a glance (do NOT bury these)\n\n1. **Agent-based discovery is required for dependency mapping.**\n   Agentless (Collector VM) gathers inventory and basic performance but\n   CANNOT capture inter-host network connections. If the wave plan\n   depends on dependency data, agents must be installed on all in-scope\n   hosts before the assessment starts.\n2. **Strategy Recommendations needs 7+ days of utilization data for\n   right-sizing.** The assessment derives EC2 instance recommendations\n   from utilization percentiles. A 1-day collection produces noisy\n   recommendations; the minimum recommended window is 7 days, with 14-30\n   days preferred for seasonal workloads.\n3. **The Discovery Collector VM requires network connectivity to BOTH\n   the vCenter and AWS (the home region).** A Collector that cannot\n   reach vCenter cannot import inventory; a Collector that cannot reach\n   AWS cannot upload data. Both firewalls must be open before the\n   Collector starts.\n4. **MGN replication requires the source server's root volume to be\n   accessible and the MGN agent installed.** A rehost strategy is not\n   \"done\" when the 6R says rehost — it is done when MGN replication is\n   healthy and a test cutover succeeds.\n5. **DMS replatform requires the source and target database engines to\n   be compatible.** Strategy Recommendations may recommend replatform\n   from Oracle to Aurora PostgreSQL, but DMS schema conversion (via AWS\n   SCT) is a prerequisite. The assessment does not run SCT automatically.\n\n## Pre-flight: data requirements\n\nPlanning a Migration Hub Strategy assessment requires these inputs:\n\n| Input | Source | Why |\n|---|---|---|\n| Home region | `aws migrationhub-strategy get-portfolio-preferences` (region-aware) | Migration Hub is region-scoped; all data lands in the home region |\n| Existing Discovery data | `aws discovery describe-agents` \u002F `list-configurations` | Avoid re-collecting if agents are already deployed |\n| vCenter connectivity | Network firewall rules | Collector VM must reach vCenter on 443 |\n| Application inventory | CMDB, spreadsheet, or vCenter VM list | Defines the assessment scope |\n| MGN service role | `iam get-role` on `AWSApplicationMigrationAgentInstallationRole` | Rehost handoff requires MGN to be set up |\n| DMS endpoints | `aws dms describe-endpoints` | Database replatform requires source and target endpoints |\n| Strategy preferences | `migrationhub-strategy get-portfolio-preferences` | Configure rehost\u002Freplatform\u002Frefactor weighting |\n\n**If the input is malformed** (missing vCenter or agent list, ambiguous\nhome region), emit:\n\n```text\nASSESSMENT: \u003Creference>\nVERDICT: ERROR\nREASON: Cannot plan assessment — data source and application inventory are required.\nGAP: Re-supply the discovery method (agent-based \u002F agentless), the application or server list, and the target home region.\n```\n\n## Process — Assessment planning (apply in order, produce deployment plan)\n\n### Step 0: Expert knowledge — non-obvious Discovery and Strategy behaviors\n\n→ Step 0 expert-knowledge deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n### Step 1: Choose the discovery method\n\n| Dimension | Agent-based (Discovery Agent) | Agentless (Collector VM) |\n|---|---|---|\n| Installation | Agent on each guest OS | OVA on vCenter or hypervisor |\n| Inventory data | Yes | Yes |\n| Performance data | Process-level (CPU, memory, disk per process) | VM-level (CPU, memory, disk for the whole VM) |\n| Network dependency mapping | Yes (process-to-process connections) | No (VM-level only) |\n| Guest OS access required | Yes (install agent) | No |\n| Reboot required | Sometimes (driver install on Windows) | No |\n| Best for | Dependency mapping, right-sizing, application grouping | Quick inventory, vCenter-only environments |\n| Minimum collection window for 6R | 7 days | 7 days (but 6R falls back to rehost without dependencies) |\n\n**Decision rule:** deploy agent-based discovery on all critical\napplications (those with inter-host dependencies, databases, or\nright-sizing uncertainty). Deploy agentless for the long tail of\nstandalone VMs where inventory-only is sufficient. The two data sources\nmerge in Discovery.\n\n### Step 2: Deploy the Discovery Collector (agentless)\n\nDownload the Collector OVA from the Migration Hub console and deploy on\nvCenter:\n\n→ Collector registration CLI moved verbatim to [references\u002Fdiscovery-collector-deployment.md](references\u002Fdiscovery-collector-deployment.md).\n\nCollector prerequisites checklist:\n\n| Prerequisite | How to verify | Effect if missing |\n|---|---|---|\n| vCenter reachability (443) | `nc -zv vcenter.example.com 443` | Collector cannot import inventory |\n| AWS reachability (443 to home region) | `nc -zv migrationhub-strategy.us-east-1.amazonaws.com 443` | Collector cannot upload data |\n| vCenter credentials with read access | Test login | Collector cannot enumerate VMs |\n| Collector VM network with DHCP or static IP | vCenter console | Collector cannot communicate |\n| DNS resolution for AWS endpoints | `nslookup migrationhub-strategy.us-east-1.amazonaws.com` | Upload fails intermittently |\n\n### Step 3: Configure and start the assessment\n\n```bash\n# Start the assessment (assumes Discovery data is already collected)\naws migrationhub-strategy start-assessment \\\n  --assessment-name portfolio-assessment-q3 \\\n  --s3bucket-for-report-data migration-reports-111111111111 \\\n  --region us-east-1\n```\n\nAssessment scope and duration:\n\n| Parameter | Recommended value | Why |\n|---|---|---|\n| Collection window before assessment | 7-14 days | Right-sizing needs percentile data |\n| Assessment scope | All in-scope servers | Group-by-application requires full scope |\n| S3 report bucket | Dedicated bucket with lifecycle policy | Reports are large; set 90-day expiration |\n| Strategy preferences | Configure before starting | rehost vs replatform weighting affects output |\n\n### Step 4: Interpret the 6R strategy classification\n\nStrategy Recommendations assigns one of six strategies per application:\n\n| Strategy | Meaning | When it is recommended |\n|---|---|---|\n| Rehost | Lift-and-shift to EC2 with minimal changes | Default when no anti-patterns detected and no replatform driver |\n| Replatform | Move to a managed AWS service with minor changes (e.g., EC2 to Elastic Beanstalk, self-managed DB to RDS) | When a managed service reduces operational overhead without code changes |\n| Refactor | Redesign the application for cloud-native architecture | When the application has a strong cloud-native driver (scalability, cost) |\n| Repurchase | Move to a SaaS or different product | When the current product is being replaced (e.g., commercial CRM to SaaS) |\n| Retain | Keep on-premises or defer migration | When the application is sunsetting soon or has hard compliance constraints |\n| Retire | Decommission the application | When the application is unused (Discovery shows zero activity) |\n\n**Key insight:** the 6R is a starting point, not a mandate. Operators\nshould validate each recommendation against business context. A rehost\nrecommendation for a stateful monolith may be technically correct but\nstrategically wrong if the business wants to refactor for scalability.\n\n### Step 5: Detect anti-patterns\n\nStrategy Recommendations flags anti-patterns that affect the strategy:\n\n| Anti-pattern | Detection signal | Strategy impact |\n|---|---|---|\n| End-of-life OS (e.g., Windows Server 2012 R2, CentOS 7) | OS version from agent or vCenter | Forces replatform (upgrade OS) or refactor (containerize) |\n| Deprecated DB engine (e.g., Oracle 11g, SQL Server 2008) | DB engine version from agent | Forces replatform (upgrade DB) or repurchase (move to managed) |\n| Kernel version gap | Linux kernel version | May block MGN agent compatibility; update required |\n| Bare-metal host | vCenter host type | Rehost not possible; must virtualize first |\n| Excessive resource allocation | Utilization \u003C 10% peak | Right-sizing recommendation; rehost with smaller instance |\n| High network dependency (100+ connections) | Agent network data | Wave planning must sequence this application carefully |\n\n### Step 6: TCO analysis and right-sizing\n\nStrategy Recommendations generates a TCO comparison between on-premises\nand AWS, based on:\n\n- On-premises hardware cost (from the operator's input or defaults)\n- AWS cost (from right-sized EC2 recommendations + EBS + data transfer)\n- 3-year TCO horizon (default)\n\nRight-sizing methodology:\n\n| Utilization percentile | EC2 recommendation |\n|---|---|\n| P95 CPU \u003C 20%, memory \u003C 30% | Downsize by 2 sizes |\n| P95 CPU 20-60%, memory 30-70% | Current size or one size down |\n| P95 CPU > 80% or memory > 90% | Upsize or split |\n\n**Gap class — missing utilization data:** if the collection window is\nless than 7 days or the agent was not installed, right-sizing falls back\nto a match-current-spec recommendation (on-premises vCPU\u002FRAM mapped to\nthe closest EC2 instance). This over-provisions in most cases. Flag\n`PREREQUISITES_MISSING` if the collection window is insufficient.\n\n### Step 7: Plan migration waves from dependency data\n\nWave planning groups applications by dependency proximity. The goal is to\nmigrate interdependent applications together to avoid partial-migration\nbreakage.\n\nWave planning inputs:\n\n| Input | Source |\n|---|---|\n| Application dependency graph | Discovery agent network data |\n| Application grouping | Strategy Recommendations group-by-application output |\n| Business priority | Stakeholder input |\n| Risk tolerance | Stakeholder input |\n| Cutover window constraints | Stakeholder input |\n\nWave sequencing heuristic:\n\n1. **Wave 0 (pilot):** 1-2 low-risk, standalone applications (no\n   dependencies). Validate the MGN\u002FDMS pipeline end-to-end.\n2. **Wave 1 (foundation):** shared services (DNS, AD, monitoring) that\n   downstream applications depend on. These MUST migrate first.\n3. **Wave 2+ (dependency-ordered):** applications grouped by dependency\n   clusters. Each wave is a connected component in the dependency graph\n   — migrating a wave must not leave a dependency stranded across the\n   on-premises\u002FAWS boundary.\n4. **Wave N (complex):** applications with 100+ dependencies or hard\n   compliance constraints. These require detailed runbooks and may use\n   a hybrid model (retain on-premises with VPN\u002FDirect Connect).\n\n**Hard constraint:** a wave must not split a dependency cluster. If\napplication A (wave 2) depends on application B (wave 3), either move B\nto wave 2 or delay A to wave 3. The dependency graph determines the\nminimum wave count; business priority determines the ordering within\nthat constraint.\n\n### Step 8: Hand off to Application Migration Service (MGN) for rehost\n\nFor applications classified as \"rehost,\" MGN handles replication and\ncutover:\n\n```bash\n# Install the MGN agent on the source server (requires OS access)\n# On Linux:\nsudo yum install aws-replication-agent -y\n\n# Register the source server with MGN\naws mgn create-launch-template-template \\\n  --launch-template-template-name rehost-template \\\n  --region us-east-1\n```\n\nMGN handoff checklist:\n\n| Step | Command \u002F action |\n|---|---|\n| Install MGN agent | Per OS (yum, apt, MSI) |\n| Verify replication healthy | `aws mgn describe-replication-configuration-templates` |\n| Configure launch template | Set instance type, subnet, security group |\n| Run test cutover | `aws mgn start-cutover --source-server-id s-xxxx` |\n| Validate test instance | Application-level smoke tests |\n| Schedule production cutover | Stakeholder approval + maintenance window |\n\n### Step 9: Hand off to Database Migration Service (DMS) for replatform\n\nFor databases classified as \"replatform\" (self-managed to RDS\u002FAurora):\n\n```bash\n# Create the DMS replication instance\naws dms create-replication-instance \\\n  --replication-instance-identifier migration-rep \\\n  --replication-instance-class dms.r5.xlarge \\\n  --region us-east-1\n```\n\nDMS handoff checklist:\n\n| Step | Command \u002F action |\n|---|---|\n| Run AWS SCT for schema conversion | SCT GUI or CLI (heterogeneous migrations only) |\n| Create source endpoint | `aws dms create-endpoint --endpoint-type source ...` |\n| Create target endpoint | `aws dms create-endpoint --endpoint-type target ...` |\n| Create migration task | `aws dms create-replication-task ...` |\n| Start full load + CDC | `aws dms start-replication-task --migration-type full-load-and-cdc` |\n| Validate data parity | Compare row counts and checksums |\n| Cutover application connection | Update connection strings |\n\n## Output format\n\n```text\nASSESSMENT: \u003Creference>\nHOME_REGION: \u003Cregion>\nDISCOVERY_METHOD:\n  - Agent-based: \u003Cyes | no>, agent count \u003CN>\n  - Agentless: \u003Cyes | no>, Collector VM on \u003CvCenter \u002F hypervisor>\n  - Collection window: \u003Cdays>\nCOLLECTOR_PLAN:\n  - Prerequisites: \u003Cverified list>\n  - Deployment: \u003COVA + registration steps>\nASSESSMENT_SCHEDULE:\n  - Start: \u003Cimmediate | after-collection>\n  - Duration: \u003Cdays>\n  - Report bucket: \u003Cs3 uri>\nSTRATEGY_GROUPS:\n  - Application: \u003Cname>, servers: \u003CN>, strategy: \u003C6R>, confidence: \u003Chigh | medium | low>\nANTI_PATTERNS:\n  - Server: \u003Cid>, pattern: \u003CEOL OS | deprecated DB | ...>, impact: \u003Creplatform | refactor | ...>\nTCO:\n  - On-premises 3-year: \u003C$X>\n  - AWS 3-year (right-sized): \u003C$Y>\n  - Savings: \u003C$Z>\nRIGHT_SIZING:\n  - Server: \u003Cid>, current: \u003CvCPU\u002FRAM>, recommended: \u003Cinstance type>, utilization: \u003CP95 CPU\u002Fmem>\nWAVE_PLAN:\n  - Wave 0: \u003Cpilot applications>\n  - Wave 1: \u003Cfoundation applications>\n  - Wave 2+: \u003Cdependency-ordered clusters>\nMGN_HANDOFF: \u003Cready | blocked>\nDMS_HANDOFF: \u003Cready | blocked>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nGAP: \u003Cif PREREQUISITES_MISSING, the specific missing piece>\nTEMPLATE: \u003CCLI snippets for Collector, assessment, MGN, DMS>\n```\n\n### Worked example — READY_TO_DEPLOY, full assessment\n\n```text\nASSESSMENT: portfolio-q3-assessment\nHOME_REGION: us-east-1\nDISCOVERY_METHOD:\n  - Agent-based: yes, agent count 120 (all critical hosts)\n  - Agentless: yes, Collector VM on vcenter.example.com\n  - Collection window: 14 days\nCOLLECTOR_PLAN:\n  - Prerequisites: vCenter 443 reachable, AWS 443 reachable, vCenter read credentials verified, DNS resolving\n  - Deployment: OVA deployed, registered to home region us-east-1\nASSESSMENT_SCHEDULE:\n  - Start: after-collection (14 days from Collector deploy)\n  - Duration: 14 days collection + 1 day analysis\n  - Report bucket: s3:\u002F\u002Fmigration-reports-111111111111\u002Fportfolio-q3\u002F\nSTRATEGY_GROUPS:\n  - Application: billing-service, servers: 8, strategy: rehost, confidence: high\n  - Application: user-auth, servers: 5, strategy: replatform (self-managed PostgreSQL to RDS), confidence: high\n  - Application: legacy-crm, servers: 12, strategy: refactor (containerize), confidence: medium\n  - Application: reporting-etl, servers: 0 active, strategy: retire, confidence: high\nANTI_PATTERNS:\n  - Server: srv-042, pattern: EOL OS (Windows Server 2012 R2), impact: replatform to Windows Server 2022 required\n  - Server: srv-078, pattern: deprecated DB engine (Oracle 11g), impact: replatform to Aurora PostgreSQL or upgrade\n  - Server: srv-091, pattern: excessive resource allocation (P95 CPU 3%), impact: right-size from m5.4xlarge to m5.large\nTCO:\n  - On-premises 3-year: $1,800,000\n  - AWS 3-year (right-sized): $1,100,000\n  - Savings: $700,000 (39%)\nRIGHT_SIZING:\n  - Server: srv-091, current: 16 vCPU \u002F 64 GB, recommended: m5.large (2 vCPU \u002F 8 GB), utilization: P95 CPU 3%, mem 12%\n  - Server: srv-042, current: 8 vCPU \u002F 32 GB, recommended: m5.xlarge (4 vCPU \u002F 16 GB), utilization: P95 CPU 45%, mem 60%\nWAVE_PLAN:\n  - Wave 0 (pilot): billing-service (8 servers, no external dependencies)\n  - Wave 1 (foundation): shared-dns, shared-ad, shared-monitoring (15 servers, all downstream depend on these)\n  - Wave 2: user-auth (5 servers, depends on shared-ad from Wave 1)\n  - Wave 3: legacy-crm (12 servers, depends on shared-dns and user-auth)\nMGN_HANDOFF: ready (agent install instructions prepared for rehost targets)\nDMS_HANDOFF: ready (SCT + DMS endpoints prepared for user-auth PostgreSQL replatform)\nVERDICT: READY_TO_DEPLOY\nGAP: None\nTEMPLATE:\n  # 1. Deploy Collector VM (download OVA from console, deploy on vcenter.example.com)\n  aws discovery start-import-task --name vcenter-import --vcenter --region us-east-1\n\n  # 2. Install agents on 120 critical hosts (yum\u002Fapt\u002FMSI per OS)\n\n  # 3. Wait 14 days, then start assessment\n  aws migrationhub-strategy start-assessment --assessment-name portfolio-q3-assessment --s3bucket-for-report-data migration-reports-111111111111 --region us-east-1\n\n  # 4. MGN rehost for billing-service\n  aws mgn create-launch-template-template --launch-template-template-name billing-rehost --region us-east-1\n  # 5. DMS replatform for user-auth PostgreSQL\n  aws dms create-replication-instance --replication-instance-identifier user-auth-rep --replication-instance-class dms.r5.xlarge --region us-east-1\n```\n\n### Worked example — PREREQUISITES_MISSING, agentless-only with short window\n\n→ Secondary worked example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Anti-Patterns — NEVER do these things\n\n- NEVER start an assessment with less than 7 days of Discovery data.\n  Right-sizing and 6R classification rely on utilization percentiles.\n  A short window produces noisy recommendations.\n\n- NEVER rely on agentless-only discovery for wave planning. The Collector\n  VM provides inventory but NOT inter-host dependencies. Without the\n  dependency graph, wave sequencing is impossible. Install agents on\n  critical hosts.\n\n- NEVER rehost an end-of-life OS without flagging the anti-pattern.\n  Strategy Recommendations detects EOL OS and recommends replatform.\n  Ignoring this produces an EC2 instance that fails compliance on day one.\n\n- NEVER assume the 6R strategy is final. It is derived from runtime\n  telemetry, not business context. Validate each recommendation with\n  stakeholders.\n\n- NEVER skip the MGN test cutover. A rehost is not complete until MGN\n  replication is healthy AND a test cutover produces a bootable,\n  functional EC2 instance.\n\n- NEVER skip AWS SCT for heterogeneous database migrations. DMS\n  replicates data; it does NOT convert schema objects or stored\n  procedures. An Oracle-to-Aurora replatform without SCT produces a\n  database with tables but no triggers, views, or procedures.\n\n- NEVER deploy the Collector VM without verifying vCenter AND AWS\n  network reachability (both paths on 443). A Collector that cannot\n  reach either endpoint appears healthy but never reports data.\n\n- NEVER change the Migration Hub home region after collection starts.\n  All Discovery data is region-scoped. Confirm the region with\n  stakeholders before starting.\n\n- NEVER wave-plan without the dependency graph. A wave that splits a\n  dependency cluster creates a broken state where applications cannot\n  reach each other across the on-premises\u002FAWS boundary.\n\n- NEVER start DMS replication without validating data parity after the\n  full load. Compare row counts and checksums before cutover.\n\n- NEVER interpret \"retain\" as \"do nothing.\" Retained applications still\n  require a connectivity plan (VPN\u002FDirect Connect) to reach migrated\n  applications in AWS.\n\n- NEVER use Migration Hub Orchestrator managed templates without\n  verifying they fit the application profile. Validate against one pilot\n  application first.\n\n## Configuration dependency graph\n\n→ Configuration dependency graph moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Pre-flight safety checks\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing operation,\n  emit: `CONFIRM: About to \u003Caction> for assessment \u003Cname> in \u003Cregion>.\n  Proceed? (yes\u002Fno)`\n- **Before deploying the Collector VM**, verify vCenter and AWS network\n  paths are open.\n- **Before starting the assessment**, verify the collection window is at\n  least 7 days.\n- **Before a production MGN cutover**, verify a test cutover succeeded.\n- **Before a DMS cutover**, verify data parity (row counts + checksums).\n\n## Appendix A — 6R strategy decision matrix\n\n→ Appendix A decision matrix moved verbatim to [references\u002Fstrategy-and-wave-planning.md](references\u002Fstrategy-and-wave-planning.md).\n\n## Appendix B — Collector VM vs Discovery Agent deployment summary\n\n→ Appendix B comparison table moved verbatim to [references\u002Fdiscovery-collector-deployment.md](references\u002Fdiscovery-collector-deployment.md).\n\nFor the full Collector deployment walkthrough and agent install commands,\nsee **references\u002Fdiscovery-collector-deployment.md**. For the 6R\ninterpretation guide and wave planning templates, see\n**references\u002Fstrategy-and-wave-planning.md**.\n\n## Recent AWS features (2024-2026)\n\n→ Recent AWS features deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: agent-based vs agentless trade-off + 6R from telemetry + wave sequencing\n\n→ Expert-heuristic deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step-0 expert knowledge, configuration dependency graph, expert heuristic, extended Mindset, recent AWS features 2024-2026\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked example (PREREQUISITES_MISSING, agentless-only short window)\n- [references\u002Fdiscovery-collector-deployment.md](references\u002Fdiscovery-collector-deployment.md) — Collector VM \u002F Discovery Agent deployment — extended with Step 2 CLI and Appendix B\n- [references\u002Fstrategy-and-wave-planning.md](references\u002Fstrategy-and-wave-planning.md) — 6R strategy + wave planning — extended with Appendix A decision matrix\n\n## Domain\n\nAWS CloudOps \u002F Migration — Strategy assessment and wave planning.\n\n## AWS documentation\n\n- **AWS Migration Hub Strategy Recommendations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmigrationhub-strategy\u002Flatest\u002Fuserguide\u002F\n- **Application Discovery Service** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fapplication-discovery\u002Flatest\u002Fuserguide\u002F\n- **Application Migration Service (MGN)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmgn\u002Flatest\u002F\n- **Database Migration Service (DMS)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fdms\u002Flatest\u002F\n- **AWS Schema Conversion Tool (SCT)** — https:\u002F\u002Fdocs.aws.amazon.com\u002FSchemaConversionTool\u002Flatest\u002Fuserguide\u002F\n- **Migration Hub Orchestrator** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmigrationhub-orchestrator\u002Flatest\u002F\n","# Migration Hub Strategy Deployer\n\n## Mindset\n\n**One-line takeaway:** a migration strategy assessment is a three-stage\npipeline — **collect** (Application Discovery Service gathers inventory,\nperformance, and network dependency telemetry via agent-based Collectors\nor agentless import) → **classify** (Strategy Recommendations derives\nthe 6R strategy per application from runtime data and anti-pattern\ndetection) → **sequence** (wave planning groups applications by\ndependency proximity and risk into deployable migration waves). A gap\nin ANY stage produces a silent failure: the Collector is deployed but\nnever reports data, the assessment runs but classifies everything as\n\"rehost\" because utilization data is missing, or the wave plan ignores\na hard dependency and the first wave breaks a downstream application.\n\n→ Extended Mindset rationale moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Quick navigation\n\n| You want to... | Go to |\n|---|---|\n| Pick between agent-based and agentless discovery | Step 1 + trade-off table |\n| Deploy the Collector VM on vCenter | Step 2 + worked CLI |\n| Configure the assessment scope and duration | Step 3 |\n| Interpret the 6R strategy classification | Step 4 + Appendix A |\n| Detect anti-patterns (EOL OS, deprecated DB) | Step 5 |\n| Run TCO analysis and right-sizing | Step 6 |\n| Plan migration waves from dependency data | Step 7 |\n| Hand off to MGN for rehost execution | Step 8 |\n| Hand off to DMS for database replatform | Step 9 |\n| Avoid common Collector and assessment pitfalls | Anti-Patterns |\n| Recent features (Strategy Recommendations API, MGN wave builder) | Recent AWS features |\n\n## Critical rules at a glance (do NOT bury these)\n\n1. **Agent-based discovery is required for dependency mapping.**\n   Agentless (Collector VM) gathers inventory and basic performance but\n   CANNOT capture inter-host network connections. If the wave plan\n   depends on dependency data, agents must be installed on all in-scope\n   hosts before the assessment starts.\n2. **Strategy Recommendations needs 7+ days of utilization data for\n   right-sizing.** The assessment derives EC2 instance recommendations\n   from utilization percentiles. A 1-day collection produces noisy\n   recommendations; the minimum recommended window is 7 days, with 14-30\n   days preferred for seasonal workloads.\n3. **The Discovery Collector VM requires network connectivity to BOTH\n   the vCenter and AWS (the home region).** A Collector that cannot\n   reach vCenter cannot import inventory; a Collector that cannot reach\n   AWS cannot upload data. Both firewalls must be open before the\n   Collector starts.\n4. **MGN replication requires the source server's root volume to be\n   accessible and the MGN agent installed.** A rehost strategy is not\n   \"done\" when the 6R says rehost — it is done when MGN replication is\n   healthy and a test cutover succeeds.\n5. **DMS replatform requires the source and target database engines to\n   be compatible.** Strategy Recommendations may recommend replatform\n   from Oracle to Aurora PostgreSQL, but DMS schema conversion (via AWS\n   SCT) is a prerequisite. The assessment does not run SCT automatically.\n\n## Pre-flight: data requirements\n\nPlanning a Migration Hub Strategy assessment requires these inputs:\n\n| Input | Source | Why |\n|---|---|---|\n| Home region | `aws migrationhub-strategy get-portfolio-preferences` (region-aware) | Migration Hub is region-scoped; all data lands in the home region |\n| Existing Discovery data | `aws discovery describe-agents` \u002F `list-configurations` | Avoid re-collecting if agents are already deployed |\n| vCenter connectivity | Network firewall rules | Collector VM must reach vCenter on 443 |\n| Application inventory | CMDB, spreadsheet, or vCenter VM list | Defines the assessment scope |\n| MGN service role | `iam get-role` on `AWSApplicationMigrationAgentInstallationRole` | Rehost handoff requires MGN to be set up |\n| DMS endpoints | `aws dms describe-endpoints` | Database replatform requires source and target endpoints |\n| Strategy preferences | `migrationhub-strategy get-portfolio-preferences` | Configure rehost\u002Freplatform\u002Frefactor weighting |\n\n**If the input is malformed** (missing vCenter or agent list, ambiguous\nhome region), emit:\n\n```text\nASSESSMENT: \u003Creference>\nVERDICT: ERROR\nREASON: Cannot plan assessment — data source and application inventory are required.\nGAP: Re-supply the discovery method (agent-based \u002F agentless), the application or server list, and the target home region.\n```\n\n## Process — Assessment planning (apply in order, produce deployment plan)\n\n### Step 0: Expert knowledge — non-obvious Discovery and Strategy behaviors\n\n→ Step 0 expert-knowledge deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n### Step 1: Choose the discovery method\n\n| Dimension | Agent-based (Discovery Agent) | Agentless (Collector VM) |\n|---|---|---|\n| Installation | Agent on each guest OS | OVA on vCenter or hypervisor |\n| Inventory data | Yes | Yes |\n| Performance data | Process-level (CPU, memory, disk per process) | VM-level (CPU, memory, disk for the whole VM) |\n| Network dependency mapping | Yes (process-to-process connections) | No (VM-level only) |\n| Guest OS access required | Yes (install agent) | No |\n| Reboot required | Sometimes (driver install on Windows) | No |\n| Best for | Dependency mapping, right-sizing, application grouping | Quick inventory, vCenter-only environments |\n| Minimum collection window for 6R | 7 days | 7 days (but 6R falls back to rehost without dependencies) |\n\n**Decision rule:** deploy agent-based discovery on all critical\napplications (those with inter-host dependencies, databases, or\nright-sizing uncertainty). Deploy agentless for the long tail of\nstandalone VMs where inventory-only is sufficient. The two data sources\nmerge in Discovery.\n\n### Step 2: Deploy the Discovery Collector (agentless)\n\nDownload the Collector OVA from the Migration Hub console and deploy on\nvCenter:\n\n→ Collector registration CLI moved verbatim to [references\u002Fdiscovery-collector-deployment.md](references\u002Fdiscovery-collector-deployment.md).\n\nCollector prerequisites checklist:\n\n| Prerequisite | How to verify | Effect if missing |\n|---|---|---|\n| vCenter reachability (443) | `nc -zv vcenter.example.com 443` | Collector cannot import inventory |\n| AWS reachability (443 to home region) | `nc -zv migrationhub-strategy.us-east-1.amazonaws.com 443` | Collector cannot upload data |\n| vCenter credentials with read access | Test login | Collector cannot enumerate VMs |\n| Collector VM network with DHCP or static IP | vCenter console | Collector cannot communicate |\n| DNS resolution for AWS endpoints | `nslookup migrationhub-strategy.us-east-1.amazonaws.com` | Upload fails intermittently |\n\n### Step 3: Configure and start the assessment\n\n```bash\n# Start the assessment (assumes Discovery data is already collected)\naws migrationhub-strategy start-assessment \\\n  --assessment-name portfolio-assessment-q3 \\\n  --s3bucket-for-report-data migration-reports-111111111111 \\\n  --region us-east-1\n```\n\nAssessment scope and duration:\n\n| Parameter | Recommended value | Why |\n|---|---|---|\n| Collection window before assessment | 7-14 days | Right-sizing needs percentile data |\n| Assessment scope | All in-scope servers | Group-by-application requires full scope |\n| S3 report bucket | Dedicated bucket with lifecycle policy | Reports are large; set 90-day expiration |\n| Strategy preferences | Configure before starting | rehost vs replatform weighting affects output |\n\n### Step 4: Interpret the 6R strategy classification\n\nStrategy Recommendations assigns one of six strategies per application:\n\n| Strategy | Meaning | When it is recommended |\n|---|---|---|\n| Rehost | Lift-and-shift to EC2 with minimal changes | Default when no anti-patterns detected and no replatform driver |\n| Replatform | Move to a managed AWS service with minor changes (e.g., EC2 to Elastic Beanstalk, self-managed DB to RDS) | When a managed service reduces operational overhead without code changes |\n| Refactor | Redesign the application for cloud-native architecture | When the application has a strong cloud-native driver (scalability, cost) |\n| Repurchase | Move to a SaaS or different product | When the current product is being replaced (e.g., commercial CRM to SaaS) |\n| Retain | Keep on-premises or defer migration | When the application is sunsetting soon or has hard compliance constraints |\n| Retire | Decommission the application | When the application is unused (Discovery shows zero activity) |\n\n**Key insight:** the 6R is a starting point, not a mandate. Operators\nshould validate each recommendation against business context. A rehost\nrecommendation for a stateful monolith may be technically correct but\nstrategically wrong if the business wants to refactor for scalability.\n\n### Step 5: Detect anti-patterns\n\nStrategy Recommendations flags anti-patterns that affect the strategy:\n\n| Anti-pattern | Detection signal | Strategy impact |\n|---|---|---|\n| End-of-life OS (e.g., Windows Server 2012 R2, CentOS 7) | OS version from agent or vCenter | Forces replatform (upgrade OS) or refactor (containerize) |\n| Deprecated DB engine (e.g., Oracle 11g, SQL Server 2008) | DB engine version from agent | Forces replatform (upgrade DB) or repurchase (move to managed) |\n| Kernel version gap | Linux kernel version | May block MGN agent compatibility; update required |\n| Bare-metal host | vCenter host type | Rehost not possible; must virtualize first |\n| Excessive resource allocation | Utilization \u003C 10% peak | Right-sizing recommendation; rehost with smaller instance |\n| High network dependency (100+ connections) | Agent network data | Wave planning must sequence this application carefully |\n\n### Step 6: TCO analysis and right-sizing\n\nStrategy Recommendations generates a TCO comparison between on-premises\nand AWS, based on:\n\n- On-premises hardware cost (from the operator's input or defaults)\n- AWS cost (from right-sized EC2 recommendations + EBS + data transfer)\n- 3-year TCO horizon (default)\n\nRight-sizing methodology:\n\n| Utilization percentile | EC2 recommendation |\n|---|---|\n| P95 CPU \u003C 20%, memory \u003C 30% | Downsize by 2 sizes |\n| P95 CPU 20-60%, memory 30-70% | Current size or one size down |\n| P95 CPU > 80% or memory > 90% | Upsize or split |\n\n**Gap class — missing utilization data:** if the collection window is\nless than 7 days or the agent was not installed, right-sizing falls back\nto a match-current-spec recommendation (on-premises vCPU\u002FRAM mapped to\nthe closest EC2 instance). This over-provisions in most cases. Flag\n`PREREQUISITES_MISSING` if the collection window is insufficient.\n\n### Step 7: Plan migration waves from dependency data\n\nWave planning groups applications by dependency proximity. The goal is to\nmigrate interdependent applications together to avoid partial-migration\nbreakage.\n\nWave planning inputs:\n\n| Input | Source |\n|---|---|\n| Application dependency graph | Discovery agent network data |\n| Application grouping | Strategy Recommendations group-by-application output |\n| Business priority | Stakeholder input |\n| Risk tolerance | Stakeholder input |\n| Cutover window constraints | Stakeholder input |\n\nWave sequencing heuristic:\n\n1. **Wave 0 (pilot):** 1-2 low-risk, standalone applications (no\n   dependencies). Validate the MGN\u002FDMS pipeline end-to-end.\n2. **Wave 1 (foundation):** shared services (DNS, AD, monitoring) that\n   downstream applications depend on. These MUST migrate first.\n3. **Wave 2+ (dependency-ordered):** applications grouped by dependency\n   clusters. Each wave is a connected component in the dependency graph\n   — migrating a wave must not leave a dependency stranded across the\n   on-premises\u002FAWS boundary.\n4. **Wave N (complex):** applications with 100+ dependencies or hard\n   compliance constraints. These require detailed runbooks and may use\n   a hybrid model (retain on-premises with VPN\u002FDirect Connect).\n\n**Hard constraint:** a wave must not split a dependency cluster. If\napplication A (wave 2) depends on application B (wave 3), either move B\nto wave 2 or delay A to wave 3. The dependency graph determines the\nminimum wave count; business priority determines the ordering within\nthat constraint.\n\n### Step 8: Hand off to Application Migration Service (MGN) for rehost\n\nFor applications classified as \"rehost,\" MGN handles replication and\ncutover:\n\n```bash\n# Install the MGN agent on the source server (requires OS access)\n# On Linux:\nsudo yum install aws-replication-agent -y\n\n# Register the source server with MGN\naws mgn create-launch-template-template \\\n  --launch-template-template-name rehost-template \\\n  --region us-east-1\n```\n\nMGN handoff checklist:\n\n| Step | Command \u002F action |\n|---|---|\n| Install MGN agent | Per OS (yum, apt, MSI) |\n| Verify replication healthy | `aws mgn describe-replication-configuration-templates` |\n| Configure launch template | Set instance type, subnet, security group |\n| Run test cutover | `aws mgn start-cutover --source-server-id s-xxxx` |\n| Validate test instance | Application-level smoke tests |\n| Schedule production cutover | Stakeholder approval + maintenance window |\n\n### Step 9: Hand off to Database Migration Service (DMS) for replatform\n\nFor databases classified as \"replatform\" (self-managed to RDS\u002FAurora):\n\n```bash\n# Create the DMS replication instance\naws dms create-replication-instance \\\n  --replication-instance-identifier migration-rep \\\n  --replication-instance-class dms.r5.xlarge \\\n  --region us-east-1\n```\n\nDMS handoff checklist:\n\n| Step | Command \u002F action |\n|---|---|\n| Run AWS SCT for schema conversion | SCT GUI or CLI (heterogeneous migrations only) |\n| Create source endpoint | `aws dms create-endpoint --endpoint-type source ...` |\n| Create target endpoint | `aws dms create-endpoint --endpoint-type target ...` |\n| Create migration task | `aws dms create-replication-task ...` |\n| Start full load + CDC | `aws dms start-replication-task --migration-type full-load-and-cdc` |\n| Validate data parity | Compare row counts and checksums |\n| Cutover application connection | Update connection strings |\n\n## Output format\n\n```text\nASSESSMENT: \u003Creference>\nHOME_REGION: \u003Cregion>\nDISCOVERY_METHOD:\n  - Agent-based: \u003Cyes | no>, agent count \u003CN>\n  - Agentless: \u003Cyes | no>, Collector VM on \u003CvCenter \u002F hypervisor>\n  - Collection window: \u003Cdays>\nCOLLECTOR_PLAN:\n  - Prerequisites: \u003Cverified list>\n  - Deployment: \u003COVA + registration steps>\nASSESSMENT_SCHEDULE:\n  - Start: \u003Cimmediate | after-collection>\n  - Duration: \u003Cdays>\n  - Report bucket: \u003Cs3 uri>\nSTRATEGY_GROUPS:\n  - Application: \u003Cname>, servers: \u003CN>, strategy: \u003C6R>, confidence: \u003Chigh | medium | low>\nANTI_PATTERNS:\n  - Server: \u003Cid>, pattern: \u003CEOL OS | deprecated DB | ...>, impact: \u003Creplatform | refactor | ...>\nTCO:\n  - On-premises 3-year: \u003C$X>\n  - AWS 3-year (right-sized): \u003C$Y>\n  - Savings: \u003C$Z>\nRIGHT_SIZING:\n  - Server: \u003Cid>, current: \u003CvCPU\u002FRAM>, recommended: \u003Cinstance type>, utilization: \u003CP95 CPU\u002Fmem>\nWAVE_PLAN:\n  - Wave 0: \u003Cpilot applications>\n  - Wave 1: \u003Cfoundation applications>\n  - Wave 2+: \u003Cdependency-ordered clusters>\nMGN_HANDOFF: \u003Cready | blocked>\nDMS_HANDOFF: \u003Cready | blocked>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nGAP: \u003Cif PREREQUISITES_MISSING, the specific missing piece>\nTEMPLATE: \u003CCLI snippets for Collector, assessment, MGN, DMS>\n```\n\n### Worked example — READY_TO_DEPLOY, full assessment\n\n```text\nASSESSMENT: portfolio-q3-assessment\nHOME_REGION: us-east-1\nDISCOVERY_METHOD:\n  - Agent-based: yes, agent count 120 (all critical hosts)\n  - Agentless: yes, Collector VM on vcenter.example.com\n  - Collection window: 14 days\nCOLLECTOR_PLAN:\n  - Prerequisites: vCenter 443 reachable, AWS 443 reachable, vCenter read credentials verified, DNS resolving\n  - Deployment: OVA deployed, registered to home region us-east-1\nASSESSMENT_SCHEDULE:\n  - Start: after-collection (14 days from Collector deploy)\n  - Duration: 14 days collection + 1 day analysis\n  - Report bucket: s3:\u002F\u002Fmigration-reports-111111111111\u002Fportfolio-q3\u002F\nSTRATEGY_GROUPS:\n  - Application: billing-service, servers: 8, strategy: rehost, confidence: high\n  - Application: user-auth, servers: 5, strategy: replatform (self-managed PostgreSQL to RDS), confidence: high\n  - Application: legacy-crm, servers: 12, strategy: refactor (containerize), confidence: medium\n  - Application: reporting-etl, servers: 0 active, strategy: retire, confidence: high\nANTI_PATTERNS:\n  - Server: srv-042, pattern: EOL OS (Windows Server 2012 R2), impact: replatform to Windows Server 2022 required\n  - Server: srv-078, pattern: deprecated DB engine (Oracle 11g), impact: replatform to Aurora PostgreSQL or upgrade\n  - Server: srv-091, pattern: excessive resource allocation (P95 CPU 3%), impact: right-size from m5.4xlarge to m5.large\nTCO:\n  - On-premises 3-year: $1,800,000\n  - AWS 3-year (right-sized): $1,100,000\n  - Savings: $700,000 (39%)\nRIGHT_SIZING:\n  - Server: srv-091, current: 16 vCPU \u002F 64 GB, recommended: m5.large (2 vCPU \u002F 8 GB), utilization: P95 CPU 3%, mem 12%\n  - Server: srv-042, current: 8 vCPU \u002F 32 GB, recommended: m5.xlarge (4 vCPU \u002F 16 GB), utilization: P95 CPU 45%, mem 60%\nWAVE_PLAN:\n  - Wave 0 (pilot): billing-service (8 servers, no external dependencies)\n  - Wave 1 (foundation): shared-dns, shared-ad, shared-monitoring (15 servers, all downstream depend on these)\n  - Wave 2: user-auth (5 servers, depends on shared-ad from Wave 1)\n  - Wave 3: legacy-crm (12 servers, depends on shared-dns and user-auth)\nMGN_HANDOFF: ready (agent install instructions prepared for rehost targets)\nDMS_HANDOFF: ready (SCT + DMS endpoints prepared for user-auth PostgreSQL replatform)\nVERDICT: READY_TO_DEPLOY\nGAP: None\nTEMPLATE:\n  # 1. Deploy Collector VM (download OVA from console, deploy on vcenter.example.com)\n  aws discovery start-import-task --name vcenter-import --vcenter --region us-east-1\n\n  # 2. Install agents on 120 critical hosts (yum\u002Fapt\u002FMSI per OS)\n\n  # 3. Wait 14 days, then start assessment\n  aws migrationhub-strategy start-assessment --assessment-name portfolio-q3-assessment --s3bucket-for-report-data migration-reports-111111111111 --region us-east-1\n\n  # 4. MGN rehost for billing-service\n  aws mgn create-launch-template-template --launch-template-template-name billing-rehost --region us-east-1\n  # 5. DMS replatform for user-auth PostgreSQL\n  aws dms create-replication-instance --replication-instance-identifier user-auth-rep --replication-instance-class dms.r5.xlarge --region us-east-1\n```\n\n### Worked example — PREREQUISITES_MISSING, agentless-only with short window\n\n→ Secondary worked example moved verbatim to [references\u002Fworked-examples.md](references\u002Fworked-examples.md).\n\n## Anti-Patterns — NEVER do these things\n\n- NEVER start an assessment with less than 7 days of Discovery data.\n  Right-sizing and 6R classification rely on utilization percentiles.\n  A short window produces noisy recommendations.\n\n- NEVER rely on agentless-only discovery for wave planning. The Collector\n  VM provides inventory but NOT inter-host dependencies. Without the\n  dependency graph, wave sequencing is impossible. Install agents on\n  critical hosts.\n\n- NEVER rehost an end-of-life OS without flagging the anti-pattern.\n  Strategy Recommendations detects EOL OS and recommends replatform.\n  Ignoring this produces an EC2 instance that fails compliance on day one.\n\n- NEVER assume the 6R strategy is final. It is derived from runtime\n  telemetry, not business context. Validate each recommendation with\n  stakeholders.\n\n- NEVER skip the MGN test cutover. A rehost is not complete until MGN\n  replication is healthy AND a test cutover produces a bootable,\n  functional EC2 instance.\n\n- NEVER skip AWS SCT for heterogeneous database migrations. DMS\n  replicates data; it does NOT convert schema objects or stored\n  procedures. An Oracle-to-Aurora replatform without SCT produces a\n  database with tables but no triggers, views, or procedures.\n\n- NEVER deploy the Collector VM without verifying vCenter AND AWS\n  network reachability (both paths on 443). A Collector that cannot\n  reach either endpoint appears healthy but never reports data.\n\n- NEVER change the Migration Hub home region after collection starts.\n  All Discovery data is region-scoped. Confirm the region with\n  stakeholders before starting.\n\n- NEVER wave-plan without the dependency graph. A wave that splits a\n  dependency cluster creates a broken state where applications cannot\n  reach each other across the on-premises\u002FAWS boundary.\n\n- NEVER start DMS replication without validating data parity after the\n  full load. Compare row counts and checksums before cutover.\n\n- NEVER interpret \"retain\" as \"do nothing.\" Retained applications still\n  require a connectivity plan (VPN\u002FDirect Connect) to reach migrated\n  applications in AWS.\n\n- NEVER use Migration Hub Orchestrator managed templates without\n  verifying they fit the application profile. Validate against one pilot\n  application first.\n\n## Configuration dependency graph\n\n→ Configuration dependency graph moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Pre-flight safety checks\n\n- **MANDATORY CONFIRMATION GATE.** Before any state-changing operation,\n  emit: `CONFIRM: About to \u003Caction> for assessment \u003Cname> in \u003Cregion>.\n  Proceed? (yes\u002Fno)`\n- **Before deploying the Collector VM**, verify vCenter and AWS network\n  paths are open.\n- **Before starting the assessment**, verify the collection window is at\n  least 7 days.\n- **Before a production MGN cutover**, verify a test cutover succeeded.\n- **Before a DMS cutover**, verify data parity (row counts + checksums).\n\n## Appendix A — 6R strategy decision matrix\n\n→ Appendix A decision matrix moved verbatim to [references\u002Fstrategy-and-wave-planning.md](references\u002Fstrategy-and-wave-planning.md).\n\n## Appendix B — Collector VM vs Discovery Agent deployment summary\n\n→ Appendix B comparison table moved verbatim to [references\u002Fdiscovery-collector-deployment.md](references\u002Fdiscovery-collector-deployment.md).\n\nFor the full Collector deployment walkthrough and agent install commands,\nsee **references\u002Fdiscovery-collector-deployment.md**. For the 6R\ninterpretation guide and wave planning templates, see\n**references\u002Fstrategy-and-wave-planning.md**.\n\n## Recent AWS features (2024-2026)\n\n→ Recent AWS features deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: agent-based vs agentless trade-off + 6R from telemetry + wave sequencing\n\n→ Expert-heuristic deep dive moved verbatim to [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — Step-0 expert knowledge, configuration dependency graph, expert heuristic, extended Mindset, recent AWS features 2024-2026\n- [references\u002Fworked-examples.md](references\u002Fworked-examples.md) — secondary worked example (PREREQUISITES_MISSING, agentless-only short window)\n- [references\u002Fdiscovery-collector-deployment.md](references\u002Fdiscovery-collector-deployment.md) — Collector VM \u002F Discovery Agent deployment — extended with Step 2 CLI and Appendix B\n- [references\u002Fstrategy-and-wave-planning.md](references\u002Fstrategy-and-wave-planning.md) — 6R strategy + wave planning — extended with Appendix A decision matrix\n\n## Domain\n\nAWS CloudOps \u002F Migration — Strategy assessment and wave planning.\n\n## AWS documentation\n\n- **AWS Migration Hub Strategy Recommendations** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmigrationhub-strategy\u002Flatest\u002Fuserguide\u002F\n- **Application Discovery Service** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fapplication-discovery\u002Flatest\u002Fuserguide\u002F\n- **Application Migration Service (MGN)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmgn\u002Flatest\u002F\n- **Database Migration Service (DMS)** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fdms\u002Flatest\u002F\n- **AWS Schema Conversion Tool (SCT)** — https:\u002F\u002Fdocs.aws.amazon.com\u002FSchemaConversionTool\u002Flatest\u002Fuserguide\u002F\n- **Migration Hub Orchestrator** — https:\u002F\u002Fdocs.aws.amazon.com\u002Fmigrationhub-orchestrator\u002Flatest\u002F\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":42},{"tags":25,"phase":26,"author":27,"domain":28,"family":29,"version":30,"keywords":31,"task_type":32,"complexity":33,"entry_point":34,"skill_class":35,"when_to_use":36,"requires_llm":37,"verdict_shape":38,"lifecycle_status":39,"invocation_schema":40,"supports_pipeline":37,"activation_triggers":41},"aws-migration-hub, strategy-recommendations, application-discovery-service, collector, 6r-strategy, wave-planning, mgn, dms, deploy","1","Jacky Chan — AWS Community Builder","aws-cloudops","Migration","0.1.0","AWS Migration Hub, Strategy Recommendations, Application Discovery Service, ADS, Agent-based discovery, Agentless discovery, Collector VM, vCenter, 6R strategy, rehost, replatform, refactor, repurchase, retain, retire, anti-pattern detection, end-of-life OS, deprecated DB engine, TCO analysis, right-sizing, migration wave planning, dependency mapping, Application Migration Service, MGN, Database Migration Service, DMS","deploy","high","false","capability","Planning a Migration Hub Strategy Recommendations assessment, deploying the Application Discovery Service Collector (agent-based or agentless), interpreting 6R strategy classifications from runtime telemetry, detecting anti-patterns (end-of-life OS, deprecated DB engines), running a TCO analysis, right-sizing instances from utilization data, planning migration waves from dependency maps, or handing off to Application Migration Service (MGN) and Database Migration Service (DMS) for execution.","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Input shape (one of): (a) a migration assessment specification including data source (agent-based, agentless import, or existing Discovery data), target applications or servers, assessment duration, and strategy preferences; (b) a partial spec for interactive refinement (\"assess 200 vCenter VMs for 6R strategy\"); (c) existing assessment results for interpretation and wave planning. Output shape: { ASSESSMENT_SPEC, VERDICT, COLLECTOR_PLAN, ASSESSMENT_SCHEDULE, STRATEGY_GROUPS[], ANTI_PATTERNS[], WAVE_PLAN, FINDINGS[] } where VERDICT is READY_TO_DEPLOY (Collector plan and assessment ready) or PREREQUISITES_MISSING (specific gap cited).","create Migration Hub Strategy assessment, deploy Discovery Collector, agent-based vs agentless discovery, 6R strategy classification, rehost replatform refactor repurchase retain retire, anti-pattern detection end-of-life OS, deprecated DB engine migration, TCO analysis migration, right-sizing recommendations, migration wave planning, dependency mapping migration, Application Migration Service MGN handoff, Database Migration Service DMS replatform","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). No AWS CLI required for offline assessment planning. Live deployment uses aws migrationhub-strategy start-assessment, get-assessment, list-assessment, aws discovery describe-agents, describe-configurations, list-configurations, start-import-task, get-import-task, aws migrationhuborchestrator create-workflow, and aws mgn create-launch-template-template — AWS CLI v2, SSO or key-based credentials, Discovery and...","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fmigration-hub-strategy-deployer",0,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills","https:\u002F\u002Fgithub.com\u002Fjhkchan","CTO & Co-Founder @Beever-AI  & @votee. CAISP. AWS Community Builder. Organizer@GDGCloudHK. MongoDB Champion. Technopreneur + Infornographer.","2026-09-24 08:54:10",{"source":8,"skillName":5,"commands":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill migration-hub-strategy-deployer",{"tool":57,"command":58},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill migration-hub-strategy-deployer",{"tool":60,"command":61},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill migration-hub-strategy-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103,107,111,115,119,123,127,131,135,139],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",6292,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Feval\u002Ftest-cases.yaml",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"evals\u002Fbaselines\u002Fagentless-only-short-window.md",622,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fbaselines\u002Fagentless-only-short-window.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"evals\u002Fbaselines\u002Fcollector-network-blocker.md",554,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fbaselines\u002Fcollector-network-blocker.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"evals\u002Fbaselines\u002Fdatabase-replatform-dms.md",592,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fbaselines\u002Fdatabase-replatform-dms.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"evals\u002Fbaselines\u002Feol-os-anti-pattern.md",602,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fbaselines\u002Feol-os-anti-pattern.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"evals\u002Fbaselines\u002Ffull-portfolio-assessment.md",1163,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fbaselines\u002Ffull-portfolio-assessment.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"evals\u002Feval_config.yaml",1756,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Feval_config.yaml",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"evals\u002Fevals.json",4344,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fevals.json",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"evals\u002Fprompts\u002Fagentless-only-short-window.md",543,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fprompts\u002Fagentless-only-short-window.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"evals\u002Fprompts\u002Fcollector-network-blocker.md",534,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fprompts\u002Fcollector-network-blocker.md",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"evals\u002Fprompts\u002Fdatabase-replatform-dms.md",671,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fprompts\u002Fdatabase-replatform-dms.md",{"path":112,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":113,"sourceHtmlUrl":114},"evals\u002Fprompts\u002Feol-os-anti-pattern.md",572,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fprompts\u002Feol-os-anti-pattern.md",{"path":116,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":117,"sourceHtmlUrl":118},"evals\u002Fprompts\u002Ffull-portfolio-assessment.md",836,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fevals\u002Fprompts\u002Ffull-portfolio-assessment.md",{"path":120,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":121,"sourceHtmlUrl":122},"examples\u002FREADME.md",7212,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fexamples\u002FREADME.md",{"path":124,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fadvanced-patterns.md",8882,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":128,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fdiscovery-collector-deployment.md",4777,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Freferences\u002Fdiscovery-collector-deployment.md",{"path":132,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fstrategy-and-wave-planning.md",6255,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Freferences\u002Fstrategy-and-wave-planning.md",{"path":136,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fworked-examples.md",1919,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Freferences\u002Fworked-examples.md",{"path":140,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":141,"sourceHtmlUrl":142},"skill.usf.yaml",4607,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fmigration-hub-strategy-deployer\u002Fskill.usf.yaml",[144,151,158,165,172,179],{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":19},"01M7ADVD60X4PCAPKSE58P9NDC","xray-tracing-deployer","Deploys AWS X-Ray distributed tracing with production-grade configuration: X-Ray daemon deployment (EC2 systemd, ECS sidecar, EKS DaemonSet, Lambda built-in), SDK instrumentation (Java, Python, Node.js, Go, .NET) with annotations and metadata, sampling rules (default reservoir + rate vs custom rules with URL \u002F method \u002F service-name predicates), service map generation, trace query and retrieval, groups and insights, CloudWatch ServiceLens integration, IAM permissions (PutTraceSegments, GetSamplingRules), and latest features (Lambda Powertools tracing, OpenTelemetry \u002F ADOT Collector support, W3C trace context). Emits a READY_TO_DEPLOY checklist with every configuration item verified. Use when enabling X-Ray on a new application, adding tracing to ECS \u002F EKS \u002F Lambda, validating a sampling configuration, or generating daemon deployment CLI and IaC templates. Triggers: X-Ray, distributed tracing, X-Ray daemon, sampling rules, service map, X-Ray SDK, OpenTelemetry, ADOT, Lambda Powertools, CloudWatch ServiceLens.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxray-tracing-deployer\u002FSKILL.md",[],[],{"skillNo":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":157,"publishedAt":19},"01M7ADTVJ7DCBM9CB1FY51GH7J","wellarchitected-workload-auditor","Audits AWS Well-Architected Tool workloads for review staleness, per-pillar high-risk issue counts, milestone tracking gaps, and remediation plan completeness. Emits a deterministic verdict (STALE_REVIEW | HIGH_RISK | CONFIG_GAP | OK) per workload with per-pillar risk breakdown, milestone trend analysis, and specific remediation. Use when reviewing Well-Architected workloads, checking WA review freshness, auditing high-risk issues per pillar, validating milestone coverage, or tracking remediation plans.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-workload-auditor\u002FSKILL.md",[],[],{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":164,"publishedAt":19},"01M7ADT59G6FTTNZYHT2QRPNNP","wellarchitected-review-operator","Operates AWS Well-Architected Tool reviews end-to-end — creates workloads, runs pillar reviews (operational excellence, security, reliability, performance, cost optimization, sustainability, Prosperity), answers questions with risk-tier rationale, generates reports and improvement plans, creates milestones, and integrates with Trusted Advisor and Well-Architected Labs. Runs deterministic pre-checks (workload existence, lens availability, pillar coverage), emits the exact update-answer \u002F get-consolidated-report CLI behind a CONFIRM gate, and verifies risk-tier transitions. Emits READY | BLOCKED | COMPLETED. Use when creating a workload, answering pillar questions, generating an improvement plan, creating a milestone, or integrating with Trusted Advisor. Triggers: well-architected tool, well architected review, workload review, pillar, operational excellence, security, reliability, performance, cost optimization, sustainability, prosperity, improvement plan, milestone, trusted advisor.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwellarchitected-review-operator\u002FSKILL.md",[],[],{"skillNo":166,"name":167,"nameZh":6,"description":168,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":169,"categories":170,"keywords":171,"publishedAt":19},"01M7ADSH5JA9QHNPPHQCD7EVA7","wafv2-web-acl-deployer","Provisions AWS WAFv2 Web ACLs with correct production defaults: scope selection (CLOUDFRONT vs REGIONAL), managed rule groups (AWSManagedRulesCommonRuleSet, SQLiRuleSet, LinuxRuleSet, WindowsRuleSet, IPReputationList, BotControlRuleSet, AmazonIpReputationList, ATP), custom rules (byte match, IP set, regex pattern, geo match, size constraint, rate-based), rule priority ordering, logging destinations (Kinesis Firehose, CloudWatch Logs, S3), resource association (ALB, API Gateway, CloudFront), rate-based rules with aggregate keys (IP, forwarded IP), Challenge and CAPTCHA actions, and account takeover prevention. Emits a READY_TO_DEPLOY checklist. Use when creating a Web ACL, attaching managed rules, configuring rate limiting, enabling WAF logging, associating a Web ACL with an ALB\u002FAPI Gateway\u002FCloudFront, or configuring CAPTCHA\u002FChallenge actions. Triggers: create WAF Web ACL, WAFv2, managed rule groups, WAF rate limiting, WAF logging, WAF CAPTCHA, WAF Challenge action, bot control, ATP managed rules.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-deployer\u002FSKILL.md",[],[],{"skillNo":173,"name":174,"nameZh":6,"description":175,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":176,"categories":177,"keywords":178,"publishedAt":19},"01M7ADRYFAT8R73FBNCHRC573X","wafv2-web-acl-auditor","Audits AWS WAFv2 Web ACL configurations to determine whether the ACL provides effective protection: default-action posture (Allow vs Block), managed-rule-group coverage gaps, rule effectiveness (BLOCK vs COUNT, shadow\u002Fbypass rules, stale exclusions), rate-based rule correctness, logging and visibility configuration, and text-transformation bypass vectors. Emits a deterministic verdict per Web ACL. Use when reviewing a WAFv2 Web ACL for security posture, checking managed-rule coverage, validating rate-limit configuration, auditing WAF logging, or hardening a WAF before production deployment. Triggers: WAF, WAFv2, Web ACL, managed rule group, AWSManagedRules, rate-based rule, CAPTCHA, Challenge, OverrideAction, Count mode, forwarded IP, Bot Control, ATP, text transformation, WAF logging, WAF visibility, OWASP, SQLi, XSS, RFI.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwafv2-web-acl-auditor\u002FSKILL.md",[],[],{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":185,"publishedAt":19},"01M7ADR8W7G72JX4KFGN03QK8Q","waf-rule-deployer","Provisions AWS WAFv2 rule sets with production defaults: Web ACL creation (CloudFront scope in us-east-1 vs Regional scope), rule groups (managed vs custom) with capacity planning in WCU (Web ACL Capacity Units, 1500 default per ACL), managed rule groups (AWSManagedRulesCommonRuleSet, AWSManagedRulesSQLiRuleSet, AWSManagedRulesAmazonIpReputationList, AWSManagedRulesLinuxRuleSet, AWSManagedRulesWindowsRuleSet, AWSManagedRulesUnixRuleSet), custom rules (byte-match, regex pattern set, geo-match, rate-based), IP set and regex pattern set resources, rule priority ordering (lowest number evaluated first), action types (allow, block, count, CAPTCHA, Challenge), bot control managed rule group, account takeover. Triggers: create WAF rule, WAF managed rule group, WAF custom rule, WAF byte match, WAF geo match, WAF rate based rule, WAF IP set, WAF regex pattern set, WAF WCU budget, WAF CloudFront ACL, WAF logging Kinesis Firehose, WAF bot control, WAF ATP, WAF label matching, WAF Challenge action, WAF CAPTCHA.","https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fwaf-rule-deployer\u002FSKILL.md",[],[]]