add 'service' to the configuration and use the value for requests instead of hardcoded "aps" #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
👋 Hello!
Changes:
Motivation:
We have a use case where we run a Mimir cluster exposed through an endpoint fronted by AWS API Gateway, using IAM authentication. We also have multiple Prometheus deployments pushing metrics to Mimir, using IAM credentials.
But without the ability to set the 'service' part of the signature in the sigv4 configuration, the requests are forbidden/403. In our specific case 'execute-api' is needed. Though I think other use cases could also make use of this.
@roidelapluie @gotjosh Let me know what you think. Cheers!