[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A7EJK9KH2H7JDWFJRFDM67":3,"skill-same:01M7A7EJK9KH2H7JDWFJRFDM67":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},"01M7A7EJK9KH2H7JDWFJRFDM67","ec2-spot-fleet-deployer",null,"Provisions EC2 Spot Fleets with production defaults: launch template configuration, Spot Fleet request (target capacity, allocation strategy: lowestPrice\u002FcapacityOptimized\u002Fdiversified\u002F priceCapacityOptimized), instance pools, fleet type (request\u002Fmaintain), replacement strategies, capacity rebalance, Spot placement score, capacity reservations. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Spot Fleet request, choosing an allocation strategy, configuring instance diversification, enabling capacity rebalance, or integrating Spot Fleets with capacity reservations. Triggers: create spot fleet, EC2 Spot Fleet request, spot instance pool, allocation strategy, capacity rebalance, spot placement score, priceCapacityOptimized, lowestPrice spot, capacityOptimized spot, diversified spot fleet, maintain spot fleet.","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\u002Fec2-spot-fleet-deployer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: ec2-spot-fleet-deployer\ndescription: 'Provisions EC2 Spot Fleets with production defaults: launch template configuration, Spot Fleet request (target capacity, allocation strategy: lowestPrice\u002FcapacityOptimized\u002Fdiversified\u002F priceCapacityOptimized), instance pools, fleet type (request\u002Fmaintain), replacement strategies, capacity rebalance, Spot placement score, capacity reservations. Emits a READY_TO_DEPLOY checklist with verification commands. Use when creating a Spot Fleet request, choosing an allocation strategy, configuring instance diversification, enabling capacity rebalance, or integrating Spot Fleets with capacity reservations. Triggers: create spot fleet, EC2 Spot Fleet request, spot instance pool, allocation strategy, capacity rebalance, spot placement score, priceCapacityOptimized, lowestPrice spot, capacityOptimized spot, diversified spot fleet, maintain spot fleet.'\nlicense: Apache-2.0\ncompatibility: 'Agent runtime that reads SKILL.md (Claude Code, Cursor, Windsurf, Codex, Gemini). For live deployment: AWS CLI v2 with ec2, iam, and service-roles access. Works with Terraform aws_spot_fleet_request resources and CloudFormation AWS::EC2::SpotFleet 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: Compute\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, ec2, spot-fleet, cloudops, deploy, compute, provisioning, allocation-strategy, capacity-rebalance, launch-template, spot-instances\n  dependencies: aws-orchestrator\n  keywords: aws, ec2, spot fleet, spot instances, cloudops, deploy, provisioning, allocation strategy, lowestPrice, capacityOptimized, diversified, priceCapacityOptimized, instance pools, target capacity, capacity rebalance, spot placement score, capacity reservations, launch template, fleet type, maintain\n  when_to_use: Invoke when the user wants to create an EC2 Spot Fleet request (maintain or one-time request), select an allocation strategy (lowestPrice, capacityOptimized, diversified, priceCapacityOptimized), configure instance pool diversification, enable capacity rebalance and replacement, use Spot placement score for capacity awareness, or integrate Spot Fleets with capacity reservations. Do NOT invoke for single Spot Instance requests (use RunInstances with InstanceMarketOptions), for On-Demand Capacity Reservations standalone (use capacity-reservation operators), for EC2 Auto Scaling Groups with mixed instances (use autoscaling-policy-deployer), or for auditing existing Spot Fleet configurations (use autoscaling-group-auditor).\n---\n\n# EC2 Spot Fleet Deployer\n\nAn AWS CloudOps agent skill that provisions EC2 Spot Fleets with\ncorrect defaults. The skill walks the operator through fleet type\nselection, launch template configuration, allocation strategy\nchoice, instance pool diversification, target capacity, replacement\nstrategies, capacity rebalance, and Spot placement score. It\ncaptures capacity and cost decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate Spot Fleet, EC2 Spot Fleet request, spot allocation\nstrategy, capacity rebalance spot, Spot placement score,\npriceCapacityOptimized, lowestPrice spot, capacityOptimized spot,\ndiversified Spot Fleet, maintain Spot Fleet, Spot instance pool,\ntarget capacity, Spot Fleet launch template.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Spot-Fleet-provisioning request\n(fleet type, allocation strategy, instance types, target capacity,\nor a partial configuration), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section\nusing the literal all-caps labels `SPOT_FLEET:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the\nchecklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-\nbased evals and downstream provisioning pipelines rely on;\ndeviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is\n`PREREQUISITES_MISSING` with a specific gap citation in the\nchecklist (marked `[✗]`), and `READY_TO_DEPLOY` MUST NOT also\nappear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Fleet type (maintain vs request) | Fleet lifecycle decision |\n| Step 2 — Launch template configuration | AMI, instance type, network |\n| Step 3 — Allocation strategy | Cost vs capacity trade-off |\n| Step 4 — Instance pools and diversification | Interruption resilience |\n| Step 5 — Target capacity (units vs vCPUs) | Sizing |\n| Step 6 — Replacement strategies | Interruption handling |\n| Step 7 — Capacity rebalance | Proactive rebalancing |\n| Step 8 — Spot placement score | Capacity-aware launch |\n| Step 9 — Capacity reservations integration | Guaranteed capacity |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fallocation-strategies.md | Strategy deep dive |\n| references\u002Fprovisioning-cli-commands.md | Copy-pasteable CLI sequence |\n\n## Mindset\nFull mindset and the 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: allocation strategy selection\nWorkload-profile decision framework and key implications moved to\n[references\u002Fallocation-strategies.md](references\u002Fallocation-strategies.md).\n\n## Expert heuristic: capacity rebalance and replacement\nRebalance-vs-default-replacement comparison, lifecycle, and enabling JSON 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.\nIf any are missing, the verdict is **PREREQUISITES_MISSING** with a\nspecific gap citation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account with EC2 Spot Fleet access | Cannot provision without it | `aws sts get-caller-identity` |\n| Region selected | Instance types and AZ availability vary by region | `aws configure get region` |\n| IAM service role for Spot Fleet | Spot Fleet needs `AWSServiceRoleForEC2SpotFleet` to launch instances | `aws iam get-role --role-name AWSServiceRoleForEC2SpotFleet` |\n| Launch template exists (or create one) | Fleet needs a standardized instance configuration | `aws ec2 describe-launch-templates` |\n| AMI valid in the region | AMIs are region-scoped; cross-region AMI IDs are invalid | `aws ec2 describe-images --image-ids \u003Cami-id>` |\n| Instance types available in the region | Not all instance types are available in all regions\u002FAZs | `aws ec2 describe-instance-types --instance-types \u003Ctype>` |\n| At least 2-3 instance types specified | Single-type fleets have no diversification fallback | List in the Overrides |\n| At least 2 AZs specified | Single-AZ fleets lose all capacity on AZ failure | List AZs in Overrides |\n| Target capacity identified | Determines fleet size; `maintain` fleets auto-adjust | Positive integer |\n| Spot placement score (optional) | Pre-check capacity availability before creating fleet | `aws ec2 get-spot-placement-scores` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Fleet type (maintain vs request)\n\nThe first decision is whether the fleet should continuously maintain\nits target capacity or fill it once and stop.\n\n**Decision tree:**\n```text\nDoes the workload need continuous capacity (long-running, stateless)?\n├── YES → Fleet type: maintain\n│         AWS continuously monitors and replaces interrupted instances.\n│         Target capacity can be modified (scale up\u002Fdown).\n│         Capacity rebalance can be enabled.\n│         Use for: web servers, batch processing, CI\u002FCD workers\n└── NO  → Is this a one-time burst (job queue, HPC, data processing)?\n    ├── YES → Fleet type: request\n    │         Fleet fills once and stops. No replacement.\n    │         Target capacity CANNOT be modified after creation.\n    │         Capacity rebalance is silently ignored.\n    │         Use for: one-time HPC jobs, data migration, burst compute\n    └── NO  → Fleet type: maintain (the safe default)\n```\n\n**Feature comparison:**\n\n| Feature | maintain | request |\n|---|---|---|\n| Replacement on interruption | Yes (automatic) | No |\n| Target capacity modification | Yes (live) | No (immutable) |\n| Capacity rebalance | Supported | Not supported (ignored) |\n| Excess capacity termination | Configurable | N\u002FA |\n| Expiry | Until cancelled | Fills once, then done |\n| Best for | Long-running workloads | One-time burst jobs |\n\n**Common mistake:** using `request` for a web tier and expecting\nAWS to replace interrupted instances. It will not — the fleet fills\nonce and stops. Use `maintain`.\n\n## Step 2 — Launch template configuration\n\nA launch template defines the instance configuration: AMI, instance\ntype, key pair, security groups, IAM instance profile, user data,\nand storage. The Spot Fleet references the launch template and\noverrides instance type and AZ via the Overrides array.\n\n**Create a launch template:**\n```bash\naws ec2 create-launch-template \\\n  --launch-template-name spot-fleet-web-server \\\n  --launch-template-data '{\n    \"ImageId\": \"ami-0abcdef1234567890\",\n    \"InstanceType\": \"m5.large\",\n    \"KeyName\": \"my-key-pair\",\n    \"SecurityGroupIds\": [\"sg-0abc123\"],\n    \"IamInstanceProfile\": { \"Arn\": \"arn:aws:iam::123456789012:instance-profile\u002Fspot-fleet-role\" },\n    \"UserData\": \"'$(base64 user-data.sh)'\",\n    \"BlockDeviceMappings\": [{\n      \"DeviceName\": \"\u002Fdev\u002Fxvda\",\n      \"Ebs\": { \"VolumeSize\": 30, \"VolumeType\": \"gp3\", \"DeleteOnTermination\": true }\n    }],\n    \"TagSpecifications\": [{\n      \"ResourceType\": \"instance\",\n      \"Tags\": [\n        { \"Key\": \"Name\", \"Value\": \"spot-fleet-web\" },\n        { \"Key\": \"Environment\", \"Value\": \"production\" }\n      ]\n    }]\n  }'\n```\n\n**Key rules:**\n- The instance type in the launch template is the DEFAULT; the\n  Spot Fleet Overrides override it per pool.\n- The AMI must be valid in the fleet's region.\n- EBS volumes should be `DeleteOnTermination: true` for Spot\n  (otherwise orphaned volumes accumulate cost).\n- Tag the instances at launch (launch-template tags are more\n  reliable than Spot Fleet-level tags).\n\n## Step 3 — Allocation strategy\n\nSee the \"Expert heuristic: allocation strategy selection\" section\nabove for the decision framework. Summary:\n\n| Strategy | Picks pools based on | Diversification | Interruption risk | Cost |\n|---|---|---|---|---|\n| `priceCapacityOptimized` | Price + capacity availability (RECOMMENDED) | Implicit (multi-pool) | Low-Medium | Low |\n| `capacityOptimized` | Capacity availability (max free capacity) | Implicit (multi-pool) | Lowest | Medium |\n| `lowestPrice` | Lowest price per AZ | None (concentrates) | Highest | Lowest |\n| `diversized` | Even spread across all pools | Explicit (equal) | Low | Medium |\n\n**Setting the allocation strategy:**\n```json\n{\n  \"AllocationStrategy\": \"priceCapacityOptimized\",\n  \"TargetCapacitySpecification\": {\n    \"TotalTargetCapacity\": 10,\n    \"DefaultTargetCapacityType\": \"spot\"\n  }\n}\n```\n\n**Common mistake:** using `lowestPrice` with a single instance type.\nThe fleet concentrates in one pool and is interrupted all at once.\nAlways use `priceCapacityOptimized` or `capacityOptimized` unless you\nhave a specific cost-optimization requirement with many (10+) instance\ntypes.\n\n## Step 4 — Instance pools and diversification\n\nInstance pools are unique combinations of instance type + AZ. The\nSpot Fleet draws from these pools based on the allocation strategy.\nMore pools = better diversification = lower interruption risk.\n\n**Overrides specify the pools (9 pools = 3 types x 3 AZs):**\n```json\n\"LaunchTemplateConfigs\": [{\n  \"LaunchTemplateSpecification\": { \"LaunchTemplateId\": \"lt-0abc123\", \"Version\": \"1\" },\n  \"Overrides\": [\n    { \"InstanceType\": \"m5.large\",  \"AvailabilityZone\": \"us-east-1a\" },\n    { \"InstanceType\": \"m5.large\",  \"AvailabilityZone\": \"us-east-1b\" },\n    { \"InstanceType\": \"m5.large\",  \"AvailabilityZone\": \"us-east-1c\" },\n    { \"InstanceType\": \"m5a.large\", \"AvailabilityZone\": \"us-east-1a\" },\n    { \"InstanceType\": \"c5.large\",  \"AvailabilityZone\": \"us-east-1b\" },\n    { \"InstanceType\": \"c5.large\",  \"AvailabilityZone\": \"us-east-1c\" }\n  ]\n}]\n```\n\n**Diversification best practices:**\n- Specify at least 2-3 instance types (e.g., m5, m5a, c5).\n- Specify at least 3 AZs (all AZs in the region).\n- This gives 9+ pools, dramatically reducing interruption risk.\n- Use instance type families with similar vCPU\u002Fmemory ratios so\n  your workload scales predictably.\n- Consider using `InstanceRequirements` (attribute-based) instead of\n  specific types for flexible selection.\n\n**Attribute-based instance selection (InstanceRequirements):**\n```json\n\"Overrides\": [\n  {\n    \"InstanceRequirements\": {\n      \"VCpuCount\": { \"Min\": 2, \"Max\": 4 },\n      \"MemoryMiB\": { \"Min\": 8192 },\n      \"AcceleratorCount\": { \"Max\": 0 },\n      \"BurstablePerformance\": \"excluded\"\n    },\n    \"AvailabilityZone\": \"us-east-1a\"\n  }\n]\n```\n\nThis lets AWS pick any instance type matching the requirements,\nmaximizing pool count.\n\n## Step 5 — Target capacity (units vs vCPUs vs instances)\n\nTarget capacity can be measured in three ways:\n\n| Unit type | How it works | When to use |\n|---|---|---|\n| `units` | Weighted: each override has a `WeightedCapacity` value | Mixed-size fleets (some instances count as 2 units, others as 1) |\n| `vcpu` | Each instance counts as its vCPU count | vCPU-based capacity planning |\n| `instances` (default) | Each instance counts as 1 | Simple equal-weight fleets |\n\n```json\n\"TargetCapacitySpecification\": {\n  \"TotalTargetCapacity\": 20,\n  \"DefaultTargetCapacityType\": \"spot\",\n  \"TargetCapacityUnitType\": \"vcpu\"\n}\n```\n\n**Common mistake:** using `instances` with mixed instance types\nwhere some are 2x the size of others. The fleet thinks it needs 20\ninstances, but if it picks large instances, you have way more\ncapacity than intended. Use `vcpu` or `units` for mixed fleets.\n\n## Step 6 — Replacement strategies (InstanceInterruptionBehavior)\n\nWhen a Spot Instance is interrupted, the fleet's behavior depends\non `InstanceInterruptionBehavior`:\n\n| Behavior | What happens to the interrupted instance | When to use |\n|---|---|---|\n| `terminate` (default) | Instance is terminated (EBS volumes deleted if DeleteOnTermination) | Stateless workloads |\n| `stop` | Instance is stopped (can be restarted later) | Stateful workloads that can resume |\n| `hibernate` | Instance is hibernated (RAM saved to disk) | Long-running jobs with checkpointing |\n\n```json\n{\n  \"InstanceInterruptionBehavior\": \"terminate\",\n  \"SpotMaintenanceStrategies\": {\n    \"CapacityRebalance\": {\n      \"ReplacementStrategy\": \"launch\"\n    }\n  }\n}\n```\n\n**Key rule:** `InstanceInterruptionBehavior` is set at the Spot\nFleet request level and applies to ALL instances in the fleet. It\ncannot be overridden per-instance after launch.\n\n## Step 7 — Capacity rebalance\n\nSee the \"Expert heuristic: capacity rebalance and replacement\"\nsection above for the full lifecycle. Summary configuration:\n\n```json\n\"SpotMaintenanceStrategies\": {\n  \"CapacityRebalance\": {\n    \"ReplacementStrategy\": \"launch\"\n  }\n}\n```\n\n**Replacement strategies:**\n- `launch` (default): Fleet launches a new replacement instance\n  BEFORE terminating the old one. This is the recommended strategy.\n- `terminate`: Fleet terminates the old instance immediately and\n  then launches a replacement. Higher risk of capacity gap.\n\n**Requirements:**\n- Fleet type MUST be `maintain`.\n- Fleet MUST have `InstanceInterruptionBehavior` set to `terminate`\n  or `stop`.\n- The replacement instance is launched from the same launch\n  template + overrides.\n\n**Common mistake:** enabling capacity rebalance on a `request` fleet.\nIt is silently ignored. Only `maintain` fleets support rebalancing.\n\n## Step 8 — Spot placement score\n\nSpot placement score is a pre-flight capacity check. Before creating\na fleet, query the score to see which instance type + AZ\ncombinations have the best capacity availability.\n\nQuery command and sample output moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n**Score interpretation:**\n- Score 1-3: Low availability. High interruption risk. Avoid.\n- Score 4-7: Medium availability. Acceptable for fault-tolerant.\n- Score 8-10: High availability. Low interruption risk. Prefer.\n\n**Key implication:** Spot placement score is ADVISORY ONLY. It does\nnot reserve capacity. The fleet may still be interrupted in a\nhigh-scoring pool if overall Spot demand spikes.\n\n**When to use:** Before creating large fleets (>100 instances),\nwhen choosing between instance types, or before scaling up.\n\n## Step 9 — Capacity reservations integration\n\nOn-Demand Capacity Reservations (ODCR) can be used alongside Spot\nFleets. When the fleet launches in an AZ+instance-type combination\nthat has an open ODCR, the ODCR is consumed first (guaranteed\ncapacity, On-Demand billing), then Spot fills the rest.\n\n**Configuration for ODCR preference:**\n```json\n{\n  \"LaunchTemplateConfigs\": [{\n    \"LaunchTemplateSpecification\": { \"LaunchTemplateId\": \"lt-0abc123\", \"Version\": \"1\" },\n    \"Overrides\": [{\n      \"InstanceType\": \"m5.large\",\n      \"AvailabilityZone\": \"us-east-1a\"\n    }]\n  }],\n  \"TargetCapacitySpecification\": {\n    \"TotalTargetCapacity\": 10,\n    \"OnDemandTargetCapacity\": 3,\n    \"DefaultTargetCapacityType\": \"spot\"\n  },\n  \"OnDemandOptions\": {\n    \"CapacityReservationOptions\": {\n      \"UsageStrategy\": \"use-capacity-reservations-first\"\n    }\n  }\n}\n```\n\n**Key rules:**\n- ODCR must match instance type + AZ + platform exactly.\n- `OnDemandTargetCapacity` specifies how many units to run as\n  On-Demand (consumed from ODCR if available).\n- The rest of the fleet runs as Spot.\n- This gives a hybrid: guaranteed capacity for critical instances +\n  cost savings for the rest.\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 use `lowestPrice` with a single instance type.** The\n   fleet concentrates in one pool. When that pool is reclaimed, the\n   entire fleet is interrupted simultaneously with no fallback. Use\n   `priceCapacityOptimized` with at least 3 instance types.\n\n2. **NEVER use `request` fleet type for long-running workloads.**\n   A `request` fleet fills once and stops. It does NOT replace\n   interrupted instances. Use `maintain` for any workload that\n   needs continuous capacity.\n\n3. **NEVER specify only one instance type or one AZ.** Single-type\n   or single-AZ fleets have no diversification. Always specify 2-3+\n   instance types across 3+ AZs for interruption resilience.\n\n4. **NEVER enable capacity rebalance on a `request` fleet.** It is\n   silently ignored. Capacity rebalance only works with `maintain`\n   fleet type. Verify fleet type before configuring rebalance.\n\n5. **NEVER treat Spot placement score as a capacity guarantee.** It\n   is advisory only. A score of 10 does not reserve capacity. Use\n   it to avoid low-scoring pools, not as a reservation.\n\n## Output format\n\n```text\nSPOT_FLEET: \u003Cfleet-id> (allocation strategy: \u003Cstrategy>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Fleet type: maintain | request\n  [✓|✗] Allocation strategy: priceCapacityOptimized | capacityOptimized | lowestPrice | diversified\n  [✓|✗] Launch template: \u003Clt-id> (version \u003Cn>)\n  [✓|✗] Instance types: \u003Ctype-1>, \u003Ctype-2>, \u003Ctype-3> (in \u003Cn> AZs = \u003Cpool-count> pools)\n  [✓|✗] Target capacity: \u003Cn> \u003Cunit-type> (spot: \u003Cn>, on-demand: \u003Cn>)\n  [✓|✗] InstanceInterruptionBehavior: terminate | stop | hibernate\n  [✓|✗] Capacity rebalance: enabled (launch strategy) | disabled\n  [✓|✗] Spot placement score: checked (top pool score: \u003Cscore>) | not checked\n  [✓|✗] Capacity reservations (ODCR): used-first (\u003Cn> On-Demand units) | not used\n  [✓|✗] IAM service role: AWSServiceRoleForEC2SpotFleet\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ec2 describe-spot-fleet-requests --spot-fleet-request-ids \u003Cfleet-id>\n  aws ec2 describe-spot-fleet-instances --spot-fleet-request-id \u003Cfleet-id>\n  aws ec2 describe-spot-fleet-request-history --spot-fleet-request-id \u003Cfleet-id>\n```\n\n### Worked example — maintain fleet with priceCapacityOptimized and rebalance\n\n```text\nSPOT_FLEET: sfr-1234567890abcdef0 (allocation strategy: priceCapacityOptimized)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Fleet type: maintain\n  [✓] Allocation strategy: priceCapacityOptimized\n  [✓] Launch template: lt-0abc123def456 (version 1)\n  [✓] Instance types: m5.large, m5a.large, c5.large (in 3 AZs = 9 pools)\n  [✓] Target capacity: 20 vcpu (spot: 20, on-demand: 0)\n  [✓] InstanceInterruptionBehavior: terminate\n  [✓] Capacity rebalance: enabled (launch strategy)\n  [✓] Spot placement score: checked (top pool score: 10)\n  [✓] Capacity reservations (ODCR): not used\n  [✓] IAM service role: AWSServiceRoleForEC2SpotFleet\n  [✓] Tags: Environment=production, Service=batch-processing\nVERIFICATION_COMMANDS:\n  aws ec2 describe-spot-fleet-requests --spot-fleet-request-ids sfr-1234567890abcdef0\n  aws ec2 describe-spot-fleet-instances --spot-fleet-request-id sfr-1234567890abcdef0\n  aws ec2 describe-spot-fleet-request-history --spot-fleet-request-id sfr-1234567890abcdef0\n```\n\n## Error handling\nFleet failure 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, capacity rebalance deep dive, recent AWS features (moved from this file)\n- [references\u002Fallocation-strategies.md](references\u002Fallocation-strategies.md) — allocation-strategy workload-profile heuristic (moved from this file) plus the strategy comparison matrix and decision framework\n- [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md) — full copy-pasteable provisioning CLI sequence\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — Spot placement score query and sample output (moved from this file)\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — fleet stuck\u002Fpartially filled, rebalance not working, MaxSpotInstanceCountExceeded, immutable allocation strategy (moved from this file)\n\n## Domain\n\nAWS CloudOps \u002F EC2 Spot Fleet Provisioning & Cost-Optimized Compute\nCapacity Management.\n\n## AWS documentation\n\n- **Spot Fleet User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-fleet.html\n- **Allocation strategies** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-fleet-allocation-strategy.html\n- **Capacity rebalance** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fcapacity-rebalance.html\n- **Spot placement score** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-placement-score.html\n- **Spot Fleet request options** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-request-options.html\n- **Instance interruption behavior** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-interruptions.html\n- **On-Demand Capacity Reservations** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fec2-capacity-reservations.html\n- **Attribute-based instance selection** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-instance-request-types.html#attribute-based-instance-type-selection\n","# EC2 Spot Fleet Deployer\n\nAn AWS CloudOps agent skill that provisions EC2 Spot Fleets with\ncorrect defaults. The skill walks the operator through fleet type\nselection, launch template configuration, allocation strategy\nchoice, instance pool diversification, target capacity, replacement\nstrategies, capacity rebalance, and Spot placement score. It\ncaptures capacity and cost decisions, explains why each default\nmatters, and emits a READY_TO_DEPLOY checklist with copy-pasteable\nverification commands.\n\n## Activation keywords\n\ncreate Spot Fleet, EC2 Spot Fleet request, spot allocation\nstrategy, capacity rebalance spot, Spot placement score,\npriceCapacityOptimized, lowestPrice spot, capacityOptimized spot,\ndiversified Spot Fleet, maintain Spot Fleet, Spot instance pool,\ntarget capacity, Spot Fleet launch template.\n\n## STRICT output contract\n\nWhen this skill is invoked with a Spot-Fleet-provisioning request\n(fleet type, allocation strategy, instance types, target capacity,\nor a partial configuration), the agent MUST respond with the\nREADY_TO_DEPLOY checklist defined in the \"Output format\" section\nusing the literal all-caps labels `SPOT_FLEET:`, `VERDICT:`,\n`CHECKLIST:`, and `VERIFICATION_COMMANDS:`. Do NOT preface the\nchecklist with prose, headings, or disclaimers — emit the block as\nthe first lines of the response. This contract is what assertion-\nbased evals and downstream provisioning pipelines rely on;\ndeviating from the literal labels breaks automation silently.\n\nIf any prerequisite is missing, the verdict is\n`PREREQUISITES_MISSING` with a specific gap citation in the\nchecklist (marked `[✗]`), and `READY_TO_DEPLOY` MUST NOT also\nappear.\n\n## Quick navigation\n\n| Section | When to read |\n|---|---|\n| Prerequisites | Always — verify before provisioning |\n| Step 1 — Fleet type (maintain vs request) | Fleet lifecycle decision |\n| Step 2 — Launch template configuration | AMI, instance type, network |\n| Step 3 — Allocation strategy | Cost vs capacity trade-off |\n| Step 4 — Instance pools and diversification | Interruption resilience |\n| Step 5 — Target capacity (units vs vCPUs) | Sizing |\n| Step 6 — Replacement strategies | Interruption handling |\n| Step 7 — Capacity rebalance | Proactive rebalancing |\n| Step 8 — Spot placement score | Capacity-aware launch |\n| Step 9 — Capacity reservations integration | Guaranteed capacity |\n| Step 10 — Recent features | Latest |\n| NEVER do these things | Review before signing off |\n| Output format | The literal checklist template |\n| references\u002Fallocation-strategies.md | Strategy deep dive |\n| references\u002Fprovisioning-cli-commands.md | Copy-pasteable CLI sequence |\n\n## Mindset\nFull mindset and the 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: allocation strategy selection\nWorkload-profile decision framework and key implications moved to\n[references\u002Fallocation-strategies.md](references\u002Fallocation-strategies.md).\n\n## Expert heuristic: capacity rebalance and replacement\nRebalance-vs-default-replacement comparison, lifecycle, and enabling JSON 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.\nIf any are missing, the verdict is **PREREQUISITES_MISSING** with a\nspecific gap citation.\n\n| Prerequisite | Why it matters | How to verify |\n|---|---|---|\n| AWS account with EC2 Spot Fleet access | Cannot provision without it | `aws sts get-caller-identity` |\n| Region selected | Instance types and AZ availability vary by region | `aws configure get region` |\n| IAM service role for Spot Fleet | Spot Fleet needs `AWSServiceRoleForEC2SpotFleet` to launch instances | `aws iam get-role --role-name AWSServiceRoleForEC2SpotFleet` |\n| Launch template exists (or create one) | Fleet needs a standardized instance configuration | `aws ec2 describe-launch-templates` |\n| AMI valid in the region | AMIs are region-scoped; cross-region AMI IDs are invalid | `aws ec2 describe-images --image-ids \u003Cami-id>` |\n| Instance types available in the region | Not all instance types are available in all regions\u002FAZs | `aws ec2 describe-instance-types --instance-types \u003Ctype>` |\n| At least 2-3 instance types specified | Single-type fleets have no diversification fallback | List in the Overrides |\n| At least 2 AZs specified | Single-AZ fleets lose all capacity on AZ failure | List AZs in Overrides |\n| Target capacity identified | Determines fleet size; `maintain` fleets auto-adjust | Positive integer |\n| Spot placement score (optional) | Pre-check capacity availability before creating fleet | `aws ec2 get-spot-placement-scores` |\n\nIf any prerequisite is missing, output `VERDICT: PREREQUISITES_MISSING`\nand cite the specific gap.\n\n## Step 1 — Fleet type (maintain vs request)\n\nThe first decision is whether the fleet should continuously maintain\nits target capacity or fill it once and stop.\n\n**Decision tree:**\n```text\nDoes the workload need continuous capacity (long-running, stateless)?\n├── YES → Fleet type: maintain\n│         AWS continuously monitors and replaces interrupted instances.\n│         Target capacity can be modified (scale up\u002Fdown).\n│         Capacity rebalance can be enabled.\n│         Use for: web servers, batch processing, CI\u002FCD workers\n└── NO  → Is this a one-time burst (job queue, HPC, data processing)?\n    ├── YES → Fleet type: request\n    │         Fleet fills once and stops. No replacement.\n    │         Target capacity CANNOT be modified after creation.\n    │         Capacity rebalance is silently ignored.\n    │         Use for: one-time HPC jobs, data migration, burst compute\n    └── NO  → Fleet type: maintain (the safe default)\n```\n\n**Feature comparison:**\n\n| Feature | maintain | request |\n|---|---|---|\n| Replacement on interruption | Yes (automatic) | No |\n| Target capacity modification | Yes (live) | No (immutable) |\n| Capacity rebalance | Supported | Not supported (ignored) |\n| Excess capacity termination | Configurable | N\u002FA |\n| Expiry | Until cancelled | Fills once, then done |\n| Best for | Long-running workloads | One-time burst jobs |\n\n**Common mistake:** using `request` for a web tier and expecting\nAWS to replace interrupted instances. It will not — the fleet fills\nonce and stops. Use `maintain`.\n\n## Step 2 — Launch template configuration\n\nA launch template defines the instance configuration: AMI, instance\ntype, key pair, security groups, IAM instance profile, user data,\nand storage. The Spot Fleet references the launch template and\noverrides instance type and AZ via the Overrides array.\n\n**Create a launch template:**\n```bash\naws ec2 create-launch-template \\\n  --launch-template-name spot-fleet-web-server \\\n  --launch-template-data '{\n    \"ImageId\": \"ami-0abcdef1234567890\",\n    \"InstanceType\": \"m5.large\",\n    \"KeyName\": \"my-key-pair\",\n    \"SecurityGroupIds\": [\"sg-0abc123\"],\n    \"IamInstanceProfile\": { \"Arn\": \"arn:aws:iam::123456789012:instance-profile\u002Fspot-fleet-role\" },\n    \"UserData\": \"'$(base64 user-data.sh)'\",\n    \"BlockDeviceMappings\": [{\n      \"DeviceName\": \"\u002Fdev\u002Fxvda\",\n      \"Ebs\": { \"VolumeSize\": 30, \"VolumeType\": \"gp3\", \"DeleteOnTermination\": true }\n    }],\n    \"TagSpecifications\": [{\n      \"ResourceType\": \"instance\",\n      \"Tags\": [\n        { \"Key\": \"Name\", \"Value\": \"spot-fleet-web\" },\n        { \"Key\": \"Environment\", \"Value\": \"production\" }\n      ]\n    }]\n  }'\n```\n\n**Key rules:**\n- The instance type in the launch template is the DEFAULT; the\n  Spot Fleet Overrides override it per pool.\n- The AMI must be valid in the fleet's region.\n- EBS volumes should be `DeleteOnTermination: true` for Spot\n  (otherwise orphaned volumes accumulate cost).\n- Tag the instances at launch (launch-template tags are more\n  reliable than Spot Fleet-level tags).\n\n## Step 3 — Allocation strategy\n\nSee the \"Expert heuristic: allocation strategy selection\" section\nabove for the decision framework. Summary:\n\n| Strategy | Picks pools based on | Diversification | Interruption risk | Cost |\n|---|---|---|---|---|\n| `priceCapacityOptimized` | Price + capacity availability (RECOMMENDED) | Implicit (multi-pool) | Low-Medium | Low |\n| `capacityOptimized` | Capacity availability (max free capacity) | Implicit (multi-pool) | Lowest | Medium |\n| `lowestPrice` | Lowest price per AZ | None (concentrates) | Highest | Lowest |\n| `diversized` | Even spread across all pools | Explicit (equal) | Low | Medium |\n\n**Setting the allocation strategy:**\n```json\n{\n  \"AllocationStrategy\": \"priceCapacityOptimized\",\n  \"TargetCapacitySpecification\": {\n    \"TotalTargetCapacity\": 10,\n    \"DefaultTargetCapacityType\": \"spot\"\n  }\n}\n```\n\n**Common mistake:** using `lowestPrice` with a single instance type.\nThe fleet concentrates in one pool and is interrupted all at once.\nAlways use `priceCapacityOptimized` or `capacityOptimized` unless you\nhave a specific cost-optimization requirement with many (10+) instance\ntypes.\n\n## Step 4 — Instance pools and diversification\n\nInstance pools are unique combinations of instance type + AZ. The\nSpot Fleet draws from these pools based on the allocation strategy.\nMore pools = better diversification = lower interruption risk.\n\n**Overrides specify the pools (9 pools = 3 types x 3 AZs):**\n```json\n\"LaunchTemplateConfigs\": [{\n  \"LaunchTemplateSpecification\": { \"LaunchTemplateId\": \"lt-0abc123\", \"Version\": \"1\" },\n  \"Overrides\": [\n    { \"InstanceType\": \"m5.large\",  \"AvailabilityZone\": \"us-east-1a\" },\n    { \"InstanceType\": \"m5.large\",  \"AvailabilityZone\": \"us-east-1b\" },\n    { \"InstanceType\": \"m5.large\",  \"AvailabilityZone\": \"us-east-1c\" },\n    { \"InstanceType\": \"m5a.large\", \"AvailabilityZone\": \"us-east-1a\" },\n    { \"InstanceType\": \"c5.large\",  \"AvailabilityZone\": \"us-east-1b\" },\n    { \"InstanceType\": \"c5.large\",  \"AvailabilityZone\": \"us-east-1c\" }\n  ]\n}]\n```\n\n**Diversification best practices:**\n- Specify at least 2-3 instance types (e.g., m5, m5a, c5).\n- Specify at least 3 AZs (all AZs in the region).\n- This gives 9+ pools, dramatically reducing interruption risk.\n- Use instance type families with similar vCPU\u002Fmemory ratios so\n  your workload scales predictably.\n- Consider using `InstanceRequirements` (attribute-based) instead of\n  specific types for flexible selection.\n\n**Attribute-based instance selection (InstanceRequirements):**\n```json\n\"Overrides\": [\n  {\n    \"InstanceRequirements\": {\n      \"VCpuCount\": { \"Min\": 2, \"Max\": 4 },\n      \"MemoryMiB\": { \"Min\": 8192 },\n      \"AcceleratorCount\": { \"Max\": 0 },\n      \"BurstablePerformance\": \"excluded\"\n    },\n    \"AvailabilityZone\": \"us-east-1a\"\n  }\n]\n```\n\nThis lets AWS pick any instance type matching the requirements,\nmaximizing pool count.\n\n## Step 5 — Target capacity (units vs vCPUs vs instances)\n\nTarget capacity can be measured in three ways:\n\n| Unit type | How it works | When to use |\n|---|---|---|\n| `units` | Weighted: each override has a `WeightedCapacity` value | Mixed-size fleets (some instances count as 2 units, others as 1) |\n| `vcpu` | Each instance counts as its vCPU count | vCPU-based capacity planning |\n| `instances` (default) | Each instance counts as 1 | Simple equal-weight fleets |\n\n```json\n\"TargetCapacitySpecification\": {\n  \"TotalTargetCapacity\": 20,\n  \"DefaultTargetCapacityType\": \"spot\",\n  \"TargetCapacityUnitType\": \"vcpu\"\n}\n```\n\n**Common mistake:** using `instances` with mixed instance types\nwhere some are 2x the size of others. The fleet thinks it needs 20\ninstances, but if it picks large instances, you have way more\ncapacity than intended. Use `vcpu` or `units` for mixed fleets.\n\n## Step 6 — Replacement strategies (InstanceInterruptionBehavior)\n\nWhen a Spot Instance is interrupted, the fleet's behavior depends\non `InstanceInterruptionBehavior`:\n\n| Behavior | What happens to the interrupted instance | When to use |\n|---|---|---|\n| `terminate` (default) | Instance is terminated (EBS volumes deleted if DeleteOnTermination) | Stateless workloads |\n| `stop` | Instance is stopped (can be restarted later) | Stateful workloads that can resume |\n| `hibernate` | Instance is hibernated (RAM saved to disk) | Long-running jobs with checkpointing |\n\n```json\n{\n  \"InstanceInterruptionBehavior\": \"terminate\",\n  \"SpotMaintenanceStrategies\": {\n    \"CapacityRebalance\": {\n      \"ReplacementStrategy\": \"launch\"\n    }\n  }\n}\n```\n\n**Key rule:** `InstanceInterruptionBehavior` is set at the Spot\nFleet request level and applies to ALL instances in the fleet. It\ncannot be overridden per-instance after launch.\n\n## Step 7 — Capacity rebalance\n\nSee the \"Expert heuristic: capacity rebalance and replacement\"\nsection above for the full lifecycle. Summary configuration:\n\n```json\n\"SpotMaintenanceStrategies\": {\n  \"CapacityRebalance\": {\n    \"ReplacementStrategy\": \"launch\"\n  }\n}\n```\n\n**Replacement strategies:**\n- `launch` (default): Fleet launches a new replacement instance\n  BEFORE terminating the old one. This is the recommended strategy.\n- `terminate`: Fleet terminates the old instance immediately and\n  then launches a replacement. Higher risk of capacity gap.\n\n**Requirements:**\n- Fleet type MUST be `maintain`.\n- Fleet MUST have `InstanceInterruptionBehavior` set to `terminate`\n  or `stop`.\n- The replacement instance is launched from the same launch\n  template + overrides.\n\n**Common mistake:** enabling capacity rebalance on a `request` fleet.\nIt is silently ignored. Only `maintain` fleets support rebalancing.\n\n## Step 8 — Spot placement score\n\nSpot placement score is a pre-flight capacity check. Before creating\na fleet, query the score to see which instance type + AZ\ncombinations have the best capacity availability.\n\nQuery command and sample output moved to [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md).\n\n**Score interpretation:**\n- Score 1-3: Low availability. High interruption risk. Avoid.\n- Score 4-7: Medium availability. Acceptable for fault-tolerant.\n- Score 8-10: High availability. Low interruption risk. Prefer.\n\n**Key implication:** Spot placement score is ADVISORY ONLY. It does\nnot reserve capacity. The fleet may still be interrupted in a\nhigh-scoring pool if overall Spot demand spikes.\n\n**When to use:** Before creating large fleets (>100 instances),\nwhen choosing between instance types, or before scaling up.\n\n## Step 9 — Capacity reservations integration\n\nOn-Demand Capacity Reservations (ODCR) can be used alongside Spot\nFleets. When the fleet launches in an AZ+instance-type combination\nthat has an open ODCR, the ODCR is consumed first (guaranteed\ncapacity, On-Demand billing), then Spot fills the rest.\n\n**Configuration for ODCR preference:**\n```json\n{\n  \"LaunchTemplateConfigs\": [{\n    \"LaunchTemplateSpecification\": { \"LaunchTemplateId\": \"lt-0abc123\", \"Version\": \"1\" },\n    \"Overrides\": [{\n      \"InstanceType\": \"m5.large\",\n      \"AvailabilityZone\": \"us-east-1a\"\n    }]\n  }],\n  \"TargetCapacitySpecification\": {\n    \"TotalTargetCapacity\": 10,\n    \"OnDemandTargetCapacity\": 3,\n    \"DefaultTargetCapacityType\": \"spot\"\n  },\n  \"OnDemandOptions\": {\n    \"CapacityReservationOptions\": {\n      \"UsageStrategy\": \"use-capacity-reservations-first\"\n    }\n  }\n}\n```\n\n**Key rules:**\n- ODCR must match instance type + AZ + platform exactly.\n- `OnDemandTargetCapacity` specifies how many units to run as\n  On-Demand (consumed from ODCR if available).\n- The rest of the fleet runs as Spot.\n- This gives a hybrid: guaranteed capacity for critical instances +\n  cost savings for the rest.\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 use `lowestPrice` with a single instance type.** The\n   fleet concentrates in one pool. When that pool is reclaimed, the\n   entire fleet is interrupted simultaneously with no fallback. Use\n   `priceCapacityOptimized` with at least 3 instance types.\n\n2. **NEVER use `request` fleet type for long-running workloads.**\n   A `request` fleet fills once and stops. It does NOT replace\n   interrupted instances. Use `maintain` for any workload that\n   needs continuous capacity.\n\n3. **NEVER specify only one instance type or one AZ.** Single-type\n   or single-AZ fleets have no diversification. Always specify 2-3+\n   instance types across 3+ AZs for interruption resilience.\n\n4. **NEVER enable capacity rebalance on a `request` fleet.** It is\n   silently ignored. Capacity rebalance only works with `maintain`\n   fleet type. Verify fleet type before configuring rebalance.\n\n5. **NEVER treat Spot placement score as a capacity guarantee.** It\n   is advisory only. A score of 10 does not reserve capacity. Use\n   it to avoid low-scoring pools, not as a reservation.\n\n## Output format\n\n```text\nSPOT_FLEET: \u003Cfleet-id> (allocation strategy: \u003Cstrategy>)\nVERDICT: READY_TO_DEPLOY | PREREQUISITES_MISSING\nCHECKLIST:\n  [✓|✗] Fleet type: maintain | request\n  [✓|✗] Allocation strategy: priceCapacityOptimized | capacityOptimized | lowestPrice | diversified\n  [✓|✗] Launch template: \u003Clt-id> (version \u003Cn>)\n  [✓|✗] Instance types: \u003Ctype-1>, \u003Ctype-2>, \u003Ctype-3> (in \u003Cn> AZs = \u003Cpool-count> pools)\n  [✓|✗] Target capacity: \u003Cn> \u003Cunit-type> (spot: \u003Cn>, on-demand: \u003Cn>)\n  [✓|✗] InstanceInterruptionBehavior: terminate | stop | hibernate\n  [✓|✗] Capacity rebalance: enabled (launch strategy) | disabled\n  [✓|✗] Spot placement score: checked (top pool score: \u003Cscore>) | not checked\n  [✓|✗] Capacity reservations (ODCR): used-first (\u003Cn> On-Demand units) | not used\n  [✓|✗] IAM service role: AWSServiceRoleForEC2SpotFleet\n  [✓|✗] Tags: \u003Ckey=value list>\nVERIFICATION_COMMANDS:\n  aws ec2 describe-spot-fleet-requests --spot-fleet-request-ids \u003Cfleet-id>\n  aws ec2 describe-spot-fleet-instances --spot-fleet-request-id \u003Cfleet-id>\n  aws ec2 describe-spot-fleet-request-history --spot-fleet-request-id \u003Cfleet-id>\n```\n\n### Worked example — maintain fleet with priceCapacityOptimized and rebalance\n\n```text\nSPOT_FLEET: sfr-1234567890abcdef0 (allocation strategy: priceCapacityOptimized)\nVERDICT: READY_TO_DEPLOY\nCHECKLIST:\n  [✓] Fleet type: maintain\n  [✓] Allocation strategy: priceCapacityOptimized\n  [✓] Launch template: lt-0abc123def456 (version 1)\n  [✓] Instance types: m5.large, m5a.large, c5.large (in 3 AZs = 9 pools)\n  [✓] Target capacity: 20 vcpu (spot: 20, on-demand: 0)\n  [✓] InstanceInterruptionBehavior: terminate\n  [✓] Capacity rebalance: enabled (launch strategy)\n  [✓] Spot placement score: checked (top pool score: 10)\n  [✓] Capacity reservations (ODCR): not used\n  [✓] IAM service role: AWSServiceRoleForEC2SpotFleet\n  [✓] Tags: Environment=production, Service=batch-processing\nVERIFICATION_COMMANDS:\n  aws ec2 describe-spot-fleet-requests --spot-fleet-request-ids sfr-1234567890abcdef0\n  aws ec2 describe-spot-fleet-instances --spot-fleet-request-id sfr-1234567890abcdef0\n  aws ec2 describe-spot-fleet-request-history --spot-fleet-request-id sfr-1234567890abcdef0\n```\n\n## Error handling\nFleet failure 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, capacity rebalance deep dive, recent AWS features (moved from this file)\n- [references\u002Fallocation-strategies.md](references\u002Fallocation-strategies.md) — allocation-strategy workload-profile heuristic (moved from this file) plus the strategy comparison matrix and decision framework\n- [references\u002Fprovisioning-cli-commands.md](references\u002Fprovisioning-cli-commands.md) — full copy-pasteable provisioning CLI sequence\n- [references\u002Fdiagnostic-commands.md](references\u002Fdiagnostic-commands.md) — Spot placement score query and sample output (moved from this file)\n- [references\u002Ferror-handling.md](references\u002Ferror-handling.md) — fleet stuck\u002Fpartially filled, rebalance not working, MaxSpotInstanceCountExceeded, immutable allocation strategy (moved from this file)\n\n## Domain\n\nAWS CloudOps \u002F EC2 Spot Fleet Provisioning & Cost-Optimized Compute\nCapacity Management.\n\n## AWS documentation\n\n- **Spot Fleet User Guide** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-fleet.html\n- **Allocation strategies** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-fleet-allocation-strategy.html\n- **Capacity rebalance** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fcapacity-rebalance.html\n- **Spot placement score** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-placement-score.html\n- **Spot Fleet request options** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-request-options.html\n- **Instance interruption behavior** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-interruptions.html\n- **On-Demand Capacity Reservations** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fec2-capacity-reservations.html\n- **Attribute-based instance selection** — https:\u002F\u002Fdocs.aws.amazon.com\u002FAWSEC2\u002Flatest\u002FUserGuide\u002Fspot-instance-request-types.html#attribute-based-instance-type-selection\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, ec2, spot-fleet, cloudops, deploy, compute, provisioning, allocation-strategy, capacity-rebalance, launch-template, spot-instances","1","Jacky Chan — AWS Community Builder","aws-cloudops","Compute","0.1.0","aws, ec2, spot fleet, spot instances, cloudops, deploy, provisioning, allocation strategy, lowestPrice, capacityOptimized, diversified, priceCapacityOptimized, instance pools, target capacity, capacity rebalance, spot placement score, capacity reservations, launch template, fleet type, maintain","deploy","high","false","capability","Invoke when the user wants to create an EC2 Spot Fleet request (maintain or one-time request), select an allocation strategy (lowestPrice, capacityOptimized, diversified, priceCapacityOptimized), configure instance pool diversification, enable capacity rebalance and replacement, use Spot placement score for capacity awareness, or integrate Spot Fleets with capacity reservations. Do NOT invoke for single Spot Instance requests (use RunInstances with InstanceMarketOptions), for On-Demand Capacity Reservations standalone (use capacity-reservation operators), for EC2 Auto Scaling Groups with mixed instances (use autoscaling-policy-deployer), or for auditing existing Spot Fleet configurations (use autoscaling-group-auditor).","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 ec2, iam, and service-roles access. Works with Terraform aws_spot_fleet_request resources and CloudFormation AWS::EC2::SpotFleet templates.","main","eeace51bd5dd1db2030729d83eeab988861553aa","skills\u002Fec2-spot-fleet-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 ec2-spot-fleet-deployer",{"tool":56,"command":57},"bunx","bunx skills add jhkchan\u002Faws-agent-skills --skill ec2-spot-fleet-deployer",{"tool":59,"command":60},"pnpm","pnpm dlx skills add jhkchan\u002Faws-agent-skills --skill ec2-spot-fleet-deployer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-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","参考文档",5937,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Feval\u002Ftest-cases.yaml",{"path":71,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fbaselines\u002Fcapacity-rebalance-enabled.md",795,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fbaselines\u002Fcapacity-rebalance-enabled.md",{"path":75,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":76,"sourceHtmlUrl":77},"evals\u002Fbaselines\u002Fmaintain-price-capacity-optimized.md",890,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fbaselines\u002Fmaintain-price-capacity-optimized.md",{"path":79,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":80,"sourceHtmlUrl":81},"evals\u002Fbaselines\u002Fmissing-iam-role.md",763,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fbaselines\u002Fmissing-iam-role.md",{"path":83,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":84,"sourceHtmlUrl":85},"evals\u002Fbaselines\u002Frequest-lowest-price-burst.md",817,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fbaselines\u002Frequest-lowest-price-burst.md",{"path":87,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":88,"sourceHtmlUrl":89},"evals\u002Fbaselines\u002Fspot-placement-score.md",843,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fbaselines\u002Fspot-placement-score.md",{"path":91,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":92,"sourceHtmlUrl":93},"evals\u002Feval_config.yaml",1778,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Feval_config.yaml",{"path":95,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":96,"sourceHtmlUrl":97},"evals\u002Fevals.json",11389,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fevals.json",{"path":99,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":100,"sourceHtmlUrl":101},"evals\u002Fprompts\u002Fcapacity-rebalance-enabled.md",655,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fprompts\u002Fcapacity-rebalance-enabled.md",{"path":103,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":104,"sourceHtmlUrl":105},"evals\u002Fprompts\u002Fmaintain-price-capacity-optimized.md",689,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fprompts\u002Fmaintain-price-capacity-optimized.md",{"path":107,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":108,"sourceHtmlUrl":109},"evals\u002Fprompts\u002Fmissing-iam-role.md",444,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fprompts\u002Fmissing-iam-role.md",{"path":111,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":112,"sourceHtmlUrl":113},"evals\u002Fprompts\u002Frequest-lowest-price-burst.md",593,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fprompts\u002Frequest-lowest-price-burst.md",{"path":115,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":116,"sourceHtmlUrl":117},"evals\u002Fprompts\u002Fspot-placement-score.md",657,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fevals\u002Fprompts\u002Fspot-placement-score.md",{"path":119,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":120,"sourceHtmlUrl":121},"examples\u002FREADME.md",6094,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Fexamples\u002FREADME.md",{"path":123,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":124,"sourceHtmlUrl":125},"references\u002Fadvanced-patterns.md",7813,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Freferences\u002Fadvanced-patterns.md",{"path":127,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":128,"sourceHtmlUrl":129},"references\u002Fallocation-strategies.md",7002,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Freferences\u002Fallocation-strategies.md",{"path":131,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":132,"sourceHtmlUrl":133},"references\u002Fdiagnostic-commands.md",791,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Freferences\u002Fdiagnostic-commands.md",{"path":135,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":136,"sourceHtmlUrl":137},"references\u002Ferror-handling.md",1172,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Freferences\u002Ferror-handling.md",{"path":139,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":140,"sourceHtmlUrl":141},"references\u002Fprovisioning-cli-commands.md",8841,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-deployer\u002Freferences\u002Fprovisioning-cli-commands.md",{"path":143,"resourceType":66,"resourceTypeDesc":67,"sizeBytes":144,"sourceHtmlUrl":145},"skill.usf.yaml",4265,"https:\u002F\u002Fgithub.com\u002Fjhkchan\u002Faws-agent-skills\u002Fblob\u002Fmain\u002Fskills\u002Fec2-spot-fleet-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",[],[]]