What problem does it solve? Setting up S3 access for workloads running on Amazon EKS normally requires juggling IAM roles, trust policies, ServiceAccounts, and credential management. This Skill automates the entire flow so pods can read and write S3 objects without static AWS credentials or IRSA OIDC configuration. ## Core Features & Use Cases - S3 Bucket Provisioning: Create buckets with AES-256 encryption, versioning, lifecycle expiration rules, CORS, and optional public-read policies via a single script. - EKS Pod Identity Setup: Create IAM roles with pods.eks.amazonaws.com trust policies, attach scoped S3 policies (read-only, read-write, prefix-restricted), and link them to Kubernetes ServiceAccounts through Pod Identity Associations. - Reference Templates: Includes IAM policy JSON templates, Kubernetes manifests (ServiceAccount, Deployment, ConfigMap, Kustomize overlay), and a full S3 OpenAPI 3.2.0 specification. - Use Case: You are deploying an API on EKS that stores user uploads in S3. Run one command to create the bucket, IAM role, ServiceAccount, and Pod Identity Association, then verify access from a test pod. ## Quick Start Ask the AI to create an S3 bucket named my-app-uploads in us-east-1 and configure EKS Pod Identity so the my-app-api ServiceAccount in the my-app namespace can access it without static credentials.