Deprecation of signature signing v2

GitLab is deprecating support for AWS S3 signature signing v2 in the Container Registry. This feature allowed users to authenticate and authorize requests to Amazon S3 buckets using an older signing process. However, AWS SDK v2 no longer supports signature signing v2, and it has been phased out for new buckets and in certain regions by Amazon.

To ensure continued compatibility and security, users are advised to transition to signature signing v4, which is the current standard supported by AWS. This change will require updating your S3 bucket configurations and ensuring that your GitLab Container Registry settings are compatible with signature signing v4.

Migration Steps:

1. Check your S3 storage backend configuration in the GitLab Container Registry settings.
2. Remove the v4auth: false option if it's set. This is the key step to enable v4 authentication.
3. No other changes are typically needed, as your existing credentials should work with v4 authentication.

Note: If you encounter any issues after making these changes, try regenerating your AWS credentials.

For more information on configuring your registry with the latest AWS S3 standards, please refer to our documentation on configuring the Container Registry.