private-object-access-control

Enforce private object access control on S3-compatible storage with bucket policies and IAM scopes.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/marquesfelip/agents-and-skills --skill private-object-access-control
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: private-object-access-control
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/private-object-access-control
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill private-object-access-control

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a comprehensive framework to enforce private object access control on S3-compatible storage by standardizing bucket policies, IAM scopes, presigned access, and an API proxy pattern. It helps prevent accidental public exposure of objects and enables robust tenant isolation and auditable access.

Core Features & Use Cases

  • Define access models for buckets and objects (presigned URLs, API proxy, direct IAM access) with policy guardrails.
  • Enforce Block Public Access settings across providers and validate configurations to prevent accidental exposure.
  • Implement application-layer authorization to ensure tenants can access only their own objects, with audit trails for sensitive data.
  • Apply cross-tenant isolation checks, least-privilege IAM for applications, and ongoing compliance checks.
  • Provide an end-to-end pattern including an API proxy for high-sensitivity files with server-side access logging and controlled streaming.

Quick Start

Configure a private-object access control workflow for your storage, block public access, and validate cross-tenant isolation.

Frequently Asked Questions about private-object-access-control

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

FAQPage Schema
What is the best way to enforce private object access control on S3-compatible storage?

Private object access control on S3-compatible storage is enforced through explicit bucket policies, least-privilege IAM roles, and optional API proxy patterns for high-sensitivity files, preventing accidental public exposure.

How do I implement tenant isolation for private buckets in cloud environments?

Tenant isolation for private buckets is implemented through application-layer authorization and cross-tenant isolation checks, ensuring tenants access only their own objects with auditable access trails.

When should I use an API proxy pattern instead of presigned URLs for object storage?

Use an API proxy pattern instead of presigned URLs for high-sensitivity files requiring server-side access logging, controlled streaming, and strict application-layer authorization.

How do I block public access and validate configurations to prevent accidental S3 bucket exposure?

Block public access and prevent accidental exposure by enforcing Block Public Access settings across providers and validating configurations with ongoing compliance checks.

Does this private access control approach work with S3-compatible storage across different cloud providers?

Yes, this approach works across S3-compatible storage in cloud environments by standardizing bucket policies, IAM scopes, and Block Public Access settings across different providers.

What IAM roles and bucket policies are needed for least-privilege access to private S3 buckets?

Least-privilege access requires explicit bucket policies and least-privilege IAM roles for applications, ensuring only authorized entities access specific objects with auditable trails.