-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Kinesis output plugin does not work in govcloud #2911
Comments
Do you know if it works outside of the govcloud? |
Yes it works fine. It appears that the go AWS SDK can't resolve the endpoint correctly when it's in govcloud, since they do not obey the same naming convention for the URLs. |
All that really needs to be done is exposing a configuration value for the endpoint to be set in the AWS service configuration. I did something like:
This is definitely something I can contribute, I'm just not sure about the go style conventions used by telegraf. |
That looks good. |
Ok, actually, it's due to the version of the aws-sdk-go dependency. The commit listed in Godeps was before Kinesis was added to govcloud, so it doesn't have a resolver for kinesis when in us-gov-west-1. Newer versions of the SDK resolve this endpoint automatically. |
Thanks, I'll update the dependency. |
I updated the dependency, give it a spin if you can. |
I'll fire it up tomorrow and report back. |
Confirming that this works now, with the exact same config file I was using before. |
Bug report
Relevant telegraf.conf:
System info:
Telegraf v1.3.0
Amazon Linux
Steps to reproduce:
Expected behavior:
Telegraf to start and write metrics to the stream.
Actual behavior:
Telegraf fails to start, prints out that the 'Endpoint' configuration is required since it cannot resolve it automatically.
Additional info:
The text was updated successfully, but these errors were encountered: