[AWS] [API Gateway] Logs data stream

[lucian-ioan]

What does this PR do?

Adds logs data stream which collects API Gateway logs from CloudWatch or S3.

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.

Author's Checklist

• [ ]

How to test this PR locally

Related issues

• Closes [AWS] [API Gateway] Logs data stream #6991

Screenshots

[elasticmachine]

💚 Build Succeeded

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-07-20T10:50:57.477+0000

• Duration: 54 min 54 sec

Test stats 🧪

Test	Results
Failed	0
Passed	198
Skipped	4
Total	202

🤖 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% (16/16)	💚
Files	94.118% (16/17)	👎 -3.116
Classes	94.118% (16/17)	👎 -3.116
Methods	85.862% (249/290)	👎 -6.31
Lines	86.001% (7464/8679)	👎 -5.149
Conditionals	100.0% (0/0)	💚

[tdancheva]

Since @zmoog already picked it up, I will just leave a comment, can you please add a standalone S3 bucket option, like I have done here? You can see this issue. We need to do this for all the data streams where it is missing. I did it for and merged Cloudtrail and vpcflow so far.

[zmoog]

This may be a leftover, I noticed we have two "Queue URL" fields:

[zmoog]

The PR looks good. I missed only one small thing in the last pass: an SQS option at the end of the advanced setting instead of close to the other SQS options.

[zmoog]

I would only move the SQS option with the others and then LGTM.

[elasticmachine]

Package aws - 1.49.0 containing this change is available at https://epr.elastic.co/search?package=aws