Lab: S3-compatible Object Storage simulated with MinIO

What you will learn in this TP

• Use an S3 API outside AWS
• Version and archive objects
• Share an object temporarily

Introduction #

What you will learn in this section

• Use an S3 API outside AWS
• Version and archive objects
• Share an object temporarily

Context. The team is moving its backups to OVHcloud Object Storage. You validate scripts and configuration on a local S3 API.

Prerequisites: Docker, the AWS CLI (for the S3 API), kubectl, k3d and Terraform 1.7 or later; everything is simulated locally, with no OVHcloud account  ·  Estimated time: 35 min

Validated S3 scripts, ready for the OVHcloud endpoint.

Hands-on #

Guided steps, with their solution.

1. 1. Start MinIO

   Why? MinIO implements the S3 API: AWS tools work by changing the URL, as with OVHcloud.

   Start MinIO and create an ovh-local CLI profile.

2. 2. Versioned bucket

   Why? Versioning protects backups from overwrites and deletion.

   Create sauvegardes, enable versioning, upload two versions of a file and list them.

3. 3. Lifecycle and temporary link

   Why? Lifecycle deletes old versions automatically; a presigned link shares without opening the bucket.

   Add a rule deleting non-current versions after 30 days, then generate a 10-minute link.

4. 4. Sync a folder

   Why? sync only transfers differences: ideal for daily backups.

   Sync a local folder, change a file and sync again watching the transfers.

Difficulty level : ●●○○○ (2/5)