S3

What This Skill Does

The S3 skill for OpenClaw provides a robust framework for interacting with S3-compatible object storage services. It acts as an abstraction layer that handles the complexities of object lifecycle management, bucket policy enforcement, and secure data transmission. Beyond basic CRUD operations, this skill excels at managing complex infrastructure requirements like multipart uploads, versioning, and CORS configurations, ensuring that data operations remain performant and compliant with security best practices.

Installation

You can integrate this skill into your OpenClaw environment by running the following command in your terminal: clawhub install openclaw/skills/skills/ivangdavila/s3

Use Cases

• Automated Data Archival: Configure lifecycle rules to transition old logs or temporary files from standard storage to cheaper Glacier tiers automatically to minimize monthly spend.
• Secure Asset Distribution: Generate time-limited, cryptographically signed URLs for private user content, preventing public exposure while allowing temporary read access.
• Large Scale Data Ingestion: Manage high-throughput multipart uploads for large datasets or video files, ensuring incomplete uploads are cleaned up to prevent hidden storage costs.
• Frontend-to-S3 Pipelines: Configure CORS policies to enable secure, direct file uploads from a web application browser client to a protected bucket without traversing your own backend servers.

Example Prompts

• "List all incomplete multipart uploads in my 'user-uploads' bucket and abort any older than 7 days to save costs."
• "Create a bucket policy for 'assets-bucket' that allows read-only access for a specific IAM role and enforce block-public-access settings."
• "Generate a pre-signed PUT URL for 'profile-images/user-123.png' with a 5-minute expiration and include the necessary Content-Type header."

Tips & Limitations

• Security First: Always treat presigned URLs as sensitive credentials. Use the shortest possible expiration duration suited for your task.
• Performance Tuning: If your bucket experiences high request volume, avoid using sequential timestamped prefixes. Incorporate random hashes to distribute load across S3 partitions.
• Hidden Costs: Remember that lifecycle transitions and incomplete multipart uploads are billed. Always set explicit abort rules to prevent invisible storage growth. Additionally, be aware that S3 is an object store, not a filesystem; deep nesting may look organized but provides no performance benefit.