[8.13](backport #3823) Add a new section on how to collect CloudTrail events using Amazon Data Firehose

[mergify]

This tutorial has reached a pretty stable status and is ready to be reviewed.

Doc preview.

Relates to #3819

---

This is an automatic backport of pull request #3823 done by [Mergify](https://mergify.com).

[mergify]

Cherry-pick of ec22304 has failed:

On branch mergify/bp/8.13/pr-3823
Your branch is up to date with 'origin/8.13'.

You are currently cherry-picking commit ec223045.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-cloudtrail-cloudwatch.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-cloudtrail-dashboard.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-cloudtrail-discover.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-cloudtrail-logsexplorer.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-delivery-stream.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-failed-delivery-stream.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-monitor-cloudtrail-logs.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-subscription-filter.png
	new file:   docs/en/observability/cloud-monitoring/aws/images/firehose-verify-events-cloudwatch.png
	modified:   docs/en/observability/cloud-monitoring/aws/monitor-amazon-intro.asciidoc
	new file:   docs/en/observability/cloud-monitoring/aws/monitor-aws-cloudtrail-firehose.asciidoc

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   docs/en/observability/cloud-monitoring/aws/monitor-aws-agent.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[github-actions]

A documentation preview will be available soon.

• 🔨 Buildkite builds
• 📚 HTML diff
• 📙 Preview page

Request a new doc build by commenting

• Rebuild this PR: run docs-build
• Rebuild this PR and all Elastic docs: run docs-build rebuild

_{run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.}

_{If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.}

[bmorelli25]

@mergify update

[bmorelli25]

@mergify rebase

[mergify]

update

☑️ Nothing to do

• -conflict [📌 update requirement]
• #commits-behind>0 [📌 update requirement]
• -closed [📌 update requirement]
• queue-position=-1 [📌 update requirement]

[mergify]

rebase

☑️ Nothing to do

• -conflict [📌 rebase requirement]
• -closed [📌 rebase requirement]
• queue-position=-1 [📌 rebase requirement]
• any of:
  • #commits-behind>0 [📌 rebase requirement]
  • #commits>1 [📌 rebase requirement]
  • -linear-history [📌 rebase requirement]

[mergify]

This pull request is now in conflict. Could you fix it @mergify[bot]? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b mergify/bp/8.13/pr-3823 upstream/mergify/bp/8.13/pr-3823
git merge upstream/8.13
git push upstream mergify/bp/8.13/pr-3823

[bmorelli25]

@mergify update

[mergify]

update

☑️ Nothing to do

• #commits-behind>0 [📌 update requirement]
• -closed [📌 update requirement]
• -conflict [📌 update requirement]
• queue-position=-1 [📌 update requirement]

[bmorelli25]

@mergify refresh

[mergify]

refresh

✅ Pull request refreshed