When using GCP workload identity pool with the AWS provider, then running the GCP source plugin inside AWS Fargate, an error like dial tcp 169.254.169.254:80: connect: invalid argument occurs.

Fargate uses a different metadata endpoint, ${ECS_CONTAINER_METADATA_URI_V4}/task, but it is not clear how to make this work.

A workaround one user found is to take the AWS token from the session and save it as an env var, but it would be great if we could better document the best approach to doing this, or have it work automatically as part of the plugin authentication process.