aws-storage

• SKILL.mdcore · 23,076 bytes
• SKILL.mdcore · 23,076 bytes
• references/data-movement-and-protection-knowledge.mddoc · 6,375 bytes
• references/ebs-knowledge.mddoc · 6,271 bytes
• references/efs-knowledge.mddoc · 4,558 bytes
• references/fsx-lustre-knowledge.mddoc · 6,521 bytes
• references/fsx-ontap-knowledge.mddoc · 7,276 bytes
• references/fsx-openzfs-knowledge.mddoc · 5,723 bytes
• references/fsx-windows-knowledge.mddoc · 5,650 bytes
• references/s3-express-knowledge.mddoc · 5,827 bytes
• references/s3-files-knowledge.mddoc · 5,792 bytes
• references/s3-general-purpose-knowledge.mddoc · 7,345 bytes
• references/s3-tables-knowledge.mddoc · 7,325 bytes
• references/s3-vectors-knowledge.mddoc · 5,734 bytes

## Overview

This skill provides domain expertise for choosing among AWS storage services, selecting storage classes, optimizing cost, and routing to resources for operating storage services. It covers object storage (S3 General Purpose buckets and their storage classes, S3 Express One Zone on directory buckets, S3 Tables, S3 Vectors), file storage (Amazon EFS, S3 Files, FSx for Lustre, FSx for NetApp ONTAP, FSx for OpenZFS, and FSx for Windows File Server), block storage (EBS volume types and EC2 instance store), and the data-movement and protection services that connect them (DataSync, Storage Gateway, Transfer Family, and AWS Backup). It does not advise on databases or analytics query engines. It works with or without the AWS MCP server; when available, the [AWS MCP server](https://docs.aws.amazon.com/agent-toolkit/) is recommended for verifying current specifications and pricing, and all guidance also works with the standard AWS CLI. For deep single-service tasks, route to the specialized skills listed in the Routing section below.

## How to Handle User Queries

When this skill is triggered, classify the user's request and follow the appropriate path.

### Rules

These apply to all responses regardless of path:

1. You MUST verify current numbers. When the AWS MCP server is available, use search_documentation and read_documentation to cross-check before citing specifics. When quoting costs, you MUST include a link to the relevant pricing page. When quoting performance metrics, you MUST include a link to the relevant product page. Otherwise, verify against linked AWS documentation pages or use the AWS CLI to confirm current values. Where a reference file directs you to documentation for a current value, you MUST retrieve that value from the linked page before answering. Do not substitute a remembered figure, and do not offer an approximation or a range in place of a retrieved value. If retrieval is not possible in the current environment, name the value you could not verify rather than citing one from memory.
2. You MUST retrieve the relevant service reference file from the Routing section below before answering questions about that service. AWS storage specifications, limits, and service capabilities change frequently. You MUST NOT answer from memory alone. You MUST surface relevant troubleshooting guidance and 'gotchas' from reference files in your response. Justify recommendations by workload fit, not by mentioning that a reference file 'explicitly' mentions a workload for a given service.
3. You MUST include cost implications when recommending services or approaches. Do not wait for the user to ask. Do not compare services on storage charges alone; per-object fees such as metadata charges can materially change TCO. For deep cost analysis, monitoring, or optimization beyond storage selection, route to the [`billing-and-cost-management`](https://github.com/aws/agent-toolkit-for-aws/tree/e2588f4b494416e68c5a991e51b21c2d99038de3/skills/core-skills/aws-billing-and-cost-management) skill.