Watadot Aws S3
ReviewAudited by ClawScan on May 10, 2026.
Overview
This is a straightforward AWS S3 command-reference skill, but its examples can use your active AWS account to create buckets, upload files, and delete S3 objects if run as written.
Use this skill only with an intended AWS account/profile, verify bucket and prefix targets before running commands, dry-run sync operations before using --delete, and apply least-privilege IAM policies.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Running this command as written could delete cloud objects in the target S3 path.
The sync example includes --delete, which can remove destination S3 objects that are not present locally. This is purpose-aligned for S3 sync but potentially destructive if used against the wrong bucket or prefix.
aws s3 sync ./local-dir s3://<bucket-name>/path --delete --exclude "*.tmp"
Use explicit bucket/prefix targets, consider aws s3 sync --dryrun first, remove --delete unless intentional, and enable versioning/backups for important data.
If the wrong AWS profile or overly broad IAM permissions are active, the commands could affect unintended buckets or accounts.
These AWS CLI operations execute using the locally configured AWS credentials/profile and can read or modify AWS account resources. That is expected for this S3 skill, but users should notice the account authority involved.
aws s3api list-buckets --query "Buckets[].{Name:Name,Created:CreationDate}" --output table
aws s3 mb s3://<bucket-name> --region <region>Set an explicit AWS_PROFILE or account context and use least-privilege IAM policies limited to the intended buckets and prefixes.
Future AWS CLI S3 operations may use higher concurrency, which can affect bandwidth, throttling, or costs.
This changes a default AWS CLI S3 setting that can affect later S3 transfers beyond the immediate task. The behavior is visible and performance-related, but persistent.
aws configure set default.s3.max_concurrent_requests 20
Prefer profile-specific configuration when possible and document or revert the setting if it was only needed temporarily.