This issue was moved to a discussion.
You can continue the conversation there. Go to discussion →
AWS managed prometheus integration with vector sink prometheus_remote_write #20968
Labels
type: bug
A code related bug.
You can continue the conversation there. Go to discussion →
A note for the community
Problem
I am trying to connect my AWS managed prometheus instance with my vector agent running on a ec2 instance with a ecs agent running. I am trying to send ecs_metrics to prometheus. I am able to do so with a prometheus server running on the same host machine and using the prometheus_exporter sink but not with the remote_write sink. I enabled VECTOR_LOG=aws_config=debug on my vector agent and have verified that I am able to authenticate with AWS to receive the correct credentials only when I pass the env variables with the access key, session token, secret key.
Is there a way for the vector agent to assume the role that is attached to the task that vector is running in?
I am running the docker image: timberio/vector:0.39.0-alpine
Configuration
Version
timberio/vector:0.39.0-alpine
Debug Output
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: