Two Kinesis-family services got new names in the last two years: Kinesis Data Firehose became Amazon Data Firehose in February 2024, and Kinesis Data Analytics became Amazon Managed Service for Apache Flink in August 2023. Study material, older docs, and job postings still mix old and new names, so here is exactly what changed and what did not.
Last updated July 2026.
| Old name | New name | Rename date |
|---|---|---|
| Amazon Kinesis Data Firehose | Amazon Data Firehose | February 9, 2024 |
| Amazon Kinesis Data Analytics | Amazon Managed Service for Apache Flink | August 30, 2023 |
Source: AWS What's New posts, Amazon Data Firehose and Managed Service for Apache Flink.
Amazon Data Firehose captures, transforms, and delivers streaming data to destinations like S3, Redshift, OpenSearch Service, Splunk, and Snowflake with no code required. AWS dropped "Kinesis" from the name because Firehose is commonly used on its own, not only as a companion to Kinesis Data Streams, and the old name implied a tighter coupling than actually exists.
Amazon Managed Service for Apache Flink runs full Apache Flink as a serverless, fully managed service, handling provisioning, parallelism, state backends, checkpointing, and recovery so you write the application logic and AWS runs the cluster. It processes data continuously with sub-second latency from sources like Kinesis Data Streams and Amazon MSK. The rename dropped "Kinesis Data Analytics" in favor of naming the underlying engine directly, since Apache Flink is the actual processing framework the service runs.
Both renames are cosmetic. AWS's own announcements state the change applies to the console, documentation, and service web pages only. Service endpoints, API operation names, the AWS CLI, IAM action names, CloudWatch metric namespaces, and billing line items kept their original identifiers. Existing applications, IAM policies, and CloudFormation templates continue to run unchanged.
In practice this means the console and marketing pages say "Amazon Data Firehose," while an IAM policy still grants firehose:PutRecord, the CLI command is still aws firehose, and the CloudWatch namespace is still AWS/Firehose. Same story for Flink: the CLI and API still use kinesisanalyticsv2 under the hood, even though the console calls it Managed Service for Apache Flink.
Domain 1 (Data Ingestion and Transformation, 34% of the exam) lists streaming ingestion services by their current names in the official exam guide, so exam questions and answer choices use "Amazon Data Firehose" and "Amazon Managed Service for Apache Flink." But because the underlying APIs never changed, any hands-on practice, IAM policy example, or CLI reference you touch while studying will still show the pre-rename identifiers. Both are correct: the exam guide and console use the new name, the code and API use the old one. Treat "Kinesis Data Firehose" and "Kinesis Data Analytics" as retired names you will still see in the wild, not as errors.
AWS announced the rename on February 9, 2024. The change applies to the console, documentation, and service web pages only.
No. AWS's announcements confirm service endpoints, APIs, the CLI, IAM access policies, and CloudWatch metrics were unaffected. Existing applications continue to work exactly as they did before the rename.
Amazon Managed Service for Apache Flink, announced August 30, 2023. It is the same fully managed service for running Apache Flink applications, under a name that reflects the underlying engine.
The official exam guide and exam questions use the current names: Amazon Data Firehose and Amazon Managed Service for Apache Flink. You will still see the retired names in CLI commands, IAM policies, and older documentation.
Both services sit inside Domain 1, the largest domain on the DEA-C01 at 34% of scored questions. The full domain breakdown covers exactly where streaming ingestion fits alongside batch sources and transformation services.
See the full domain breakdown →