Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

Inject AWS_REGION/AWS_DEFAULT_REGION even if pod doesn't have serviceAccount #192

Open
mbonica1990 opened this issue Sep 18, 2023 · 0 comments

Comments

@mbonica1990
Copy link

What would you like to be added:
I would like an option (ideally, in EKS) to inject AWS_REGION and AWS_DEFAULT_REGION into all pods, even if they don't have service accounts. (Right now, this only happens if I have service accounts.)

Why is this needed:
I have scenarios where the code running in my pods need to be aware of their AWS region, even if they don't use STS. The main one is if I'm using an application performance monitoring (APM) agent like NewRelic, Splunk, or OpenTelemetry, where I might tag my telemetry with the current region, so I can identify performance issues endemic to one region but not another.

For example, in my newrelic.yml, I do this:
labels: “region:<%= ENV.fetch(‘AWS_REGION’){ ‘null’ } %>;”

...and in NewRelic, I can query and filter on application data just from us-east-2 or us-east-1. I need AWS_REGION to be set for this, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant