-
_This issue was originally opened by @rajeshwar-nu as hashicorp/terraform#20665. It was migrated here as a result of the [provider split](https://www.hashicorp.com/blog/upcoming-provider-changes-in-te…
ghost updated
4 months ago
-
**Describe the bug**
While using the boto3 library, I can authenticate and interact with AWS services using the IAM role assigned to my EC2 instance. However, when attempting to perform similar opera…
-
IAM role inline policies have three modes. When setting `inlinePolicies`:
- to an empty array or `undefined` (`None`, `nil`, etc.), the provider _does not_ manage the inline policies.
- to an array…
-
Today, users can use either an AWS IAM role using a pod identity or an IAM user configured through a Dapr component.
For some cases it's best to mix and match both.
Reference: https://docs.aws.a…
-
Instead of direct IAM role is IRSA supported for S3 auth? https://aws.amazon.com/blogs/opensource/introducing-fine-grained-iam-roles-service-accounts/
-
The documentation states that we can use 'aws_iam' with ACCESS_KEY+SECRET_KEY.
```
output {
opensearch {
hosts => ["hostname:port"]
auth_type => …
-
### Terraform Core Version
1.5.3
### AWS Provider Version
5.8.0
### Affected Resource(s)
- aws_iam_role_policy_attachment
- aws_iam_role
### Expected Behavior
I provide the list …
-
feature request:
While using IAM Roles Anywhere in order to allow on-premise servers to access AWS resources such as S3, the metadata url would not be the typical `169.254.169.254` but `localhost` …
-
**Describe the bug**
I encountered an error when running terraform command to install RADLab UI following the doc https://googlecloudplatform.github.io/rad-lab/docs/rad-lab-ui/ui_installation/infrast…
-
When the provider is run in an EKS pod, with the IAM assume role setup, that works with the AWS provider too, the provider cannot use the assumed role, the following error is dropped:
`* failed to lo…