Terraform provider for managing MinIO S3-compatible object storage buckets, IAM users, and advanced features through infrastructure as code.
Terraform Provider for MinIO is an open-source Terraform provider that enables infrastructure as code management for MinIO object storage deployments. It allows users to programmatically create, configure, and manage MinIO resources including S3-compatible buckets, IAM users, policies, encryption, replication, and lifecycle rules. The provider solves the problem of manual MinIO configuration by bringing it under Terraform's declarative infrastructure management.
Infrastructure engineers, DevOps teams, and developers who use MinIO for object storage and want to manage it through Terraform's infrastructure as code workflows. It's particularly valuable for teams running self-hosted MinIO deployments or using S3-compatible storage services.
Developers choose this provider because it offers complete MinIO API coverage with 55+ resources, works with any S3-compatible backend, and follows security-first principles with multiple authentication methods. It's maintained by an active community and provides enterprise-grade features for production MinIO deployments.
Terraform provider for managing MinIO S3 buckets and IAM Users.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
With over 55 resources and 25 data sources, it supports everything from bucket management to advanced features like replication and encryption, as stated in the README.
The s3_compat_mode allows it to work with various S3-compatible backends such as Cloudflare R2 and DigitalOcean Spaces, expanding its utility beyond MinIO.
Supports multiple authentication methods including STS AssumeRole and OIDC, adhering to a security-first approach as highlighted in the key features.
Every attribute has descriptions and all resources support import, making it easier to integrate into existing infrastructure, as mentioned in the README.
Versions from v2.0.0 are under AGPL-3.0, which may impose copyleft obligations that some organizations find restrictive for their infrastructure code.
Acceptance tests require Docker Compose and running multiple MinIO instances, which adds complexity for contributors and those wanting to run tests locally.
As a community-driven project, it might lack the guaranteed support and rapid feature updates compared to official providers from large vendors.