Remove dangling file for ASL integration (#665)

wazuh · Feb 3, 2025 · 9f29862 · 9f29862
1 parent 56f72b8
commit 9f29862
Show file tree

Hide file tree

Showing 4 changed files with 6 additions and 194 deletions.
diff --git a/integrations/amazon-security-lake/CONTRIBUTING.md b/integrations/amazon-security-lake/CONTRIBUTING.md
@@ -16,6 +16,12 @@ This Docker Compose project will bring up these services:
 - our [events generator](../tools/events-generator/README.md)
 - an AWS Lambda Python container.
 
+| Service       | Address                  | Credentials     |
+| ------------- | ------------------------ | --------------- |
+| Wazuh Indexer | https://localhost:9200   | admin:admin     |
+| Dashboards    | https://localhost:5601   | admin:admin     |
+| S3 Ninja      | http://localhost:9444/ui |                 |
+
 On the one hand, the event generator will push events constantly to the indexer, to the `wazuh-alerts-4.x-sample` index by default (refer to the [events generator](../tools/events-generator/README.md) documentation for customization options). On the other hand, Logstash will query for new data and deliver it to output configured in the pipeline `indexer-to-s3`. This pipeline delivers the data to an S3 bucket, from which the data is processed using a Lambda function, to finally be sent to the Amazon Security Lake bucket in Parquet format.
 
 The pipeline starts automatically, but if you need to start it manually, attach a terminal to the Logstash container and start the integration using the command below:

diff --git a/integrations/amazon-security-lake/aws-lambda.dockerfile b/integrations/amazon-security-lake/aws-lambda.dockerfile
diff --git a/integrations/amazon-security-lake/logstash/pipeline/indexer-to-file.conf b/integrations/amazon-security-lake/logstash/pipeline/indexer-to-file.conf
diff --git a/integrations/docker/amazon-security-lake.yml b/integrations/docker/amazon-security-lake.yml