MinIO
MinIOcloud2 credentials
Root User / Root Password
minio / root-credentials
MinIO root credentials define the root user with complete access and permissions to the deployment. MinIO documents setting root user and root password through environment variables or configuration settings.
Location
MINIO_ROOT_USER, MINIO_ROOT_PASSWORD, MINIO_ACCESS_KEY, MINIO_SECRET_KEYsystemd environment files, Docker Compose files, Helm values, and MinIO server config
Kubernetes Secrets, Docker secrets, cloud secret managers, and vault entries
committed deployment manifests, examples, tests, and container configs
startup logs, shell history, and CI output
MinIO S3 API and ConsoleNotes
The root user has full administrative access. Older MINIO_ACCESS_KEY and MINIO_SECRET_KEY names appear in legacy deployments.
Access Key / Secret Key
minio / access-secret-key
MinIO users and service accounts authenticate to the S3-compatible API with access keys and secret keys. Identity management docs cover built-in users, service accounts, and external identity providers.
Looks like
patternAKIA[0-9A-Z]{16}Location
AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY, MINIO_ACCESS_KEY, MINIO_SECRET_KEYmc client config, application config, .env files, and deployment manifests
Kubernetes Secrets, cloud secret managers, CI/CD variables, and service account secret stores
S3 client code, tests, notebooks, and accidentally committed configs
S3 client debug logs and CI traces
AuthorizationAWS Signature authentication headers derived from access and secret keys
Notes
Secret key exposure grants the permissions assigned to the MinIO user or service account policies.
Scope
Authorized use
LOLCreds helps map the credential surface of real products: known defaults, generated values, credential locations, and exposure patterns.