-
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
fix(inputs.cloudwatch): enable custom endpoint support #12657
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. I wonder if we should use the EndpointResolverFromURL
function instead of completely customizing the endpoint-resolver, but the present code also works for me. So either change or merge as is @powersj, both is fine with me.
If a user specifis a specific region and endpoint, then the cloudwatch client needs to be set up to use those two values and override the default values that are provided. fixes: influxdata#12653
Download PR build artifacts for linux_amd64.tar.gz, darwin_amd64.tar.gz, and windows_amd64.zip. 👍 This pull request doesn't change the Telegraf binary size 📦 Click here to get additional PR build artifactsArtifact URLs |
(cherry picked from commit f206c27)
If a user specifies a specific region and endpoint, then the cloudwatch client needs to be set up to use those two values and override the default values that are provided.
fixes: #12653