elastic / elastic/integrations
[LogsDB] [Stack 8.19.22-SNAPSHOT] [amazon_security_lake] Failing test daily: script test: routed_data_streams in amazon_security_lake.event
- Dominant language
- Handlebars
- Stars
- 333
- Forks
- 647
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 209
Description
- Stack version: 8.19.22-SNAPSHOT
- LogsDB: enabled
- Package: amazon_security_lake
- Failing test: script test: routed_data_streams
- DataStream: event
- Owners:
- @elastic/security-service-integrations
- @elastic/sit-crest-contractors
Failure:
```
routed_data_streams.txt:26: setting up service: could not boot up service using Docker Compose: running Docker Compose up command failed: exit status 18: pull access denied for minio/minio, repository does not exist or may require 'docker login': denied: requested access to the resource is denied: RUN routed_data_streams
# Verify that events from the event data stream are routed to OCSF-category-specific
# data streams via routing rules.
#
# The test data in MinIO provides one event per OCSF category_uid value (1–6),
# derived from the pipeline test fixtures:
# - category_uid 1 → amazon_security_lake.system_activity (rerouted)
# - category_uid 2 → amazon_security_lake.findings (rerouted)
# - category_uid 3 → amazon_security_lake.iam (rerouted)
# - category_uid 4 → amazon_security_lake.network_activity (rerouted)
# - category_uid 5 → amazon_security_lake.discovery (rerouted)
# - category_uid 6 → amazon_security_lake.application_activity (rerouted)
#
#
```
First build failed: https://buildkite.com/elastic/integrations/builds/49550
Contributor guide
Research direction
Start with the amazon_security_lake script test routed_data_streams and its routed_data_streams.txt fixture, then reproduce the Docker Compose setup failure for the event data stream. Confirm the required service can start and that the test completes with events routed to the six listed OCSF-category data streams.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose
- Domain
- data-engineering, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100