s3-artifact-stage-verify

Upload artifacts to S3 and verify object metadata with durable evidence.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/amitkarpe/agent-skills --skill s3-artifact-stage-verify-amitkarpe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: s3-artifact-stage-verify
Source: https://github.com/amitkarpe/agent-skills/tree/main/skills/s3-artifact-stage-verify
Command: npx skills add https://github.com/amitkarpe/agent-skills --skill s3-artifact-stage-verify-amitkarpe

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Delivering private artifacts like image tarballs or bootstrap assets through S3 often ends with unverified uploads and lost fetch paths, forcing hosts to guess whether an object is ready. This Skill stages the artifact, confirms the exact bucket, key, size, and last-modified metadata, and saves durable evidence of the delivery. ## Core Features & Use Cases - Stage-and-verify workflow: Uploads an artifact to a deterministic S3 key, then confirms it with aws s3 ls and aws s3api head-object instead of trusting the upload command. - Durable evidence capture: Saves the final S3 URI, head-object JSON, summary, logs, and a ready-to-run host-side fetch script under a timestamped output directory. - Use Case: You build a Docker image tarball locally and need it on an EC2 host. Run the script to upload it to a private bucket, verify the object metadata, and hand the host the generated fetch-example.sh to pull it down before docker load. ## Quick Start Run the stage-and-verify script with your local artifact path, target S3 URI, and an output directory to upload the file, verify its metadata, and save the host fetch command as evidence.

Frequently Asked Questions about s3-artifact-stage-verify

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upload a file to S3 and verify it succeeded?▼

Upload the file with aws s3 cp, then confirm it with aws s3 ls and aws s3api head-object to check the bucket, key, size, and last-modified timestamp. The stage-and-verify script automates this sequence and saves the results as evidence files.

How to generate an S3 fetch command for an EC2 host?▼

After verifying the upload, the script writes a fetch-example.sh containing the exact aws s3 cp command with the final S3 URI and any profile or region flags. Copy that script to the host to download the artifact before running docker load or bootstrap steps.

What tools are required to run the S3 stage-and-verify script?▼

The script requires the AWS CLI, python3, and jq installed on the machine running it. It also expects valid AWS credentials with permission to write and read objects in the target private bucket.

Why should I verify S3 uploads with head-object instead of trusting aws s3 cp?▼

A successful cp exit code does not guarantee the final object matches expectations, especially with multipart uploads or overwritten keys. head-object returns authoritative metadata like ContentLength, ETag, and LastModified directly from S3.

When should I not use S3 for artifact delivery to hosts?▼

S3 staging adds an extra hop, so it is less suitable when the artifact is already on the target host or when a direct registry push, such as a container registry, is available. Use it when hosts can authenticate to a private bucket and need a durable, auditable delivery path.