Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Using workload identity provider in AWS without IMDBS #1152

Open
wellsiau-aws opened this issue Dec 12, 2024 · 0 comments
Open

Using workload identity provider in AWS without IMDBS #1152

wellsiau-aws opened this issue Dec 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@wellsiau-aws
Copy link

Description

I found that the hcp_iam_workload_identity_provider is very cool and allows me to reduce the number of secret zero that I need to handle. Especially when playing with demo / sandbox in my own dev environment / local.

Can we use the workload identity provider without relying on IMDBS to fetch detail such as the AWS region and role name?

I think it would be helpful to understand all environment variables that hcp provider expect to fetch when using credentials.json file.

For example, I was able to workaround the error below by exporting the AWS_REGION env vars.

Error: unable to create HCP api client: no valid credentials available: failed to get new token: failed retrieving AWS region from metadata endpoint: Get "http://169.254.169.254/latest/meta-data/placement/region": context deadline exceeded

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment
@wellsiau-aws wellsiau-aws added the enhancement New feature or request label Dec 12, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant