[amazon_security_lake] Add system tests for aws-s3 input

[bhapas]

Proposed commit message

Add system tests for aws-s3 input in amazon_security_lake integration by using terraform service deployer and using the SQS queue_url generated in terraform outputs.

Checklist

• I have reviewed tips for building integrations and this pull request is aligned with them.
• I have verified that all data streams collect metrics or logs.
• I have added an entry to my package's changelog.yml file.
• I have verified that Kibana version constraints are current according to guidelines.

How to test this PR locally

Run elastic-package stack up -d -v && elastic-package test system -v

Related issues

• Relates [Meta][aws-s3] Add system tests for integrations that use aws-s3 input #7034

[elasticmachine]

💔 Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-11-09T11:20:24.300+0000

• Duration: 11 min 45 sec

Steps errors

Expand to view the steps failures

Check integration: amazon_security_lake

• Took 0 min 1 sec . View more details here
• Description: ../../build/elastic-package check -v

Take down the Elastic stack

• Took 0 min 0 sec . View more details here
• Description: build/elastic-package stack down -v

Google Storage Download

• Took 0 min 0 sec . View more details here

Google Storage Download

• Took 0 min 0 sec . View more details here

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[elasticmachine]

🌐 Coverage report

Name	Metrics % (covered/total)	Diff
Packages	100.0% (1/1)	💚
Files	70.588% (12/17)	👎 -29.412
Classes	70.588% (12/17)	👎 -29.412
Methods	57.471% (50/87)	👎 -39.897
Lines	39.967% (3842/9613)	👎 -55.46
Conditionals	100.0% (0/0)	💚

[andrewkroh]

Checkout #7887 (comment). I think security lake uses a custom notification format to SQS instead of letting S3 write the event to SQS.

[bhapas]

Depends on elastic/package-spec#662

[mrodm]

Hi @bhapas, please update your branch with the latest contents from main branch. There was an important PR merged updating the CI pipelines. Thanks!

[botelastic]

Hi! We just realized that we haven't looked into this PR in a while. We're sorry! We're labeling this issue as Stale to make it hit our filters and make sure we get back to it as soon as possible. In the meantime, it'd be extremely helpful if you could take a look at it as well and confirm its relevance. A simple comment with a nice emoji will be enough :+1. Thank you for your contribution!

[botelastic]

Hi! This PR has been stale for a while and we're going to close it as part of our cleanup procedure. We appreciate your contribution and would like to apologize if we have not been able to review it, due to the current heavy load of the team. Feel free to re-open this PR if you think it should stay open and is worth rebasing. Thank you for your contribution!