scope support for AWS deployments that have IMDSv1 disabled (Package group)

Proposal

AWS is starting to recommend that their customers disable IMDSv1, for example EKS.

Customers who deploy GitLab with IMDSv1 disabled are likely to have a bad experience as some functionality will work, some functionality will not.

It is unclear which GitLab capabilities depend on IMDS for functionality in AWS, such as obtaining IAM credentials.

A non exhaustive list within ~"group::package":

  • Container registry - use of object storage
  • Dependency proxy
    • Would the Fog update in 13.7 handle back-end storage?
    • Does it access AWS package services?

This is one of a number of issues around GitLab support for deployments with only IMDSv2 enabled. For more information see the description and comments in: #334160 (closed)

Proposal

Scope which GitLab components owned by ~"group::package" use IMDS but won't work with IMDSv1 disabled.

Links to related issues and merge requests / references