[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7HAVNTS6JTNXKXTZCPDHA":3,"skill-same:01M7A7HAVNTS6JTNXKXTZCPDHA":146},{"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":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":6,"ownerHtmlUrl":47,"ownerBlogUrl":6,"ownerDescription":48,"updatedAt":49,"install":50,"resources":63},"01M7A7HAVNTS6JTNXKXTZCPDHA","ecr-replication-deployer",null,"Provisions Amazon ECR cross-region and cross-account replication with production defaults: registry-level replication configuration (put-registry-replication-configuration), replication rules (source → destination region and registry), cross-account replication (destination registry ID), pull-through cache rules (upstream registry URL — ecr-public, quay.io, docker.io, k8s.io), cache pull permissions (Lambda\u002FECS pulls from cached image), replication lag awareness, cost per replicated image (storage in both regions), CloudWatch metrics for replication (ImageReplicationStatus), batch delete protection for replicated images, and deletion policy for source vs replica. Emits a READY_TO_DEPLOY checklist with verification commands. Use when configuring ECR cross-region replication, cross-account ECR replication, ECR pull-through cache, or. Triggers: configure ecr replication, ecr cross-region replication, ecr cross-account replication, ecr pull-through cache, ecr replication rule, ecr registry replication.","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\u002Fecr-replication-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ecr-replication-deployer\ndescription: 'Provisions Amazon ECR cross-region and cross-account replication with production defaults: registry-level replication configuration (put-registry-replication-configuration), replication rules (source → destination region and registry), cross-account replication (destination registry ID), pull-through cache rules (upstream registry URL — ecr-public, quay.io, docker.io, k8s.io), cache pull permissions (Lambda\u002FECS pulls from cached image), replication lag awareness, cost per replicated image (storage in both regions), CloudWatch metrics for replication (ImageReplicationStatus), batch delete protection for replicated images, and deletion policy for source vs replica. Emits a READY_TO_DEPLOY checklist with verification commands. Use when configuring ECR cross-region replication, cross-account ECR replication, ECR pull-through cache, or. Triggers: configure ecr replication, ecr cross-region replication, ecr cross-account replication, ecr pull-through cache, ecr replication rule, ecr registry replication.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ecr access (and cross-account IAM if cross-account replication). Works with Terraform aws_ecr_replication_configuration \u002F aws_ecr_pull_through_cache_rule resources and CloudFormation AWS::ECR::ReplicationConfiguration templates.'\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: DevTools\n  task_type: deploy\n  skill_class: capability\n  lifecycle_status: active\n  verdict_shape: READY_TO_DEPLOY | PREREQUISITES_MISSING\n  version: 0.1.0\n  author: Jacky Chan — AWS Community Builder\n  tags: aws, ecr, replication, cloudops, deploy, devtools, provisioning, cross-region, cross-account, pull-through-cache, container-registry\n  dependencies: aws-orchestrator\n  keywords: aws, ecr, elastic container registry, replication, cross-region, cross-account, pull-through cache, cloudops, deploy, provisioning, container registry, docker, devtools\n  when_to_use: Invoke when the user wants to configure ECR cross-region replication, cross-account ECR replication, ECR pull-through cache rules (for docker.io, quay.io, k8s.io, ecr-public upstream registries), multi-region container image availability for DR, or understand replication lag and cost implications. Do NOT invoke for ECR repository lifecycle policies (separate skill), ECR image scanning, or ECS\u002FEKS task deployment.\n---\n\n# ECR Replication Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon ECR cross-region\nand cross-account replication with correct defaults. The skill walks\nthe operator through registry-level replication configuration,\nreplication rules (source → destination), cross-account destination\nregistry IDs, pull-through cache rules for external registries\n(docker.io, quay.io, k8s.io, ecr-public), replication lag awareness,\ncost per replicated image (storage in both regions), CloudWatch\nmonitoring metrics (ImageReplicationStatus), batch delete protection\nfor replicated images, and deletion policy for source vs replica,\ncaptures all configuration decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\nconfigure ECR replication, ECR cross-region replication, ECR cross-\naccount replication, ECR pull-through cache, ECR replication rule,\nECR registry replication, ECR pull-through cache rule.\n\n## STRICT output contract\n\nWhen this skill is invoked with an ECR-replication-provisioning\nrequest (configure cross-region replication, set up cross-account\nreplication, create a pull-through cache rule, or a partial\nconfiguration), the agent MUST respond with the READY_TO_DEPLOY\nchecklist defined in the \"Output format\" section using the literal\nall-caps labels `ECR_REPLICATION:`, `VERDICT:`, `CHECKLIST:`, and\n`VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Registry-level replication model | Core model |\n| Step 2 — Cross-region replication | Same-account multi-region |\n| Step 3 — Cross-account replication | Cross-account sharing |\n| Step 4 — Pull-through cache rules | External registry caching |\n| Step 5 — Replication lag and timing | Eventual consistency |\n| Step 6 — Cost per replicated image | Storage cost awareness |\n| Step 7 — CloudWatch metrics | Monitoring |\n| Step 8 — Batch delete protection | Replica immutability |\n| Step 9 — Deletion policy (source vs replica) | Cleanup |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fcross-region-and-cross-account.md | Replication detail |\n| references\u002Fpull-through-cache-and-cost.md | Cache + cost detail |\n\n## Mindset\n\n**One-line takeaway:** ECR replication is configured at the REGISTRY\nlevel — ALL repositories in the source registry replicate to the\ndestination. You cannot replicate individual repositories.\nReplicated images are READ-ONLY in the destination (you cannot push\nto a replica). Pull-through cache rules let you cache external images\n(docker.io, quay.io, k8s.io, ecr-public) locally so that Lambda\u002FECS\npulls from the cached copy without hitting the external registry.\n\nThree misconceptions dominate ECR replication misdesign at\nprovisioning time:\n\nThe three provisioning misconceptions moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Configuration dependency graph (novel heuristic)\nFull dependency table and cross-dependency gotchas moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: replication is registry-level\nRegistry-level scope tree and key implication moved to\n[references\u002Fcross-region-and-cross-account.md](references\u002Fcross-region-and-cross-account.md).\n\n## Expert heuristic: pull-through cache reduces external dependency\nPull-through-cache vs replication tree and key implications moved to\n[references\u002Fpull-through-cache-and-cost.md](references\u002Fpull-through-cache-and-cost.md).\n\n## Expert heuristic: replicated images are read-only\nReplica read-only operations tree and key implication moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Source ECR registry exists | Replication source must be an existing registry | `aws ecr describe-registry` |\n| Source repositories have images | Replication copies existing and future images | `aws ecr describe-repositories` |\n| Destination region identified (cross-region) | Replication target region | Confirm region name |\n| Destination account ID (cross-account) | Cross-account replication needs 12-digit account ID | `aws sts get-caller-identity` (in destination) |\n| Destination registry allows replication (cross-account) | Destination must not have REPLICATION_DISALLOWED | Verify destination registry settings |\n| Upstream registry URL valid (pull-through cache) | Must be ecr-public, quay.io, docker.io, or k8s.io | Confirm upstream type |\n| IAM permission for ecr:PutReplicationConfiguration | Configuring replication requires this permission | Verify IAM policy |\n| Region settings support replication | Some restricted regions may not support ECR replication | Confirm region availability |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Registry-level replication model\n\nECR replication is configured at the registry level using\n`put-registry-replication-configuration`. This is a single API call\nthat defines all replication rules for the entire registry.\n\n| Concept | Description |\n|---|---|\n| Source registry | The registry where images are pushed (primary) |\n| Destination | The target region\u002Faccount where images are replicated |\n| Replication rule | A single source → destination mapping |\n| Scope | ALL repositories in the source registry (no per-repo filtering) |\n| Image state | Replicated images are READ-ONLY in the destination |\n\n```bash\n# Check current replication configuration\naws ecr describe-registry --region us-east-1\n```\n\n## Step 2 — Cross-region replication\n\nCross-region replication copies images from the source region to one\nor more destination regions within the SAME account.\n\n```bash\naws ecr put-registry-replication-configuration \\\n  --replication-configuration '{\n    \"rules\": [\n      {\n        \"destinations\": [\n          {\n            \"region\": \"us-west-2\",\n            \"registryId\": \"111122223333\"\n          },\n          {\n            \"region\": \"eu-west-1\",\n            \"registryId\": \"111122223333\"\n          }\n        ]\n      }\n    ]\n  }' \\\n  --region us-east-1\n```\n\n**Key points:**\n- `registryId` is the 12-digit AWS account ID (same for cross-region\n  within the same account).\n- Multiple destinations can be specified in a single rule.\n- Once configured, ALL repositories in us-east-1 replicate to both\n  us-west-2 and eu-west-1.\n\nVerify commands (push to source, check replica describe-images): [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n## Step 3 — Cross-account replication\n\nCross-account replication copies images from the source account to a\ndestination account. The destination account ID is specified as the\n`registryId`.\n\n```bash\naws ecr put-registry-replication-configuration \\\n  --replication-configuration '{\n    \"rules\": [\n      {\n        \"destinations\": [\n          {\n            \"region\": \"us-east-1\",\n            \"registryId\": \"999999999999\"\n          }\n        ]\n      }\n    ]\n  }' \\\n  --region us-east-1\n```\n\n**Critical:** the destination account (999999999999) must NOT have\nreplication disabled. By default, registries allow incoming\nreplication. If the destination has set the registry policy to\ndisallow replication, images will not replicate.\n\nCombined cross-region + cross-account configuration example moved to [references\u002Fcross-region-and-cross-account.md](references\u002Fcross-region-and-cross-account.md).\n\n## Step 4 — Pull-through cache rules\n\nPull-through cache rules fetch and cache external images in your ECR.\nWhen Lambda\u002FECS pulls an image matching a cache rule, ECR fetches it\nfrom the upstream registry and caches it locally.\n\n```bash\n# Create a pull-through cache rule for docker.io\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix docker-hub\u002F \\\n  --upstream-registry-url registry-1.docker.io \\\n  --region us-east-1\n\n# Create a pull-through cache rule for quay.io\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix quay\u002F \\\n  --upstream-registry-url quay.io \\\n  --region us-east-1\n\n# Create a pull-through cache rule for k8s.io\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix k8s\u002F \\\n  --upstream-registry-url registry.k8s.io \\\n  --region us-east-1\n\n# Create a pull-through cache rule for ecr-public\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix ecr-public\u002F \\\n  --upstream-registry-url public.ecr.aws \\\n  --region us-east-1\n```\n\n**Supported upstream registries:**\n\n| Upstream | URL | ECR prefix example |\n|---|---|---|\n| Docker Hub | `registry-1.docker.io` | `docker-hub\u002F` |\n| Quay.io | `quay.io` | `quay\u002F` |\n| Kubernetes | `registry.k8s.io` | `k8s\u002F` |\n| ECR Public | `public.ecr.aws` | `ecr-public\u002F` |\n\n**Pulling a cached image:**\n\n```bash\n# Instead of: docker pull nginx:latest\n# Use the pull-through cache prefix:\ndocker pull 111122223333.dkr.ecr.us-east-1.amazonaws.com\u002Fdocker-hub\u002Flibrary\u002Fnginx:latest\n```\n\n**Key points:**\n- The `ecr-repository-prefix` maps to a namespace in your ECR. All\n  pulls via this prefix create repositories under that namespace.\n- The first pull triggers the cache fetch (slower); subsequent pulls\n  use the cached copy (faster).\n- Pull-through cache repositories are managed by ECR — you cannot\n  push to them manually.\n\n## Step 5 — Replication lag and timing\n\nReplication is asynchronous. After pushing an image to the source,\nthere is a lag before it appears in the destination.\n\n```text\nReplication lag expectations:\n  ├── Same-region cross-account: seconds to ~1 minute\n  ├── Cross-region (same continent): seconds to ~2 minutes\n  ├── Cross-region (intercontinental): 1-5 minutes\n  └── Large images (>1GB): add transfer time (proportional to size)\n```\n\nCloudWatch ImageReplicationStatus check command moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n**Important:** always verify replication completed before deploying\nfrom a replica. If the image has not replicated yet, pulls will fail\nwith `ImageNotFoundException`.\n\n## Step 6 — Cost per replicated image\n\nReplicated images incur storage costs in BOTH the source and\ndestination regions. This doubles the storage cost per image.\n\n```text\nCost model:\n  Source region: ECR storage cost per GB-month\n  Destination region: ECR storage cost per GB-month (SAME rate)\n  Total storage cost: 2x normal (source + each destination)\n\n  Data transfer:\n  ├── Source → Destination (replication): AWS data transfer rates\n  └── Destination → Lambda\u002FECS (pull): standard ECR data transfer (free in-region)\n```\n\n**Key implication:** replication doubles (or triples for multi-\ndestination) storage costs. For cost optimization:\n- Use lifecycle policies to prune old images in BOTH source and\n  destinations.\n- Replicate only to regions where you actually deploy.\n- Consider pull-through cache instead of replication for third-party\n  images (only one copy cached, not replicated across regions).\n\n## Step 7 — CloudWatch metrics for replication\n\nECR provides CloudWatch metrics for monitoring replication status.\n\n| Metric | Description |\n|---|---|\n| `ImageReplicationStatus` | Count of images by replication status (Complete, Failed, InProgress) |\n| `RepositoryCount` | Number of repositories in the registry |\n| `ImageCount` | Number of images across all repositories |\n| `StorageUsed` | Total storage used in bytes |\n\nCloudWatch alarm creation command for replication failures moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n## Step 8 — Batch delete protection for replicated images\n\nReplicated images CANNOT be batch-deleted in the destination\nregistry. They are read-only. This is a safety mechanism.\n\n```bash\n# This will FAIL on a replicated image in the destination:\naws ecr batch-delete-image \\\n  --repository-name my-app \\\n  --image-ids imageTag=latest \\\n  --region us-west-2\n# Error: ImageNotFoundException or \"replicated images cannot be deleted\"\n```\n\n**To remove a replicated image:**\n1. Delete the image at the SOURCE.\n2. Manually delete the orphaned replica in the destination (it is\n   now a regular image, not tied to a source image).\n\n**Important:** deleting the source image does NOT automatically\ndelete the replica. You must clean up the destination manually or use\na lifecycle policy in the destination.\n\n## Step 9 — Deletion policy (source vs replica)\n\n| Action | Source registry | Destination registry (replica) |\n|---|---|---|\n| Push image | Allowed | Denied (read-only) |\n| Delete image | Allowed (batch-delete-image) | Denied (batch-delete blocked on replicas) |\n| Delete repository | Allowed | Allowed (but replicas reappear if source re-pushes) |\n| Lifecycle policy | Runs independently | Runs independently (apply to both) |\n\n**Recommended deletion workflow:**\n\n```text\n1. Delete image at source:\n   aws ecr batch-delete-image --repository-name my-app --image-ids imageTag=v1.0 --region us-east-1\n\n2. Delete orphaned replica in each destination:\n   aws ecr batch-delete-image --repository-name my-app --image-ids imageTag=v1.0 --region us-west-2\n   (This works AFTER the source image is deleted — the replica becomes a standalone image)\n\n3. Apply lifecycle policies in BOTH source and destinations for automated cleanup.\n```\n\n## Step 10 — Recent features\nRecent AWS feature notes (2023-2026) moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER assume replication is per-repository.** Replication is at\n   the REGISTRY level. Configuring replication replicates ALL repos.\n   Use cross-account repo policies for selective sharing.\n\n2. **NEVER try to push to a replicated image in the destination.**\n   Replicated images are READ-ONLY. Push to the source only.\n\n3. **NEVER assume deleting the source image deletes the replica.**\n   The replica becomes orphaned and must be deleted manually in the\n   destination, or cleaned up via lifecycle policy.\n\n4. **NEVER use batch-delete-image on a replicated image in the\n   destination while it is still linked to the source.** It will\n   fail. Delete the source image first, then the orphaned replica.\n\n5. **NEVER configure pull-through cache with an unsupported upstream\n   URL.** Only `registry-1.docker.io`, `quay.io`, `registry.k8s.io`,\n   and `public.ecr.aws` are supported. Custom URLs are rejected.\n\n6. **NEVER ignore replication lag before deploying from a replica.**\n   Always check `ImageReplicationStatus` to confirm the image has\n   replicated. Deploying from a non-replicated image fails with\n   `ImageNotFoundException`.\n\n7. **NEVER forget that replication doubles storage costs.** Each\n   destination region incurs the same storage cost as the source.\n   Apply lifecycle policies in BOTH source and destinations.\n\n8. **NEVER configure cross-account replication without verifying the\n   destination allows it.** If the destination has\n   `REPLICATION_DISALLOWED`, replication silently fails.\n\n9. **NEVER confuse pull-through cache with replication.** Pull-\n   through cache fetches EXTERNAL images into your ECR. Replication\n   copies YOUR images across regions\u002Faccounts.\n\n10. **NEVER assume replication is instant for large images.**\n    Replication lag for multi-GB images can be minutes. Always verify\n    before deploying.\n\n## Output format\n\n```text\nECR_REPLICATION: \u003Csource-registry-id> (region: \u003Csource-region>) → \u003Cdestinations>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Source registry: \u003Cregistry-id> (region: \u003Csource-region>)\n  [✓|✗] Replication type: Cross-region | Cross-account | Both | Pull-through cache\n  [✓|✗] Destinations: \u003Cregion:registry-id list>\n  [✓|✗] Registry scope: ALL repositories (registry-level — no per-repo filtering)\n  [✓|✗] Replicated images: READ-ONLY in destination\n  [✓|✗] Pull-through cache rules: \u003Cprefix→upstream list> | none\n  [✓|✗] Replication lag: expected \u003CX> minutes (verified ImageReplicationStatus)\n  [✓|✗] Storage cost: \u003Csource + destinations> regions (doubles\u002Ftriples storage)\n  [✓|✗] Batch delete: BLOCKED on replicas (delete at source first)\n  [✓|✗] Lifecycle policies: applied in source AND destinations | WARNING (missing in destination)\n  [✓|✗] CloudWatch monitoring: ImageReplicationStatus alarm configured | not configured\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ecr describe-registry --region \u003Csource-region>\n  aws ecr describe-repositories --region \u003Cdestination-region>\n  aws cloudwatch get-metric-statistics --namespace AWS\u002FECR --metric-name ImageReplicationStatus\n```\n\n### Worked example — cross-region replication with pull-through cache\n\n```text\nECR_REPLICATION: 111122223333 (region: us-east-1) → us-west-2:111122223333, eu-west-1:111122223333\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Source registry: 111122223333 (region: us-east-1)\n  [✓] Replication type: Cross-region (same account)\n  [✓] Destinations: us-west-2:111122223333, eu-west-1:111122223333\n  [✓] Registry scope: ALL repositories (registry-level)\n  [✓] Replicated images: READ-ONLY in destination\n  [✓] Pull-through cache rules: docker-hub\u002F → registry-1.docker.io, quay\u002F → quay.io\n  [✓] Replication lag: expected 1-2 minutes (verified ImageReplicationStatus)\n  [✓] Storage cost: 3 regions (source + 2 destinations = 3x storage)\n  [✓] Batch delete: BLOCKED on replicas (delete at source first)\n  [✓] Lifecycle policies: applied in source AND destinations\n  [✓] CloudWatch monitoring: ImageReplicationStatus alarm configured\n  [✓] Tags: Environment=production, Pattern=multi-region\nVERIFICATION_COMMANDS:\n  aws ecr describe-registry --region us-east-1\n  aws ecr describe-repositories --region us-west-2\n  aws cloudwatch get-metric-statistics --namespace AWS\u002FECR --metric-name ImageReplicationStatus\n```\n\n## Error handling\nFailure modes and their fixes moved to\n[references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — mindset misconceptions, configuration dependency graph, read-only replica heuristic, recent AWS features (moved from this file)\n- [references\u002Fcross-region-and-cross-account.md](references\u002Fcross-region-and-cross-account.md) — cross-region\u002Fcross-account replication detail, registry-level scope heuristic, combined configuration example (heuristic and example moved from this file)\n- [references\u002Fpull-through-cache-and-cost.md](references\u002Fpull-through-cache-and-cost.md) — pull-through cache and cost detail, pull-through-vs-replication heuristic (moved from this file)\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — replication verify\u002Fstatus\u002Falarm commands (moved from this file)\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — replication not working, pull-through pull fails, batch delete on replica, storage cost (moved from this file)\n\n## Domain\n\nAWS CloudOps \u002F Amazon ECR Cross-Region and Cross-Account Replication\n& Pull-Through Cache Provisioning.\n\n## AWS documentation\n\n- **ECR replication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Freplication.html\n- **Cross-region replication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Freplication-cross-region.html\n- **Cross-account replication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Freplication-cross-account.html\n- **Pull-through cache** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Fpull-through-cache.html\n- **Pull-through cache rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Fcreate-pull-through-cache-rule.html\n- **Registry replication API** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002FAPIReference\u002FAPI_PutRegistryReplicationConfiguration.html\n- **CloudWatch ECR metrics** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Fcloudwatch-metrics.html\n- **ECR lifecycle policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Flifecycle_policy_definitions.html\n","# ECR Replication Deployer\n\nAn AWS CloudOps agent skill that provisions Amazon ECR cross-region\nand cross-account replication with correct defaults. The skill walks\nthe operator through registry-level replication configuration,\nreplication rules (source → destination), cross-account destination\nregistry IDs, pull-through cache rules for external registries\n(docker.io, quay.io, k8s.io, ecr-public), replication lag awareness,\ncost per replicated image (storage in both regions), CloudWatch\nmonitoring metrics (ImageReplicationStatus), batch delete protection\nfor replicated images, and deletion policy for source vs replica,\ncaptures all configuration decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\nconfigure ECR replication, ECR cross-region replication, ECR cross-\naccount replication, ECR pull-through cache, ECR replication rule,\nECR registry replication, ECR pull-through cache rule.\n\n## STRICT output contract\n\nWhen this skill is invoked with an ECR-replication-provisioning\nrequest (configure cross-region replication, set up cross-account\nreplication, create a pull-through cache rule, or a partial\nconfiguration), the agent MUST respond with the READY_TO_DEPLOY\nchecklist defined in the \"Output format\" section using the literal\nall-caps labels `ECR_REPLICATION:`, `VERDICT:`, `CHECKLIST:`, and\n`VERIFICATION_COMMANDS:`. Do NOT preface the checklist with prose,\nheadings, or disclaimers — emit the block as the first lines of the\nresponse. This contract is what assertion-based evals and downstream\nprovisioning pipelines rely on; deviating from the literal labels\nbreaks automation silently.\n\nIf any prerequisite is missing, the verdict is `PREREQUISITES_MISSING`\nwith a specific gap citation in the checklist (marked `[✗]`), and\n`READY_TO_DEPLOY` MUST NOT also appear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Registry-level replication model | Core model |\n| Step 2 — Cross-region replication | Same-account multi-region |\n| Step 3 — Cross-account replication | Cross-account sharing |\n| Step 4 — Pull-through cache rules | External registry caching |\n| Step 5 — Replication lag and timing | Eventual consistency |\n| Step 6 — Cost per replicated image | Storage cost awareness |\n| Step 7 — CloudWatch metrics | Monitoring |\n| Step 8 — Batch delete protection | Replica immutability |\n| Step 9 — Deletion policy (source vs replica) | Cleanup |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fcross-region-and-cross-account.md | Replication detail |\n| references\u002Fpull-through-cache-and-cost.md | Cache + cost detail |\n\n## Mindset\n\n**One-line takeaway:** ECR replication is configured at the REGISTRY\nlevel — ALL repositories in the source registry replicate to the\ndestination. You cannot replicate individual repositories.\nReplicated images are READ-ONLY in the destination (you cannot push\nto a replica). Pull-through cache rules let you cache external images\n(docker.io, quay.io, k8s.io, ecr-public) locally so that Lambda\u002FECS\npulls from the cached copy without hitting the external registry.\n\nThree misconceptions dominate ECR replication misdesign at\nprovisioning time:\n\nThe three provisioning misconceptions moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Configuration dependency graph (novel heuristic)\nFull dependency table and cross-dependency gotchas moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Expert heuristic: replication is registry-level\nRegistry-level scope tree and key implication moved to\n[references\u002Fcross-region-and-cross-account.md](references\u002Fcross-region-and-cross-account.md).\n\n## Expert heuristic: pull-through cache reduces external dependency\nPull-through-cache vs replication tree and key implications moved to\n[references\u002Fpull-through-cache-and-cost.md](references\u002Fpull-through-cache-and-cost.md).\n\n## Expert heuristic: replicated images are read-only\nReplica read-only operations tree and key implication moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## Prerequisites (verify before provisioning)\n\nBefore emitting provisioning commands, verify these prerequisites. If\nany are missing, the verdict is **PREREQUISITES_MISSING**.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| Source ECR registry exists | Replication source must be an existing registry | `aws ecr describe-registry` |\n| Source repositories have images | Replication copies existing and future images | `aws ecr describe-repositories` |\n| Destination region identified (cross-region) | Replication target region | Confirm region name |\n| Destination account ID (cross-account) | Cross-account replication needs 12-digit account ID | `aws sts get-caller-identity` (in destination) |\n| Destination registry allows replication (cross-account) | Destination must not have REPLICATION_DISALLOWED | Verify destination registry settings |\n| Upstream registry URL valid (pull-through cache) | Must be ecr-public, quay.io, docker.io, or k8s.io | Confirm upstream type |\n| IAM permission for ecr:PutReplicationConfiguration | Configuring replication requires this permission | Verify IAM policy |\n| Region settings support replication | Some restricted regions may not support ECR replication | Confirm region availability |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Registry-level replication model\n\nECR replication is configured at the registry level using\n`put-registry-replication-configuration`. This is a single API call\nthat defines all replication rules for the entire registry.\n\n| Concept | Description |\n|---|---|\n| Source registry | The registry where images are pushed (primary) |\n| Destination | The target region\u002Faccount where images are replicated |\n| Replication rule | A single source → destination mapping |\n| Scope | ALL repositories in the source registry (no per-repo filtering) |\n| Image state | Replicated images are READ-ONLY in the destination |\n\n```bash\n# Check current replication configuration\naws ecr describe-registry --region us-east-1\n```\n\n## Step 2 — Cross-region replication\n\nCross-region replication copies images from the source region to one\nor more destination regions within the SAME account.\n\n```bash\naws ecr put-registry-replication-configuration \\\n  --replication-configuration '{\n    \"rules\": [\n      {\n        \"destinations\": [\n          {\n            \"region\": \"us-west-2\",\n            \"registryId\": \"111122223333\"\n          },\n          {\n            \"region\": \"eu-west-1\",\n            \"registryId\": \"111122223333\"\n          }\n        ]\n      }\n    ]\n  }' \\\n  --region us-east-1\n```\n\n**Key points:**\n- `registryId` is the 12-digit AWS account ID (same for cross-region\n  within the same account).\n- Multiple destinations can be specified in a single rule.\n- Once configured, ALL repositories in us-east-1 replicate to both\n  us-west-2 and eu-west-1.\n\nVerify commands (push to source, check replica describe-images): [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n## Step 3 — Cross-account replication\n\nCross-account replication copies images from the source account to a\ndestination account. The destination account ID is specified as the\n`registryId`.\n\n```bash\naws ecr put-registry-replication-configuration \\\n  --replication-configuration '{\n    \"rules\": [\n      {\n        \"destinations\": [\n          {\n            \"region\": \"us-east-1\",\n            \"registryId\": \"999999999999\"\n          }\n        ]\n      }\n    ]\n  }' \\\n  --region us-east-1\n```\n\n**Critical:** the destination account (999999999999) must NOT have\nreplication disabled. By default, registries allow incoming\nreplication. If the destination has set the registry policy to\ndisallow replication, images will not replicate.\n\nCombined cross-region + cross-account configuration example moved to [references\u002Fcross-region-and-cross-account.md](references\u002Fcross-region-and-cross-account.md).\n\n## Step 4 — Pull-through cache rules\n\nPull-through cache rules fetch and cache external images in your ECR.\nWhen Lambda\u002FECS pulls an image matching a cache rule, ECR fetches it\nfrom the upstream registry and caches it locally.\n\n```bash\n# Create a pull-through cache rule for docker.io\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix docker-hub\u002F \\\n  --upstream-registry-url registry-1.docker.io \\\n  --region us-east-1\n\n# Create a pull-through cache rule for quay.io\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix quay\u002F \\\n  --upstream-registry-url quay.io \\\n  --region us-east-1\n\n# Create a pull-through cache rule for k8s.io\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix k8s\u002F \\\n  --upstream-registry-url registry.k8s.io \\\n  --region us-east-1\n\n# Create a pull-through cache rule for ecr-public\naws ecr create-pull-through-cache-rule \\\n  --ecr-repository-prefix ecr-public\u002F \\\n  --upstream-registry-url public.ecr.aws \\\n  --region us-east-1\n```\n\n**Supported upstream registries:**\n\n| Upstream | URL | ECR prefix example |\n|---|---|---|\n| Docker Hub | `registry-1.docker.io` | `docker-hub\u002F` |\n| Quay.io | `quay.io` | `quay\u002F` |\n| Kubernetes | `registry.k8s.io` | `k8s\u002F` |\n| ECR Public | `public.ecr.aws` | `ecr-public\u002F` |\n\n**Pulling a cached image:**\n\n```bash\n# Instead of: docker pull nginx:latest\n# Use the pull-through cache prefix:\ndocker pull 111122223333.dkr.ecr.us-east-1.amazonaws.com\u002Fdocker-hub\u002Flibrary\u002Fnginx:latest\n```\n\n**Key points:**\n- The `ecr-repository-prefix` maps to a namespace in your ECR. All\n  pulls via this prefix create repositories under that namespace.\n- The first pull triggers the cache fetch (slower); subsequent pulls\n  use the cached copy (faster).\n- Pull-through cache repositories are managed by ECR — you cannot\n  push to them manually.\n\n## Step 5 — Replication lag and timing\n\nReplication is asynchronous. After pushing an image to the source,\nthere is a lag before it appears in the destination.\n\n```text\nReplication lag expectations:\n  ├── Same-region cross-account: seconds to ~1 minute\n  ├── Cross-region (same continent): seconds to ~2 minutes\n  ├── Cross-region (intercontinental): 1-5 minutes\n  └── Large images (>1GB): add transfer time (proportional to size)\n```\n\nCloudWatch ImageReplicationStatus check command moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n**Important:** always verify replication completed before deploying\nfrom a replica. If the image has not replicated yet, pulls will fail\nwith `ImageNotFoundException`.\n\n## Step 6 — Cost per replicated image\n\nReplicated images incur storage costs in BOTH the source and\ndestination regions. This doubles the storage cost per image.\n\n```text\nCost model:\n  Source region: ECR storage cost per GB-month\n  Destination region: ECR storage cost per GB-month (SAME rate)\n  Total storage cost: 2x normal (source + each destination)\n\n  Data transfer:\n  ├── Source → Destination (replication): AWS data transfer rates\n  └── Destination → Lambda\u002FECS (pull): standard ECR data transfer (free in-region)\n```\n\n**Key implication:** replication doubles (or triples for multi-\ndestination) storage costs. For cost optimization:\n- Use lifecycle policies to prune old images in BOTH source and\n  destinations.\n- Replicate only to regions where you actually deploy.\n- Consider pull-through cache instead of replication for third-party\n  images (only one copy cached, not replicated across regions).\n\n## Step 7 — CloudWatch metrics for replication\n\nECR provides CloudWatch metrics for monitoring replication status.\n\n| Metric | Description |\n|---|---|\n| `ImageReplicationStatus` | Count of images by replication status (Complete, Failed, InProgress) |\n| `RepositoryCount` | Number of repositories in the registry |\n| `ImageCount` | Number of images across all repositories |\n| `StorageUsed` | Total storage used in bytes |\n\nCloudWatch alarm creation command for replication failures moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n## Step 8 — Batch delete protection for replicated images\n\nReplicated images CANNOT be batch-deleted in the destination\nregistry. They are read-only. This is a safety mechanism.\n\n```bash\n# This will FAIL on a replicated image in the destination:\naws ecr batch-delete-image \\\n  --repository-name my-app \\\n  --image-ids imageTag=latest \\\n  --region us-west-2\n# Error: ImageNotFoundException or \"replicated images cannot be deleted\"\n```\n\n**To remove a replicated image:**\n1. Delete the image at the SOURCE.\n2. Manually delete the orphaned replica in the destination (it is\n   now a regular image, not tied to a source image).\n\n**Important:** deleting the source image does NOT automatically\ndelete the replica. You must clean up the destination manually or use\na lifecycle policy in the destination.\n\n## Step 9 — Deletion policy (source vs replica)\n\n| Action | Source registry | Destination registry (replica) |\n|---|---|---|\n| Push image | Allowed | Denied (read-only) |\n| Delete image | Allowed (batch-delete-image) | Denied (batch-delete blocked on replicas) |\n| Delete repository | Allowed | Allowed (but replicas reappear if source re-pushes) |\n| Lifecycle policy | Runs independently | Runs independently (apply to both) |\n\n**Recommended deletion workflow:**\n\n```text\n1. Delete image at source:\n   aws ecr batch-delete-image --repository-name my-app --image-ids imageTag=v1.0 --region us-east-1\n\n2. Delete orphaned replica in each destination:\n   aws ecr batch-delete-image --repository-name my-app --image-ids imageTag=v1.0 --region us-west-2\n   (This works AFTER the source image is deleted — the replica becomes a standalone image)\n\n3. Apply lifecycle policies in BOTH source and destinations for automated cleanup.\n```\n\n## Step 10 — Recent features\nRecent AWS feature notes (2023-2026) moved to\n[references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md).\n\n## NEVER do these things\n\n1. **NEVER assume replication is per-repository.** Replication is at\n   the REGISTRY level. Configuring replication replicates ALL repos.\n   Use cross-account repo policies for selective sharing.\n\n2. **NEVER try to push to a replicated image in the destination.**\n   Replicated images are READ-ONLY. Push to the source only.\n\n3. **NEVER assume deleting the source image deletes the replica.**\n   The replica becomes orphaned and must be deleted manually in the\n   destination, or cleaned up via lifecycle policy.\n\n4. **NEVER use batch-delete-image on a replicated image in the\n   destination while it is still linked to the source.** It will\n   fail. Delete the source image first, then the orphaned replica.\n\n5. **NEVER configure pull-through cache with an unsupported upstream\n   URL.** Only `registry-1.docker.io`, `quay.io`, `registry.k8s.io`,\n   and `public.ecr.aws` are supported. Custom URLs are rejected.\n\n6. **NEVER ignore replication lag before deploying from a replica.**\n   Always check `ImageReplicationStatus` to confirm the image has\n   replicated. Deploying from a non-replicated image fails with\n   `ImageNotFoundException`.\n\n7. **NEVER forget that replication doubles storage costs.** Each\n   destination region incurs the same storage cost as the source.\n   Apply lifecycle policies in BOTH source and destinations.\n\n8. **NEVER configure cross-account replication without verifying the\n   destination allows it.** If the destination has\n   `REPLICATION_DISALLOWED`, replication silently fails.\n\n9. **NEVER confuse pull-through cache with replication.** Pull-\n   through cache fetches EXTERNAL images into your ECR. Replication\n   copies YOUR images across regions\u002Faccounts.\n\n10. **NEVER assume replication is instant for large images.**\n    Replication lag for multi-GB images can be minutes. Always verify\n    before deploying.\n\n## Output format\n\n```text\nECR_REPLICATION: \u003Csource-registry-id> (region: \u003Csource-region>) → \u003Cdestinations>\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Source registry: \u003Cregistry-id> (region: \u003Csource-region>)\n  [✓|✗] Replication type: Cross-region | Cross-account | Both | Pull-through cache\n  [✓|✗] Destinations: \u003Cregion:registry-id list>\n  [✓|✗] Registry scope: ALL repositories (registry-level — no per-repo filtering)\n  [✓|✗] Replicated images: READ-ONLY in destination\n  [✓|✗] Pull-through cache rules: \u003Cprefix→upstream list> | none\n  [✓|✗] Replication lag: expected \u003CX> minutes (verified ImageReplicationStatus)\n  [✓|✗] Storage cost: \u003Csource + destinations> regions (doubles\u002Ftriples storage)\n  [✓|✗] Batch delete: BLOCKED on replicas (delete at source first)\n  [✓|✗] Lifecycle policies: applied in source AND destinations | WARNING (missing in destination)\n  [✓|✗] CloudWatch monitoring: ImageReplicationStatus alarm configured | not configured\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ecr describe-registry --region \u003Csource-region>\n  aws ecr describe-repositories --region \u003Cdestination-region>\n  aws cloudwatch get-metric-statistics --namespace AWS\u002FECR --metric-name ImageReplicationStatus\n```\n\n### Worked example — cross-region replication with pull-through cache\n\n```text\nECR_REPLICATION: 111122223333 (region: us-east-1) → us-west-2:111122223333, eu-west-1:111122223333\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Source registry: 111122223333 (region: us-east-1)\n  [✓] Replication type: Cross-region (same account)\n  [✓] Destinations: us-west-2:111122223333, eu-west-1:111122223333\n  [✓] Registry scope: ALL repositories (registry-level)\n  [✓] Replicated images: READ-ONLY in destination\n  [✓] Pull-through cache rules: docker-hub\u002F → registry-1.docker.io, quay\u002F → quay.io\n  [✓] Replication lag: expected 1-2 minutes (verified ImageReplicationStatus)\n  [✓] Storage cost: 3 regions (source + 2 destinations = 3x storage)\n  [✓] Batch delete: BLOCKED on replicas (delete at source first)\n  [✓] Lifecycle policies: applied in source AND destinations\n  [✓] CloudWatch monitoring: ImageReplicationStatus alarm configured\n  [✓] Tags: Environment=production, Pattern=multi-region\nVERIFICATION_COMMANDS:\n  aws ecr describe-registry --region us-east-1\n  aws ecr describe-repositories --region us-west-2\n  aws cloudwatch get-metric-statistics --namespace AWS\u002FECR --metric-name ImageReplicationStatus\n```\n\n## Error handling\nFailure modes and their fixes moved to\n[references\u002Ferror-handling.md](references\u002Ferror-handling.md).\n\n## References (load on demand)\n\n- [references\u002Fadvanced-patterns.md](references\u002Fadvanced-patterns.md) — mindset misconceptions, configuration dependency graph, read-only replica heuristic, recent AWS features (moved from this file)\n- [references\u002Fcross-region-and-cross-account.md](references\u002Fcross-region-and-cross-account.md) — cross-region\u002Fcross-account replication detail, registry-level scope heuristic, combined configuration example (heuristic and example moved from this file)\n- [references\u002Fpull-through-cache-and-cost.md](references\u002Fpull-through-cache-and-cost.md) — pull-through cache and cost detail, pull-through-vs-replication heuristic (moved from this file)\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — replication verify\u002Fstatus\u002Falarm commands (moved from this file)\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — replication not working, pull-through pull fails, batch delete on replica, storage cost (moved from this file)\n\n## Domain\n\nAWS CloudOps \u002F Amazon ECR Cross-Region and Cross-Account Replication\n& Pull-Through Cache Provisioning.\n\n## AWS documentation\n\n- **ECR replication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Freplication.html\n- **Cross-region replication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Freplication-cross-region.html\n- **Cross-account replication** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Freplication-cross-account.html\n- **Pull-through cache** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Fpull-through-cache.html\n- **Pull-through cache rules** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Fcreate-pull-through-cache-rule.html\n- **Registry replication API** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002FAPIReference\u002FAPI_PutRegistryReplicationConfiguration.html\n- **CloudWatch ECR metrics** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Fcloudwatch-metrics.html\n- **ECR lifecycle policies** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAmazonECR\u002Flatest\u002Fuserguide\u002Flifecycle_policy_definitions.html\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":41},{"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,"dependencies":37,"requires_llm":38,"verdict_shape":39,"lifecycle_status":40,"supports_pipeline":38},"aws, ecr, replication, cloudops, deploy, devtools, provisioning, cross-region, cross-account, pull-through-cache, container-registry","1","Jacky Chan — AWS Community Builder","aws-cloudops","DevTools","0.1.0","aws, ecr, elastic container registry, replication, cross-region, cross-account, pull-through cache, cloudops, deploy, provisioning, container registry, docker, devtools","deploy","high","false","capability","Invoke when the user wants to configure ECR cross-region replication, cross-account ECR replication, ECR pull-through cache rules (for docker.io, quay.io, k8s.io, ecr-public upstream registries), multi-region container image availability for DR, or understand replication lag and cost implications. Do NOT invoke for ECR repository lifecycle policies (separate skill), ECR image scanning, or ECS\u002FEKS task deployment.","aws-orchestrator","true","READY_TO_DEPLOY | PREREQUISITES_MISSING","active","Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ecr access (and cross-account IAM if cross-account replication). Works with Terraform aws_ecr_replication_configuration \u002F aws_ecr_pull_through_cache_rule resources and CloudFormation AWS::ECR::ReplicationConfiguration templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fecr-replication-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":51,"prompt":61,"zipAvailable":62},[52,55,58],{"tool":53,"command":54},"npx","npx skills add jhkchan\u002Faws-agent-skills --skill ecr-replication-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill ecr-replication-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill ecr-replication-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002FSKILL.md",true,[64,70,74,78,82,86,90,94,98,102,106,110,114,118,122,126,130,134,138,142],{"path":65,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":68,"sourceHtmlUrl":69},"eval\u002Ftest-cases.yaml","REFERENCE","参考文档",5534,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcross-account-replication.md",771,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fbaselines\u002Fcross-account-replication.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fcross-region-replication.md",838,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fbaselines\u002Fcross-region-replication.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-destination-registry-id.md",715,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fbaselines\u002Fmissing-destination-registry-id.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Fmulti-region-dr-with-lifecycle.md",951,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fbaselines\u002Fmulti-region-dr-with-lifecycle.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fpull-through-cache-docker-hub.md",653,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fbaselines\u002Fpull-through-cache-docker-hub.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1838,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",9935,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcross-account-replication.md",488,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fprompts\u002Fcross-account-replication.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fcross-region-replication.md",450,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fprompts\u002Fcross-region-replication.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-destination-registry-id.md",400,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fprompts\u002Fmissing-destination-registry-id.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Fmulti-region-dr-with-lifecycle.md",541,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fprompts\u002Fmulti-region-dr-with-lifecycle.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fpull-through-cache-docker-hub.md",549,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fevals\u002Fprompts\u002Fpull-through-cache-docker-hub.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6337,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",6668,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fcross-region-and-cross-account.md",10438,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Freferences\u002Fcross-region-and-cross-account.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fdiagnostic-commands.md",1608,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ferror-handling.md",1177,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Freferences\u002Ferror-handling.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fpull-through-cache-and-cost.md",9838,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Freferences\u002Fpull-through-cache-and-cost.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4608,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fecr-replication-deployer\u002Fskill.usf.yaml",[147,154,161,168,175,182],{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"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":155,"name":156,"nameZh":6,"description":157,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":158,"categories":159,"keywords":160,"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":162,"name":163,"nameZh":6,"description":164,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":165,"categories":166,"keywords":167,"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":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":174,"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":176,"name":177,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"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":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":188,"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",[],[]]