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.

Sign up for GitHub

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

Jump to bottom

Amazon Security Lake integration uses reserved environment variable #235

Closed
Tracked by #238
AlexRuiz7 opened this issue May 28, 2024 · 0 comments · Fixed by #240
Closed
Tracked by #238

Amazon Security Lake integration uses reserved environment variable #235

AlexRuiz7 opened this issue May 28, 2024 · 0 comments · Fixed by #240
Assignees
@AlexRuiz7
Labels
level/task Task issue type/bug Bug issue

Comments

@AlexRuiz7
Copy link
Member

Description

During the internal testing of #128, it was reported that it was not possible to configure the AWS Lambda function because the AWS_REGION environment variable we use is reserved by AWS.

We need to change the name of environment variable in:

  • source code
  • repository documentation
  • official documentation

image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@AlexRuiz7 AlexRuiz7

Labels
level/task Task issue type/bug Bug issue
Projects
No open projects
Release 4.9.0
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Rename environment variable wazuh/wazuh-indexer
1 participant
@AlexRuiz7