Incorrect AWS metadata server path when running on Fargate #1099
Labels
priority: p2
Moderately-important priority. Fix may not be included in next release.
type: bug
Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Runs fine on EC2, but running on Fargate gives
Looking at https://stackoverflow.com/questions/57065458/cannot-access-instance-metadata-from-within-a-fargate-task it appears fargate has a different endpoint for iam metadata
The text was updated successfully, but these errors were encountered: