Skip to content
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

[AWS GovCloud S3] Support for MFA-enabled User and Search S3 Connector #2550

Open
3 tasks
architecthutch opened this issue May 13, 2024 · 0 comments
Open
3 tasks
Labels

Comments

@architecthutch
Copy link

Problem Description

In using an MFA-enabled AWS GovCloud user's Access + Secret keys when configuring the S3 search connector in ECE 3.6.2, Stack Pack 8.13.3, I receive the following error when attempting to sync my data:

Connector error ClientError: An error occurred (InvalidAccessKeyId) when calling the ListBuckets operation: The AWS Access Key Id you provided does not exist in our records.

I leverage an MFA-enabled named profile within AWS CLI to perform automation with the Boto3 libraries as well as maintain Zero Trust compliance when authenticating. This also ensures my credentials are secure, as the Configuration section of the Connector setup states:
Encryption for data source credentials is unavailable in this version. Your data source credentials will be stored, unencrypted, in Elasticsearch.

Federal guidelines (NIST 800-53 Rev5, NIST 800-207, EO 14028, etc) require securing data in transit and data at rest, such as that of credentials and S3 Bucket contents. In this scenario I have an AWS CMK-encrypted, non-Public S3 bucket the Connector is attempting to access. These security measures need to remain in place for compliance reasons.

Proposed Solution

  • Enable the capability for the connector to handle MFA.
  • If not feasible currently, request contact with AWS to determine viability
  • Validate functionality in an AWS GovCloud environment with

Additional Context

This recommendation was output from a discussion with Elastic over their slack channel mentioned above. The intent is to leverage data from this connector as an indexing point with ELSER and semantic search.

@architecthutch architecthutch added the enhancement New feature or request label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants