-
Notifications
You must be signed in to change notification settings - Fork 239
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
SSM and SecretsManager Config Variable support #1894
Comments
Thank you, @driverpt and certainly something we can consider for 2023. |
@mhausenblas , is it also possible to add Lambda doesn't have the Ideally we would like to spin out an OTEL Collector the sameway as we do in ECS |
would be really helpful |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
Not Stale |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
I think it's work in progress according to the Roadmap :) |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been marked as stale for 30 days with no activity. |
I think it's in progress and can't be closed |
Regarding the secretsmanager scheme on the confmap, are there any plans to bring it live in the AWS Otel collector? I see the topic has been put on closed, but this feature is somehow not available. Thanks for your support. |
Is your feature request related to a problem? Please describe.
We would like to run OTEL Collector as Lambda Layer but we need the External Provider Key to be injected from AWS SecretsManager.
The purpose is to prevent attaching Lambdas to VPC to avoid IP Exhaustion.
Describe the solution you'd like
Have a custom AWS Config Provider in OTEL Config, e.g.:
Describe alternatives you've considered
N/A
Additional context
External Providers as in DataDog, NewRelic, Splunk, etc.....
The text was updated successfully, but these errors were encountered: