-
Notifications
You must be signed in to change notification settings - Fork 183
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
[BUG] AWSV4SignerAuth does not accept "aos" #534
Comments
This feels like an OSB problem because the AWS service is definitely |
@dblock AWS service uses
Since OSB relies on opensearch-py to communicate with target clusters, I believe the contributor added this check because opensearch-py might not support
|
@IanHoang That default is correct, the service code is "es". Service codes are used to scope service credentials. Do you not agree? |
@dblock You're right, thanks for calling this out! opensearch-py uses botocore, which still uses |
What is the bug?
When users are using OSB to test a SigV4 authenticated opensearch cluster, they set the environment variable to
aos
oraoss
. However, AWSSigV4Auth class takeses
instead ofaos
. This could be misleading to new OpenSearch users.Are there any plans to support
aos
on top ofes
andaoss
?How can one reproduce the bug?
Error encountered:
What is the expected behavior?
opensearch-py should accept
aos
as well on top ofes
andaoss
.What is your host/environment?
Occurs on MacOS, Linux and with Amazon Managed-Service Clusters
Do you have any screenshots?
N/A
Do you have any additional context?
N/A
The text was updated successfully, but these errors were encountered: