You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/content/configuration.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -393,7 +393,9 @@ To use the EC2 metadata service, the IAM role to use and the AWS region for the
393
393
be specified as `iam_role` and `aws_region` respectively.
394
394
395
395
To use the ECS metadata service, specify only the AWS region for the resource as `aws_region`. ECS
396
-
containers have at most one associated IAM role.
396
+
containers have at most one associated IAM role. As per the [AWS documentation](https://docs.aws.amazon.com/sdkref/latest/guide/feature-container-credentials.html), credentials are
397
+
sourced from the `AWS_CONTAINER_CREDENTIALS_RELATIVE_URI` metadata environment variable or the
398
+
`AWS_CONTAINER_CREDENTIALS_FULL_URI`metadata environment variable in order.
397
399
398
400
> Providing a value for `iam_role` will cause OPA to use the EC2 metadata service even
399
401
> if running inside an ECS container. This may result in unexpected problems if, for example,
0 commit comments