troubleshooting-s3-files — Skills

What it does

You MUST verify aws CLI is available with s3files subcommand support

You MUST confirm valid AWS credentials

You MUST ONLY check for tool existence and version — MUST NOT execute destructive or mutating commands during verification

You MUST inform the user if any required tools are missing

You MUST respect the user's decision to abort if tools are unavailable

You SHOULD explain steps before executing and wait for user confirmation on write commands

Mount target SG MUST have inbound TCP 2049 from compute SG

Requirements & configuration

Mount hangs in isolated VPC: If the VPC has no internet access, S3 Files requires a CloudWatch Logs VPC endpoint (com.amazonaws.REGION.logs) for mount to complete.

Mount access denied: Compute role needs s3files:ClientMount. For dev/test only, AmazonS3FilesClientFullAccess is acceptable — avoid in production.

Write permission denied: Compute role needs s3files:ClientWrite

Root access denied: Compute role needs s3files:ClientRootAccess. ⚠️ Bypasses POSIX permissions — prefer access points with scoped POSIX users.

Intelligent read routing not working: Compute role needs s3:GetObject on the bucket.

troubleshooting s3 files

Source

Repository: https://github.com/aws/agent-toolkit-for-aws

troubleshooting-s3-files FAQ

What does the troubleshooting-s3-files skill do?

> Diagnoses and resolves Amazon S3 Files issues including mount failures, permission errors, synchronization problems, and performance issues. Use when the user has an S3 file system that is not mounting, returning access denied, not syncing changes to S3, showing files in lost+found, or performing slower than expected. You MUST verify aws CLI is available with s3files subcommand support You MUST confirm valid AWS credentials

What does troubleshooting-s3-files require?

Mount hangs in isolated VPC: If the VPC has no internet access, S3 Files requires a CloudWatch Logs VPC endpoint (com.amazonaws.REGION.logs) for mount to complete. Mount access denied: Compute role needs s3files:ClientMount. For dev/test only, AmazonS3FilesClientFullAccess is acceptable — avoid in production. Write permission denied: Compute role needs s3files:ClientWrite Root access denied: Compute role needs s3files:ClientRootAccess. ⚠️ Bypasses POSIX permissions — prefer access points with scoped POSIX users. Intelligent read routing not working: Compute role needs s3:GetObject on the bucket.

How do I install troubleshooting-s3-files?

Run: npx -y skills add https://github.com/aws/agent-toolkit-for-aws --skill troubleshooting-s3-files --agent claude-code — the source lives at github.com/aws/agent-toolkit-for-aws.

Maintain troubleshooting-s3-files?

Let people know it's listed here — add the badge (live metrics, light/dark aware) or a plain link to your README or docs.

[troubleshooting-s3-files on getagentictools](https://getagentictools.com/skills/aws-agent-toolkit-for-aws-troubleshooting-s3-files?ref=badge)

npx agentictools info skills/aws-agent-toolkit-for-aws-troubleshooting-s3-files

The second line is the CLI lookup for this page — handy in READMEs and docs.