Optimize GitLab object storage for scale and performance

This post details the configuration of GitLab's object storage for scale and performance. It introduces a consolidated form for artifacts, LFS, uploads, and packages, emphasizing the use of IAM roles for authentication and server-side encryption. It also outlines separate configuration for the container registry using the s3_v2 driver and disabling proxy downloads for direct client access. The post provides specific configuration examples for AWS, GCP, and Azure, and recommends using separate buckets for different data types.