Closed AlexRuiz7 closed 1 month ago
During the AWS Lambda configuration, it's needed to grant permissions to the Lambda function to access the S3 bucket, as seen in this guide. That solves the issue.
Improved logging
[INFO] 2024-05-29T10:18:36.787Z Found credentials in environment variables.
START RequestId: 220ef125-3f94-43f7-a2e2-c6394f49185d Version: $LATEST
[INFO] 2024-05-29T10:18:36.954Z 220ef125-3f94-43f7-a2e2-c6394f49185d Lambda function invoked due to 20240422_ls.s3.2f062956-5a30-4c2a-b693-a0f5d878294c.2024-04-22T14.20.part39.txt.
[INFO] 2024-05-29T10:18:36.954Z 220ef125-3f94-43f7-a2e2-c6394f49185d Source bucket name is REDACTED. Destination bucket is REDACTED.
[INFO] 2024-05-29T10:18:36.954Z 220ef125-3f94-43f7-a2e2-c6394f49185d Reading 20240422_ls.s3.2f062956-5a30-4c2a-b693-a0f5d878294c.2024-04-22T14.20.part39.txt.
[INFO] 2024-05-29T10:18:37.125Z 220ef125-3f94-43f7-a2e2-c6394f49185d Transforming Wazuh security events to OCSF.
[INFO] 2024-05-29T10:18:37.311Z 220ef125-3f94-43f7-a2e2-c6394f49185d Uploading data to REDACTED.
END RequestId: 220ef125-3f94-43f7-a2e2-c6394f49185d
REPORT RequestId: 448ff821-292b-4e61-b788-f4f59d0ed68d Duration: 354.24 ms Billed Duration: 355 ms Memory Size: 512 MB Max Memory Used: 168 MB
Description
During the internal testing of the Amazon Security Lake integration, it was reported a failure on the AWS Lambda function caused by Access Denied error.
Tasks