MinIO Fundamentals
MinIO is an S3-compatible object storage service. Applications store objects in buckets through an API, while MinIO distributes data and parity across drives and provides versioning, retention, replication, identity, and operational controls.
itStorage, backup, and data protection | OpenSkills.info
Intro
MinIO Fundamentals
MinIO provides object storage through an S3-compatible API. A client addresses an object by bucket and object name rather than mounting a remote file system or reading blocks. The service owns the namespace, object metadata, placement, protection, and API behavior.
Clients send authenticated S3 requests to MinIO endpoints. Buckets organize the namespace. MinIO divides object data into data and parity shards and places them across an erasure set. One or more erasure sets form a server pool, and deployments can contain multiple pools. Identity, encryption, versioning, retention, replication, healing, monitoring, and capacity management surround that data path.
Objects are not files on a shared disk
An object combines data, metadata, and an object name inside a bucket. Applications use API operations to create, retrieve, list, and delete objects. The object name may contain slash characters, but that does not turn the service into a POSIX file system with the same rename, locking, or in-place update behavior.
Continue the course
This section is part of the paid course.
See pricing to subscribe, or log in if you already have access.
Where this skill leads
Relevant careers
See how this topic contributes to broader role-level skill maps.
Sources
- https://docs.min.io/aistor/operations/core-concepts/erasure-coding/
Supports
- Server pools, erasure sets, data and parity shards, quorum, healing, failure domains, and capacity tradeoffs
- https://docs.min.io/aistor/administration/objects-and-versioning/
Supports
- Bucket and object namespace
- Versioned write, read, list, delete marker, and permanent version deletion behavior
- Capacity effects of full versions
- https://docs.min.io/aistor/administration/object-locking-and-immutability/
Supports
- Write-once, read-many retention for versioned objects
- Relationship between versioning, retention, and deletion
- https://docs.min.io/aistor/administration/replication/
Supports
- Replication modes and operational prerequisites
- Version matching and versioning requirements