Closed danielmotaleite closed 1 year ago
Hi,
We have users and recent contributors of this processor so if this was more wide spread I would have expected more reports of any issue.
Is this happening 100% of the time? When you use curl it works?
2023-10-06T21:22:20Z D! [processors.aws_ec2] Initializing AWS EC2 Processor 2023-10-06T21:22:20Z D! [processors.aws_ec2] Initializing AWS EC2 Processor
Why did this print twice? Do you have multiple instances of the processor?
GetInstanceIdentityDocument, canceled, context deadline exceeded
This error comes right after attempting to get the identity document, which are direct calls to the AWS go library. We are passing a background context, so no specific timeout. These operation errors are effectively something went wrong with the request itself by the library. These types of context deadline messages can indicate an issue with networking, DNS, etc. There is not even an HTTP status code at this point.
Hello! I am closing this issue due to inactivity. I hope you were able to resolve your problem, if not please try posting this question in our Community Slack or Community Forums or provide additional details in this issue and reqeust that it be re-opened. Thank you!
Relevant telegraf.conf
Logs from Telegraf
System info
telegraf 1.28.2
Docker
using the telegraf-ds helm v1.1.17
Steps to reproduce
Expected behavior
Get the metadata, just like the command line can do:
TOKEN=
curl -X PUT "http://169.254.169.254/latest/api/token" -H "X-aws-ec2-metadata-token-ttl-seconds: 21600"
\ && curl -H "X-aws-ec2-metadata-token: $TOKEN" -v http://169.254.169.254/latest/dynamic/instance-identity/documentActual behavior
error and telegraf fails to start
Additional info
Maybe telegraf is still using idms v1 access (without any token) and needs to be updated to v2?