Add AWS auth for OpenSearchDB http_auth initialization #2376
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.
This commit introduces a new test validating the initialization of
OpenSearchDB
withAWSV4SignerAuth
for HTTP authentication. Additionally, it updates thepoetry.lock
file to reflect dependencies changes with Poetry 2.1.1.Related to #2375
Description
The current OpenSearch configuration requires username and password for authentication, which is not compliant with security policies in many enterprises that enforce AWS IAM-based authentication (e.g., AWS SigV4 via SAML or IAM roles).
This feature request proposes adding support for AWS authentication methods such as AWSV4SignerAuth or AWS4Auth, which are already supported by the opensearch-py library. This would enable seamless authentication via AWS IAM roles, improving security, compliance, and ease of integration with AWS-hosted OpenSearch domains.
Fixes # issue
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Augmented the current test to also exercise the new
http_auth
argChecklist:
Maintainer Checklist