[aws] add agentless deployment for AWS Kafka

[jakubgalecki0]

Proposed commit message

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.
• I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

• [ ]

How to test this PR locally

Related issues

Screenshots

[github-actions]

✅ Vale Linting Results

No issues found on modified lines!

---

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

[github-actions]

TL;DR

The Check integrations aws Buildkite step failed with exit status 1, but the provided log only contains teardown/artifact-upload output and does not include the original failing command or stack trace. Immediate next step is to inspect the uploaded test artifacts for the first failing suite and rerun the job after confirming.

Remediation

• Download and inspect the uploaded JUnit artifacts (especially build/test-results/aws-*.xml) from build 42950 to identify the exact failed test/assertion.
• Re-run Check integrations aws; if the same suite fails, use the failing XML/log to patch the AWS package test or fixture. If it passes, treat this run as transient/flaky and re-trigger CI.

Investigation details

Root Cause

I could not confirm a code-level root cause from the provided failure log because it starts at teardown and does not include the actual failure section.

What is verifiable:

• Job command was .buildkite/scripts/test_one_package.sh packages/aws origin/main 0a8e12005d1eee88a0e8affaf635f8944e2b3d9f.
• Log shows only:
  • --- [aws] failed
  • Error: The command exited with status 1
  • Artifact upload and stack teardown.
• Latest commit at the failing SHA (0a8e12005d1eee88a0e8affaf635f8944e2b3d9f) modifies docs only:
  • packages/aws/_dev/build/docs/kafka.md
  • packages/aws/docs/kafka.md

Evidence

• Build: https://buildkite.com/elastic/integrations/builds/42950
• Job/step: Check integrations aws
• Key log excerpt (/tmp/gh-aw/buildkite-logs/integrations-check-integrations-aws.txt):
  • line 61: --- [aws] failed
  • line 64: Error: The command exited with status 1
  • lines 68+ show only artifact upload and cleanup

Verification

• Not run locally: this environment only has the post-failure log excerpt and no Buildkite artifact payloads to extract the original failing assertion.

Follow-up

• If you can share the first failing JUnit XML or the pre-teardown section of the Buildkite log, I can pinpoint the exact test and propose a targeted code fix.

Note

🔒 Integrity filter blocked 106 items

The following items were blocked because they don't meet the GitHub integrity level.

• [aws] add agentless deployment for AWS Kafka #19036 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19036 pull_request_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19036 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19037 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19036 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19034 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19033 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19031 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19028 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19024 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19023 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19015 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19014 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19013 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19012 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• #19011 list_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
• ... and 90 more items

To allow these resources, lower min-integrity in your GitHub frontmatter:

tools:
  github:
    min-integrity: approved  # merged | approved | unapproved | none

---

What is this? | From workflow: PR Buildkite Detective

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: aa0748c

History

• 💔 Build #42950 failed 0a8e120

[efd6]

There are a bunch of aws data streams that are having this change made. I would suggest rolling them into a single PR so that just a single version bump is made.

[efd6]

Suggested change

	link: https://github.com/elastic/integrations/pull/1
	link: https://github.com/elastic/integrations/pull/19036

[jakubgalecki0]

These PRs can be merged independently based on the external research. I guess what we could do is to batch them together once more packages are approved.

cc: @ishleenk17