Terminal
Terminal/Skill
Read-only review of FSx for Windows file systems covering Multi-AZ setup, Active Directory, capacity, backups, alarms and over-provisioning.
By Amazon Web Services
Works with
npx skills add aws/tools-for-devops-agent --skill storage-fsx-windows-sla-optimizerPerform 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.
Activate this skill when the user asks to:
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.
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.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.references/finding-logic.md — all severity rules and body
templates for the seven dimensions and the cost-optimization notes.references/report-format.md — report structure, SLA
Readiness rating criteria, dimensions table, pre-render validation.references/fleet-orchestration.md — batching, caching,
manifest, summary matrix (loaded only for multi-file-system reviews).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.fs-0123456789abcdef0fs-aaa..., fs-bbb..., fs-ccc...fsx.describeFileSystems in the stated region(s) and review all
file systems whose FileSystemType is WINDOWSStrip 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/fs-... ID — use as-isWhen a wrapper is extracted, surface it: "Reviewing file system fs-0123...
(extracted from arn:aws:fsx:...)."
^fs-[0-9a-f]{8,}$ and is not a recognized wrapper →
"<input> does not look like an FSx file-system ID (expected fs-...)."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.
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.
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 |
references/data-collection.md.<id> does not exist in <region> or the role does not have access."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."AccessDenied → present permissions audit (see Pre-flight section)ToolingFailure → present tooling notice (see Pre-flight section)references/trend-analysis.md and derive throughput, storage-trend,
usage-profile, and idle fields only from complete observed metric series.InsufficientData; never replace missing values with zero. Continue with the
available dimensions and render affected conclusions as Unable to verify.references/finding-logic.md.references/report-format.md.If any check returned AccessDenied, present:
⚠️ The role is missing read permissions for some checks.
Check Status <check name>AccessDenied The minimum policy required includes the read actions for each check above (see the skill README for the full list).
How would you like to proceed?
- Stop here (recommended). Add the missing permissions and re-run.
- Continue with reduced accuracy. Report will note gaps; rating capped at Medium.
Wait for user response. Do NOT proceed by default.
If any check returned ToolingFailure, present:
⚠️ Tooling infrastructure failure — some checks could not reach the AWS API.
Check Status <check name>ToolingFailure How would you like to proceed?
- Stop here and retry later (recommended).
- Continue with partial data. Report will note gaps; rating capped at Medium.
Wait for user response. Do NOT proceed by default.
Load references/fleet-orchestration.md for full fleet behavior. Summary:
references/trend-analysis.md, derives fields, and validates missing data
for each file system before applying finding logicThe complete FSx for Windows SLA review report is the authoritative output of this skill.
After completing the review (single or fleet):
fsx-windows-sla-review-<file-system-id>-<YYYY-MM-DD>.md for a single file
system, or fsx-windows-sla-fleet-review-<YYYY-MM-DD>.md for a fleet review. If
the runtime does not support persisted artifacts, skip artifact creation and
rely on step 3.references/report-format.md (and
references/fleet-orchestration.md for fleets).references/report-format.md. Never produce a condensed, reframed,
or "focused view" variant tailored to the question wording.references/data-collection.md.AccessDenied, ToolingFailure, or InsufficientData,
use the "Unable to verify" template for the affected dimension — never infer
state and never convert missing metrics to zero.references/finding-logic.md and use the
body templates verbatim. Substitute only placeholder values.FreeStorageCapacity is returned in bytes; convert to the displayed unit.references/data-collection.md — Read-only control-plane API calls, CloudWatch
daily-trend and 5-minute peak metric queries, error classification, and the structured
configuration object.references/trend-analysis.md — Usage-pattern method: daily-trend and 5-minute peak windowing,
peak-vs-average, weekday/weekend profile, storage growth projection, idle
detection, and the derived trend fields.references/finding-logic.md — All finding rules, severity assignments, and body
templates for the 7 SLA dimensions plus cost-optimization notes.references/report-format.md — Report structure, dimensions table, SLA Readiness
rating criteria, pre-render validation, canonical AWS documentation URLs.references/fleet-orchestration.md — Fleet-specific: batching, caching, manifest,
summary matrix rendering. Load only for multi-file-system reviews.references/fsx-windows-sla-best-practices.md — Operational depth: reasoning
behind thresholds, the Multi-AZ availability model, the Active Directory
dependency, the throughput sizing formula, and the cost-vs-SLA tradeoff.