Colin But

Please consider this feature request. It would be more than valuable to have this feature.

Can we re-open this issue please? agree with @starek4 - unless i'm missing something else, I also found out that setting up the `region` key doesn't seem to work and...

@powersj, I'm using the latest version and I'm using profile credentials. Not sure about @starek4 - what credentials method you using? The error we're seeing appears to be from the...

@powersj ``` 2023-08-26T09:13:07Z D! [agent] Connecting outputs 2023-08-26T09:13:07Z D! [agent] Attempting connection to [outputs.cloudwatch_logs] linux arm64 env AWS_REGION is "" setting region to: eu-west-1 loading with root credentials loaded config...

@powersj Yes i'm using `eu-west-1` region. Here's the log with region set as env var: ``` root@ip-172-31-34-228 bin]# AWS_REGION=eu-west-1 ./telegraf --config ../../etc/telegraf/telegraf.conf 2023-08-28T14:57:04Z I! Loading config: ../../etc/telegraf/telegraf.conf 2023-08-28T14:57:04Z I! Starting...

I can certainly try... Agree, it appears to be the go aws sdk could be the problem if the code what you say is as what you expect. Have raised...

for anyone encountering this problem also, the workaround for time being is to simply invoke telegraf by supplying the AWS Region as env var, e.g. ``` AWS_REGION=eu-west-1 ./telegraf --config /etc/telegraf/telegraf.conf...

@powersj i now get a different error: ``` 2023-09-06T09:45:23Z D! [outputs.cloudwatch_logs] Log data: key "field", source "message"... 2023-09-06T09:45:23Z D! [outputs.cloudwatch_logs] Log stream "log-group"... 2023-09-06T09:45:23Z D! [agent] Connecting outputs 2023-09-06T09:45:23Z D!...

@powersj just like last time, it is one single run. I'm running the telegraf within EC2 instance that has a docker container running inside it. Therefore, I'm using the `docker_log`...

@powersj Hi, just wondering whether there is any update regarding this matter since it's been nearly 6 months lapsed. I can see the last activity is your commit of adding...