aaron-y-chen opened a new pull request, #73509:
URL: https://github.com/apache/airflow/pull/73509
related: #52712
## Summary
Add Amazon Kinesis Data Streams integration to the common messaging
interface (AIP-82), connecting the existing `KinesisTrigger` to
`MessageQueueTrigger` using `scheme="kinesis"`.
- Implements `KinesisMessageQueueProvider` with scheme-based dispatch
(`scheme="kinesis"`).
- Registers the queue provider in `provider.yaml` and updates provider
metadata.
- Adds user documentation in `message-queues/index.rst` and an illustrative
example Dag (`example_kinesis_message_queue.py`).
## Testing
- **Live AWS E2E Verification**:
Verified against a live Amazon Kinesis Data Stream
(`airflow-kinesis-cmq-e2e` in `us-west-2`) with a running Airflow Triggerer:
1. A test record (`kinesis-e2e-payload-001`) was sent to Kinesis via AWS
CLI `put-record`.
2. `MessageQueueTrigger(scheme="kinesis")` detected the record and emitted
an `AssetEvent` (`kinesis://airflow-kinesis-cmq-e2e`).
3. The Scheduler automatically triggered an `asset_triggered` Dag run
(`asset_triggered__2026-09-21T21:46:23.928742+00:00_I3mBFdjv`), and the task
successfully decoded and verified the record data.
### E2E Screenshots
1. **AWS Kinesis Console (Data viewer showing the put record)**:
<img width="1431" height="730" alt="kinesis_1"
src="https://github.com/user-attachments/assets/8b356751-2a4b-4569-9acd-1e5b0daf4ed3"
/>
2. **Airflow Web UI (asset_triggered Dag run and decoded log)**:
<img width="1909" height="492" alt="kinesis_2"
src="https://github.com/user-attachments/assets/2df7cceb-35ab-4e4e-8c98-b8244718e735"
/>
---
##### Was generative AI tooling used to co-author this PR?
<!--
If generative AI tooling has been used in the process of authoring this PR,
please
change below checkbox to `[X]` followed by the name of the tool, uncomment
the "Generated-by".
-->
- [x] Yes (please specify the tool below)
Generated-by: [Codex-6] following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
---
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]