storage-fsx-windows-sla-optimizer

Files (17)

• .skilleval.yaml
• CHANGELOG.md
• README.md
• SKILL.md
• eval_queries.json · evals/
• evals.json · evals/
• fsx-context.json · evals/files/
• misconfigured-ad-credentials.json · evals/files/
• trend-idle.json · evals/files/
• trend-storage-filler.json · evals/files/
• trend-weekday-peaker.json · evals/files/
• data-collection.md · references/
• finding-logic.md · references/
• fleet-orchestration.md · references/
• fsx-windows-sla-best-practices.md · references/
• report-format.md · references/
• trend-analysis.md · references/

SKILL.md (first lines)

# FSx for Windows SLA Optimizer

Perform a structured, read-only SLA-readiness and availability review of Amazon FSx
for Windows File Server file systems, and surface cost-optimization opportunities
where capacity is over-provisioned. Automatically handles single-file-system and
multi-file-system (fleet) reviews based on how many file systems are provided.

The availability SLA for FSx for Windows is only actually achievable when the file
system is configured correctly: Multi-AZ for automatic failover, healthy Active
Directory connectivity, enough throughput and storage headroom, working backups, a
sensible maintenance window, and alarms to detect problems before they become
outages. This skill checks those factors and rates each file system's readiness.

## When to Use

Activate this skill when the user asks to:
- Review, audit, assess, or optimize an FSx for Windows file system's SLA,
  availability, uptime, failover readiness, or resiliency
- Determine whether a file system is Single-AZ or Multi-AZ, or whether it should be
- Understand why a file system is in a **Misconfigured** state
- Check whether throughput capacity or storage capacity is under-provisioned (SLA
  risk) or over-provisioned (cost waste / right-sizing)
- Verify backups, maintenance window, and CloudWatch alarm coverage
- Review a list of file systems ("review these file systems: fs-a, fs-b")

Do NOT activate for FSx for NetApp ONTAP / Lustre / OpenZFS, EFS, S3, EBS, the AWS
Backup service, FSx data migration, or SMB share-permission troubleshooting.

## Architecture

- **This skill (orchestrator/analyzer):** input parsing, routing, finding-logic
  application, report rendering.
- **Data collection:** `references/data-collection.md` — the read-only
  control-plane API calls used to gather file-system configuration plus daily trend
  and 5-minute peak metric series. Data is acquired with the agent's native
  `use_aws` tool under the assumed role in the target account. No credentials or
  profile are requested from the user.
- **Trend analysis:** `references/trend-analysis.md` — the usage-pattern method
  (daily trends, approximate 5-minute interval peaks, weekday/weekend profile,
  storage growth projection, and idle detection) that enriches the throughput and
  storage dimensions. Default lookback 30 days.
- **Finding logic:** `references/finding-logic.md` — all severity rules and body
  templates for the seven dimensions and the cost-optimization notes.
- **Report format:** `references/report-format.md` — report structure, SLA
  Readiness rating criteria, dimensions table, pre-render validation.
- **Fleet orchestration:** `references/fleet-orchestration.md` — batching, caching,
  manifest, summary matrix (loaded only for multi-file-system reviews).
- **Operational depth:** `references/fsx-windows-sla-best-practices.md` — reasoning
  behind thresholds, the Multi-AZ availability model, the Active Directory
  dependency, the throughput sizing formula, and the cost-vs-SLA tradeoff.

## Input Parsing & Validation

### Accepted input formats

- Single file-system ID: `fs-0123456789abcdef0`
- Comma-separated: `fs-aaa..., fs-bbb..., fs-ccc...`
- Newline-separated (pasted list)
- File reference: "review the file systems in fsids.txt" (read file, one ID per line)
- ARN wrappers (stripped automatically per rules below)
- No IDs given (e.g. "review all my FSx Windows file systems in us-east-1") →
  discover via `fsx.describeFileSystems` in the stated region(s) and review all
  file systems whose `FileSystemType` is `WINDOWS`

### Wrapper recognition

Strip the file-system ID from these patterns before collecting data:
- `arn:aws:fsx:<region>:<account>:file-system/fs-...` (and `aws-cn` / `aws-us-gov`
  partitions) — take the `fs-...` segment after `file-system/`
- Bare `fs-...` ID — use as-is

When a wrapper is extracted, surface it: "Reviewing file system `fs-0123...`
(extracted from `arn:aws:fsx:...`)."

### Reject (abort without API call)

- Empty string or whitespace only → "No file-system ID was provided."
- An ID that does not match `^fs-[0-9a-f]{8,}$` and is not a recognized wrapper →
  "`<input>` does not look like an FSx file-system ID (expected `fs-...`)."

### Region

If the user names a region, use it. If IDs are given without a region, ask once for
the region (FSx IDs are region-scoped and there is no cross-region lookup). Never
guess the region.

### Metric lookback

Default to a **30-day** lookback for the trend analysis (a clean week-over-week
trend and enough to distinguish a step-change from normal weekly variation). Honor an
explicit override if the user asks (14 / 21 / 30 / 60 days). Never block to ask for
it; default silently and print the window in the report header. See
`references/trend-analysis.md`.

## Routing

After parsing, route based on file-system count. **The user never chooses. Routing
is automatic and silent.**

| Count | Path | Behavior |
|---|---|---|
| 1 | Single-FS | Full report with all details |
| 2-10 | Fleet (single pass) | Summary matrix + full details for all |
| 11-20 | Fleet (single pass) | Summary matrix + details for Low-rated only |
| 21+ | Fleet (batched) | Batches of 10, manifest tracking, resume support |

## Single-File-System Path

### Execution flow

1. Collect raw configuration and metric series per `references/data-collection.md`.
2. If the file system is not found or the role has no access → abort: "File system
   `<id>` does not exist in `<region>` or the role does not have access."
3. Confirm `FileSystemType` is `WINDOWS`. If it is `ONTAP`, `LUSTRE`, or `OPENZFS`
   → abort: "`<id>` is an FSx for `<type>` file system; this skill reviews FSx for
   Windows only."
4. Evaluate API pre-flight statuses.
   - If any `AccessDenied` → present permissions audit (see Pre-flight section)
   - If any `ToolingFailure` → present tooling notice (see Pre-flight section)

From aws/tools-for-devops-agent, Apache-2.0.

More from aws/tools-for-devops-agent