
# Streaming on AWS

Compare documented Streaming deployments on AWS, including operating responsibility, licensing and deployment evidence.

Canonical page: https://launchinyourcloud.com/clouds/aws/streaming/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


## Provider guidance

- Account boundary: AWS account
- Provider group: cloud-infrastructure
- Provider classification: Navigation group for the documented infrastructure offering; read each application path for its actual account boundary. Source: https://docs.aws.amazon.com/accounts/latest/reference/getting-started.html (checked 2026-11-20).
- Network: VPC
- Identity and access: IAM roles and policies
- Installation guidance: CloudFormation or Terraform; review stack changes and requested IAM permissions.
- Guidance source: https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html
- Guidance reviewed: 2026-11-10


### Private offers

AWS Marketplace private offers can contain negotiated pricing and terms for a buyer account. Confirm the product delivery model and your agreement; commitment credit is not established by a directory badge.
Source: https://docs.aws.amazon.com/marketplace/latest/buyerguide/buyer-private-offers-subscribing.html (reviewed 2026-11-14).

### Private connectivity

PrivateLink provides private endpoints to supported services and resources across VPC/account boundaries. Confirm that the selected product exposes a compatible endpoint service.
Source: https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html (reviewed 2026-11-14).

### Cross-account operations

Use an IAM role with scoped permissions and a third-party external ID where applicable. Review the trust principal, support access and revocation separately from installation access.
Source: https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_third-party.html (reviewed 2026-11-14).

### Government environments

AWS GovCloud (US) is a distinct isolated-region environment. A commercial-region product deployment does not establish availability or certification there.
Source: https://docs.aws.amazon.com/govcloud-us/latest/UserGuide/whatis.html (reviewed 2026-11-14).

The listings below have evidence for Amazon Web Services. Read each cloud evidence note for the applicable package, edition and support qualifications.

5 listings.


## Aiven for Apache Kafka BYOC

Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.

- Listing: https://launchinyourcloud.com/directory/aiven-kafka-byoc/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.
- Licensing model: commercial-only
- Installation: Enable BYOC with Aiven, apply the provider-specific Terraform template, then provision Classic Kafka through the Aiven Console or CLI.
- Architecture: Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.
- Operations: Aiven manages provisioning and maintenance. The customer provides the cloud account, network configuration, IAM, quotas, and backup storage access.
- Product website: https://aiven.io/kafka
- Source review: 2026-11-21; cloud review: 2026-11-21; licensing review: 2026-11-21; infrastructure review: 2026-11-21

### Scope and qualifications

Classic Kafka uses fixed service plans. Diskless topics require enablement and an eligible custom cloud and plan. Aiven documents limited OCI access for its wider BYOC program. Confirm product and region eligibility. Metrics and logs reach Aiven, and controlled support access is documented. Agree how to migrate topics and remove delegated access before exit.

Commercial managed service. BYOC requires an Aiven commitment and Advanced or Premium support. Aiven and the cloud provider bill separately.

Persistent Kafka workload nodes run in the customer's custom cloud. In the documented private topology, the Aiven management plane connects through a bastion.


### Category fit

- streaming: Managed Apache Kafka brokers in the customer's cloud account, operated by Aiven.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud (checked 2026-11-21). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud (checked 2026-11-21). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud (checked 2026-11-21). 

Operating responsibility: Aiven operates and maintains Kafka in the customer's custom cloud. Its separate management plane provisions and monitors the service through delegated access; the customer supplies cloud-account, network and policy prerequisites. Source: https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc (checked 2026-11-21). Supporting source: BYOC networking and control plane — https://aiven.io/docs/platform/howto/byoc/networking-security.


### Cloud deployment evidence

- Aiven custom cloud on AWS (aws): https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud
  The customer applies a Terraform template in its AWS account and grants Aiven permissions through an IAM role.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Aiven custom cloud on Azure (azure): https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud
  The customer sets up an Azure custom cloud in its subscription before provisioning Kafka.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.

- Aiven custom cloud on Google Cloud (gcp): https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud
  The customer sets up a Google Cloud custom cloud in its project before provisioning Kafka.
  Source type: vendor-documentation; reviewed: 2026-11-21; vendor support: not-assessed.


### Sources

- Kafka BYOC provisioning: https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc

- Private networking and vendor access: https://aiven.io/docs/platform/howto/byoc/networking-security

- BYOC eligibility and billing: https://aiven.io/docs/platform/concepts/byoc

- Shared responsibility matrix: https://aiven.io/responsibility-matrix

- Aiven custom cloud on AWS: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud

- Aiven custom cloud on Azure: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud

- Aiven custom cloud on Google Cloud: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud

### Licensing sources

- https://aiven.io/docs/platform/concepts/byoc

### Infrastructure sources

- https://aiven.io/docs/platform/howto/byoc/networking-security


### Buyer diligence


Research coverage: 4/12 fields (33%); 3 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Organization administrators can configure a SAML identity provider and verified domains for Aiven Console users. BYOC Kafka is provisioned through that same Aiven organization and Console. This authenticates the vendor-hosted management plane; Kafka client authentication is a separate configuration. Scope: Aiven organization / Console identity for the managed BYOC service, not Kafka protocol clients.. Source: https://aiven.io/docs/platform/howto/saml/add-identity-providers (reviewed 2026-11-21). Supporting source: Kafka BYOC Console prerequisites — https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. After BYOC approval, Aiven generates a customer-specific Terraform template in Console or CLI. The customer downloads and applies it to prepare the cloud account and delegated access, then provisions Kafka in the custom cloud. This is account-specific managed-service onboarding, not a public standalone self-managed Kafka installer. Scope: AWS custom-cloud Terraform onboarding; obtain and review the generated template and permissions.. Source: https://aiven.io/docs/platform/howto/byoc/create-cloud/create-aws-custom-cloud (reviewed 2026-11-21). Supporting source: Google Cloud generated Terraform onboarding — https://aiven.io/docs/platform/howto/byoc/create-cloud/create-google-custom-cloud. Supporting source: Azure custom-cloud onboarding — https://aiven.io/docs/platform/howto/byoc/create-cloud/create-azure-custom-cloud.

- Minimum footprint / sizing: Sources checked — unresolved. The Kafka BYOC guide requires a fixed Classic Kafka plan and gives business-4 as a CLI example, but does not establish a quantitative minimum topology for the customer's provider, region and workload. Diskless topics have separate eligible plans and can add a PostgreSQL service. Obtain broker counts, instance resources, storage and availability-zone design from Aiven; the example plan name is not a sizing guarantee. Scope: Managed Kafka BYOC sizing unresolved; do not substitute Aiven-hosted Free/Developer plans.. Source: https://aiven.io/docs/products/kafka/get-started/create-kafka-service-byoc (reviewed 2026-11-21).

- License pricing: Documented. BYOC is a bespoke commercial managed service requiring an Aiven commitment and Advanced or Premium support. Pricing depends on the agreement. Aiven bills managed-service fees separately from the customer's cloud infrastructure and network traffic; standard all-inclusive Aiven Cloud rates do not establish BYOC charges. Scope: Commercial Kafka BYOC eligibility and separate billing; request the supported plan and a quote.. Source: https://aiven.io/docs/platform/concepts/byoc (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.







## Apache Pulsar

Distributed publish-subscribe messaging and streaming platform for persistent event workloads.

- Listing: https://launchinyourcloud.com/directory/apache-pulsar/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: Apache License 2.0 for upstream Apache Pulsar.
- Licensing model: open-source
- Installation: Use the official Helm chart on a customer-operated Kubernetes cluster; standalone Docker is documented for development and evaluation.
- Architecture: Customer-operated brokers, BookKeeper storage and required metadata services
- Operations: Customer manages brokers, bookies, metadata, durable volumes, retention, access controls and upgrades.
- Product website: https://pulsar.apache.org/
- Source review: 2026-11-12; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

The cited 4.2 deployment guide belongs to a maintained release line. Match chart and service versions; standalone mode is not equivalent to a resilient production cluster. Connectors and remote sinks have separate boundaries.

Apache License 2.0 for upstream Apache Pulsar. This classification covers the reviewed upstream edition; external services and dependencies retain their own terms.

Customer-operated brokers, BookKeeper storage and required metadata services. This is a customer-operated server/container deployment; portability does not establish named cloud-provider support.


### Category fit

- streaming: Distributed messaging and streaming with persistent topics and separately scalable serving and storage components.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://pulsar.apache.org/docs/4.2.x/deploy-aws/ (checked 2026-11-12). 


### Cloud deployment evidence

- Apache Pulsar 4.2 deployment on AWS (aws): https://pulsar.apache.org/docs/4.2.x/deploy-aws/
  The upstream 4.2 guide provisions EC2 instances and networking with Terraform, then installs Pulsar with Ansible in the customer AWS account. Review the selected release, instance types, persistence and network access before using the example.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Community and maintenance

Apache-governed project with a long public release history; the official release index records 5.0.0 and 5.0.1 plus maintenance of 4.2 in October 2026.

Reviewed 2026-11-10.

- Release history and managers: https://pulsar.apache.org/release-notes/

- Apache project and community: https://pulsar.apache.org/powered-by/

### Sources

- Official installation and runtime: https://pulsar.apache.org/docs/4.2.x/deploy-kubernetes/

- Upstream project and capabilities: https://github.com/apache/pulsar

- Current upstream license: https://github.com/apache/pulsar/blob/master/LICENSE

- Standalone Docker evaluation: https://pulsar.apache.org/docs/4.2.x/getting-started-docker/

### Licensing sources

- https://github.com/apache/pulsar/blob/master/LICENSE

### Infrastructure sources

- https://pulsar.apache.org/docs/4.2.x/deploy-kubernetes/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Sources checked — unresolved. Pulsar 5.0 documents OIDC bearer-token authentication for clients, principals and roles used by broker/admin operations. This is not evidence of a maintained browser-console login integration. Select the actual administrative UI and its compatible identity integration before treating user SSO as confirmed. Scope: Apache Pulsar 5.0 core client identity; browser/user-console federation remains unconfirmed. Source: https://pulsar.apache.org/docs/5.0.x/security-openid-connect/ (reviewed 2026-11-21).

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. The Apache-maintained Helm chart includes the Pulsar service components. The deployment guide separates non-production quickstart from production preparation, storage and sustained-load configuration. Scope: Pulsar 4.2.x deployment guide; select a chart matching the deployed application version. Source: https://pulsar.apache.org/docs/4.2.x/deploy-kubernetes/ (reviewed 2026-11-14). Deployment artifact: https://github.com/apache/pulsar-helm-chart. Artifact reference: repository default branch (moving; select matching application release).

- Minimum footprint / sizing: Documented. The reviewed upstream Helm values request 256 MiB/0.1 CPU per ZooKeeper pod (three replicas) and 512 MiB/0.2 CPU per BookKeeper pod (four replicas). These active scheduling requests cover only two components, not their actual capacity or the complete broker/proxy/storage/monitoring cluster. The moving chart identifies appVersion 5.0.1; pin and tune a compatible release for workload, replication and HA. Scope: Moving upstream Helm chart component defaults reviewed on this date; not a complete minimum, benchmark or replacement for the separately retained 4.2.x deployment guide. Source: https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/values.yaml (reviewed 2026-11-21). Supporting source: Chart appVersion metadata — https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/Chart.yaml. Supporting source: BookKeeper request template — https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/bookkeeper-statefulset.yaml. Supporting source: ZooKeeper request template — https://github.com/apache/pulsar-helm-chart/blob/master/charts/pulsar/templates/zookeeper-statefulset.yaml.

- License pricing: Documented. The upstream v5.0.1 core is Apache-2.0 licensed, with bundled third-party notices and components governed by their own terms. Hosted Pulsar services and vendor support are separate commercial offerings. Scope: Versioned Apache Pulsar core; no managed-service or enterprise-support entitlement inferred. Source: https://github.com/apache/pulsar/blob/v5.0.1/LICENSE (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The publisher-designated GitHub release checked was v5.0.1, published 2026-10-26. This is a release snapshot, not a promised cadence, support designation or approval to substitute it into a provider package. Scope: Upstream apache/pulsar release record; commercial editions and deployment packages may differ. Source: https://github.com/apache/pulsar/releases/tag/v5.0.1 (reviewed 2026-11-14).







## Cloudera on Cloud

Cloudera-managed control plane that provisions data, analytics and AI workload services into a customer's public-cloud account.

- Listing: https://launchinyourcloud.com/directory/cloudera-on-cloud/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Shared operations · vendor control plane
- Infrastructure IDs: servers
- License: Commercial Cloudera subscription with cloud infrastructure charges paid separately.
- Licensing model: commercial-only
- Installation: Register the customer cloud environment and credentials, then provision Cloudera workload services through the control plane
- Architecture: Vendor-operated control plane with data, compute, networking and workload environments in the customer's cloud account.
- Operations: Cloudera operates the service control plane; the customer owns cloud resources, credentials, data governance, network integration, workload sizing and shared operational responsibilities.
- Product website: https://www.cloudera.com/products/cloudera-cloud.html
- Source review: 2026-11-18; cloud review: 2026-11-17; licensing review: 2026-11-17; infrastructure review: 2026-11-17

### Scope and qualifications

This entry covers Cloudera's public-cloud BYOC service, not a fully customer-operated software distribution. Workloads and data run in the customer's AWS, Azure or Google Cloud environment while Cloudera operates the control plane. Service availability and implementation details differ by provider, especially on Google Cloud, so confirm each required service before procurement. Cloudera November bulletins cover critical Brotli CVE-2026-111497 and compromised eMudhra certificates. Use the TSB matrices for the exact Runtime or Private Cloud Base component and fixed build rather than applying a generic platform version.

Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate.

The customer account contains persistent data and compute services while Cloudera operates an external control plane. Runtime topology varies by selected workload service.


### Category fit

- data-analytics: Managed data engineering, warehousing and analytics services operate over data in customer cloud environments.

- streaming: Cloudera provides streaming ingestion and processing services where supported by the selected cloud deployment.

- ai-tools: Machine-learning and AI workload services are available within the Cloudera platform, subject to provider and subscription availability.

### Deployment boundaries


- aws: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

- azure: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

- gcp: Customer cloud account; Shared operations; control plane: vendor-hosted. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (checked 2026-11-17). 

Operating responsibility: Cloudera operates the control plane while workloads run in the customer's cloud accounts. Customer responsibilities include credentials, account policies, workload configuration and data governance; confirm each selected service's responsibility split. Source: https://www.cloudera.com/products/trust-center/shared-responsibility-model.html (checked 2026-11-20).


### Cloud deployment evidence

- Cloudera workloads in customer AWS, Azure and Google Cloud environments (aws, azure, gcp): https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html
  Cloudera documents registering customer AWS, Azure and Google Cloud environments and credentials so its control plane can provision workload resources. Provider service availability differs and must be checked for the selected workload.
  Source type: vendor-documentation; reviewed: 2026-11-17; vendor support: not-assessed.


### Sources

- Cloudera public-cloud architecture and ownership: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html

- Cloud prerequisites and credential setup: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html

- Cloudera workload services: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html

- Cloudera pricing: https://www.cloudera.com/products/pricing.html

- Cloudera TSB-2026-1007: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html

- Cloudera TSB-2026-1009: https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html

### Licensing sources

- https://www.cloudera.com/products/pricing.html

### Infrastructure sources

- https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-public-cloud.html

- https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html


### Buyer diligence


Research coverage: 12/12 fields (100%); 5 documented, 7 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The Google partnership page still labels Marketplace deployment coming soon. A current offer for the selected workload service and provider was not established from these sources. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://www.cloudera.com/partners/solutions/google-cloud-platform.html (reviewed 2026-11-17).

- Cloud commitment eligibility: Sources checked — unresolved. Platform pricing and cloud cost-optimization guidance do not establish which software fees qualify for a buyer’s committed-spend agreement. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://www.cloudera.com/products/pricing.html (reviewed 2026-11-17).

- Single sign-on: Documented. Management Console supports federation using enterprise SAML IdP metadata. Identity-provider creation is privileged; duplicate group names across IdPs can grant unintended memberships. Scope: Cloudera-managed control plane for customer-cloud workloads. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-setting-up-the-identity-provider-in-cdp.html (reviewed 2026-11-17).

- SCIM provisioning: Documented. Cloudera documents SCIM with Entra ID alongside SAML federation. Only one SCIM IdP per account is supported; userName and group-name changes are unsupported, so choose stable identifiers. Scope: Cloudera account provisioning, not a self-hosted SCIM server. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-configuring_scim_with_azure_ad.html (reviewed 2026-11-17).

- Compliance attestations: Sources checked — unresolved. The reviewed Cloudera on Cloud material establishes configuration/operating controls, but not an independent current attestation covering this edition and customer deployment. Obtain the actual report/certificate, audit period and scope before claiming coverage. Scope: Customer deployment attestation; vendor SaaS, cloud-provider and component certifications are not automatically inherited. Source: https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html (reviewed 2026-11-17).

- Security controls: Documented. The user-management guidance warns about mutable identity keys and concurrent SAML/SCIM group synchronization. Align stable NameID/userName values and review privileged account/group mappings. Current advisory review: Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Apply the exact fixed component build and review affected certificate trust. Scope: Management Console identity synchronization and permissions Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009.. Source: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html (reviewed 2026-11-18). Supporting source: Prior security-controls source — https://docs.cloudera.com/management-console/cloud/user-management/topics/mc-known_issues_and_troubleshooting_related_to_idp_setup_in_cdp.html. Supporting source: TSB-2026-1009 — https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html.

- Air-gapped operation: Sources checked — unresolved. This listing uses an external vendor control plane. The reviewed public-cloud setup does not establish complete isolated operation; Cloudera Private Cloud documentation is a different offering. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (reviewed 2026-11-17).

- Deployment artifact / IaC: Documented. Customer-cloud setup requires cloud account credentials, network prerequisites and an environment registration before Cloudera provisions workloads. The vendor control plane remains external to the customer account. Scope: Cloudera public-cloud environment setup; services differ by provider. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/getting-started/topics/cdp-set_up_cloud_prerequisites.html (reviewed 2026-11-17).

- Minimum footprint / sizing: Sources checked — unresolved. The platform offers multiple workload services with different node, storage and database needs. The overview does not establish one minimum HA footprint for 100 users/1 TB; select the actual services and workload configuration. Scope: Cloudera on cloud workload-specific sizing. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).

- License pricing: Documented. Cloudera on Cloud is a commercial subscription service. Customer cloud-resource charges and Cloudera software/service consumption are separate. Scope: Cloudera on Cloud: software entitlement and edition boundary; infrastructure and operating costs are separate. Source: https://www.cloudera.com/products/pricing.html (reviewed 2026-11-17).

- Operating cost estimate: Sources checked — unresolved. Select workload services, Data Lake/runtime topology, data scans/compute-hours and provider-specific service availability. Vendor fees and customer-cloud resources are billed separately. A complete monthly operating estimate is not established. Scope: Requested planning scenario: AWS us-east-1, 100 internal users, 1 TB data, HA, average usage; missing workload metrics and commercial terms are explicit. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).

- Release snapshot / cadence: Sources checked — unresolved. Management Console and customer-cloud workload services have independent release/runtime lines. A single platform latest-version number or universal upgrade schedule was not established. Scope: Reviewed public evidence for Cloudera on Cloud; unresolved within this edition/deployment. Source: https://docs.cloudera.com/cdp-public-cloud/cloud/overview/topics/cdp-services.html (reviewed 2026-11-17).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Cloudera November 2026 Brotli and certificate bulletins (security-advisory): Cloudera TSBs address critical Brotli CVE-2026-111497 and compromised eMudhra certificates in specified CDP components. Scope: Affected and fixed versions vary by Runtime and Private Cloud Base component; consult TSB-2026-1007 and TSB-2026-1009. Conditions: Bundled Brotli and certificate trust stores determine exposure. Action: Apply the exact fixed component build and review affected certificate trust. Source: https://docs.cloudera.com/cdp-private-cloud-base/7.3.3/private-release-notes/topics/tsb-2026-1007.html; reviewed 2026-11-18. Supporting source: TSB-2026-1009 — https://docs.cloudera.com/runtime/7.3.3/public-release-notes/topics/tsb-2026-1009.html.




## Confluent Platform Self-Managed

Self-managed event streaming platform deployed to customer-operated Kubernetes with Confluent for Kubernetes.

- Listing: https://launchinyourcloud.com/directory/confluent-platform-self-managed/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated
- Infrastructure IDs: servers
- License: A commercial Confluent subscription is required for Confluent Platform components deployed with CFK; component licenses otherwise vary.
- Licensing model: commercial-only
- Installation: Install the Confluent for Kubernetes operator with Helm, then deploy Confluent Platform components through Kubernetes custom resources.
- Architecture: CFK operator managing persistent Kafka, KRaft, Schema Registry, Connect, ksqlDB and other selected Confluent Platform services in a customer Kubernetes cluster
- Operations: Customer manages Kubernetes clusters, node pools, persistent storage, load balancers, DNS and routing, identity and RBAC, secrets, backups, scaling and upgrades; CFK reconciles the declared Confluent application resources.
- Product website: https://www.confluent.io/product/confluent-platform/
- Source review: 2026-11-19; cloud review: 2026-11-16; licensing review: 2026-11-16; infrastructure review: 2026-11-16

### Scope and qualifications

This entry covers self-managed Confluent Platform deployed with Confluent for Kubernetes, not Confluent Cloud. Current CFK guidance explicitly addresses Amazon EKS, Azure Kubernetes Service and Google Kubernetes Engine. Provider examples do not certify every Kubernetes, Confluent Platform or topology combination; use the current supported-environments matrix and validate cross-cluster networking, storage, security, version compatibility and subscription terms. Confluent's November 2026 security releases address multiple broker, Kafka Connect, ZooKeeper, TLS trust, JWT, file-read, and denial-of-service issues. Upgrade to the latest patched release for the deployed branch: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3, or 8.4.1. Until patched, deployments using a separate Kafka Connect administrative listener should remove admin.listeners; the ZooKeeper fix applies to the affected 7.x lines identified by Confluent. CONFSA-2026-37 covers CVE-2026-114938 in Confluent Platform 7.6.x–8.4.x and Control Center 2.0.x–2.7.x when package/archive installs use affected customer JDKs, plus specified Docker-image ranges. Fixed-runtime releases were still being prepared at review time. Apply -XX:-UseBASE64Intrinsics to every affected Java process, restart and verify the flag until the applicable fixed image or runtime is available.

This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering.

CFK deploys long-running stateful brokers, controllers and supporting services on customer Kubernetes worker nodes with persistent storage. Using a managed Kubernetes control plane does not make the Confluent Platform application runtime serverless.


### Category fit

- streaming: Runs Apache Kafka brokers together with schema, connector and stream-processing services for customer-operated event streaming.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 

- azure: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 

- gcp: Customer cloud account; Customer-operated; control plane: not-assessed. Source: https://docs.confluent.io/operator/current/co-multi-region.html (checked 2026-11-16). 


### Cloud deployment evidence

- Confluent for Kubernetes guidance for EKS, AKS and GKE (aws, azure, gcp): https://docs.confluent.io/operator/current/co-multi-region.html
  The current CFK multi-region guide explicitly identifies Google Kubernetes Engine, Amazon Elastic Kubernetes Service and Azure Kubernetes Service for provider-specific configuration and validation. The CFK overview defines the product as managing self-managed Confluent Platform in the customer's own Kubernetes environment. This evidence does not include the separately operated Confluent Cloud service.
  Source type: vendor-documentation; reviewed: 2026-11-16; vendor support: not-assessed.


### Sources

- Confluent for Kubernetes overview: https://docs.confluent.io/operator/current/overview.html

- Deploy Confluent for Kubernetes: https://docs.confluent.io/operator/current/co-deploy-operator.html

- Supported environments and versions: https://docs.confluent.io/operator/current/co-supported-environments.html

- CFK multi-region deployment guidance: https://docs.confluent.io/operator/current/co-multi-region.html

- Confluent Platform licensing: https://docs.confluent.io/platform/current/installation/license.html

- Confluent November 2026 security advisories and patched releases: https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes

- Confluent compromised CA trust advisory: https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates

- Confluent Kafka Connect administrative-listener advisory: https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API

- CONFSA-2026-37 Java4Shell advisory: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell

### Licensing sources

- https://docs.confluent.io/platform/current/installation/license.html

### Infrastructure sources

- https://docs.confluent.io/operator/current/overview.html

- https://docs.confluent.io/operator/current/co-supported-environments.html

- https://docs.confluent.io/operator/current/co-deploy-operator.html


### Buyer diligence


Research coverage: 8/12 fields (67%); 6 documented, 2 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Not researched.

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Control Center supports OIDC SSO and automated configuration through CFK. The guide says IdP refresh-token rotation must be disabled for this integration. This is self-managed Control Center authentication, distinct from Confluent Cloud SAML. Scope: Confluent Platform Control Center OIDC; requires the relevant licensed components. Source: https://docs.confluent.io/platform/current/security/authentication/sso-for-c3/overview.html (reviewed 2026-11-16).

- SCIM provisioning: Not researched.

- Compliance attestations: Sources checked — unresolved. The Platform guide says Confluent’s annual SOC 2 report is available on request. It does not supply the current report period or customer-environment scope; its separate FIPS configuration guidance must not be treated as a whole-deployment attestation. Scope: Vendor security-controls report availability and deployment configuration; actual attestation scope unresolved. Source: https://docs.confluent.io/platform/current/security/compliance/overview.html (reviewed 2026-11-16).

- Security controls: Documented. CFK telemetry is disabled by default; enabling Health+ sends service metadata to Confluent. The built-in JMX Prometheus exporter lacks authentication/encryption and cannot be disabled through CFK, so restrict access at the network boundary and configure other security surfaces separately. Current review: CONFSA-2026-37 covers CVE-2026-114938 in package/archive installs using affected customer JDKs and in the advisory's Platform, Control Center, CMF, Flink, operator, Gateway and CFK init-container image ranges. Fixed-runtime releases were still in preparation. Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed. Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact Docker-image ranges in CONFSA-2026-37. Source: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell (reviewed 2026-11-19). Supporting source: Prior security-controls source — https://docs.confluent.io/operator/current/co-monitor-cp.html.

- Air-gapped operation: Sources checked — unresolved. CFK documents copying the required tagged Platform/operator/init-container images into a private registry and configuring pulls from it. This establishes private image delivery, but the reviewed guide does not establish end-to-end offline licensing, dependencies or updates for the selected stack. Scope: CFK private-registry installation mechanics; full disconnected operation remains unresolved. Source: https://docs.confluent.io/operator/current/co-custom-registry.html (reviewed 2026-11-16).

- Deployment artifact / IaC: Documented. The CFK guide installs confluent-for-kubernetes from Confluent’s Helm repository, then manages Platform components through custom resources. The repository index moves; select a CFK/chart release compatible with the Platform components and Kubernetes version. Scope: Confluent for Kubernetes deployment; commercial subscription applies. Source: https://docs.confluent.io/operator/current/co-deploy-operator.html (reviewed 2026-11-16). Deployment artifact: https://packages.confluent.io/helm/index.yaml. Artifact reference: moving Helm repository index; select compatible chart version.

- Minimum footprint / sizing: Documented. The current CFK guide starts with three Kafka brokers and three KRaft controllers. Each broker’s minimum is 4 CPUs, 16 GB RAM and 1 TB disk; the production column is larger. Controllers and other components add resources. Scope: CFK minimum cluster planning; not aggregate production sizing or pre-8.0 ZooKeeper guidance. Source: https://docs.confluent.io/operator/current/co-plan-sizing.html (reviewed 2026-11-16).

- License pricing: Documented. This entry specifically covers deployment through Confluent for Kubernetes. Confluent states that deploying with CFK requires a subscription and applies licensing requirements to every Confluent Platform component in that cluster. Some components can use Apache 2.0 or Confluent Community licenses outside this CFK path, but that does not make the selected CFK deployment an open-source offering. Scope: Confluent Platform Self-Managed: software license terms; infrastructure and operating costs are separate. Source: https://docs.confluent.io/platform/current/installation/license.html (reviewed 2026-11-16).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Documented. The reviewed compatibility matrix dates CFK 3.4.x to 2026-10-28, with standard support through 2028-10-28. It supports Platform 7.6.x–8.4.x and lists separate Control Center and Kubernetes ranges. The operator, init container and Platform have distinct versions; do not use a Platform patch number as the chart/operator version. Scope: CFK 3.4 release-line/support and component compatibility; not a claim about the newest Platform patch. Source: https://docs.confluent.io/operator/current/co-supported-environments.html (reviewed 2026-11-16).




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Confluent Platform November security patches (security-advisory): Vendor advisories cover broker/Connect, CA trust, JWT, ZooKeeper and denial-of-service issues; component conditions vary. Scope: Confluent Platform fixes: 7.6.15, 7.7.13, 7.8.12, 7.9.11, 8.0.9, 8.1.7, 8.2.5, 8.3.3 or 8.4.1, as applicable to each advisory. CFK/operator versions are separate. Conditions: Kafka Connect admin.listeners creates a separate affected administrative surface. ZooKeeper fixes apply only to the vendor-identified 7.x lines; do not transfer these claims to Confluent Cloud. Action: Use each advisory to choose the patched branch and compatible CFK/components. Until patched, remove the separate Connect admin.listeners setting. Source: https://support.confluent.io/hc/en-us/sections/360008413952-Security-Advisories-and-Security-Release-Notes; reviewed 2026-11-17. Supporting source: Compromised CA trust remediation — https://support.confluent.io/hc/en-us/articles/55611336006292-CONFSA-2026-33-CVE-2026-114820-CVE-2026-114406-Confluent-Platform-Compromised-eMudhra-Certificate-Authority-Roots-and-intermediates. Supporting source: Connect administrative listener mitigation — https://support.confluent.io/hc/en-us/articles/55610452168340-CONFSA-2026-27-CVE-2026-115644-Confluent-Platform-Missing-Access-Control-Unauthenticated-Access-to-Kafka-Connect-Logging-API.

- Confluent CONFSA-2026-37 Java4Shell guidance (security-advisory): CONFSA-2026-37 covers CVE-2026-114938 in customer-JDK installs and multiple Confluent Docker-image ranges. Scope: Confluent Platform 7.6.x–8.4.x, Control Center 2.0.x–2.7.x and the exact additional image ranges in the advisory. Conditions: Package/archive installs inherit the customer JDK; Docker applicability depends on the image and tag. Action: Apply -XX:-UseBASE64Intrinsics, restart and verify every affected Java process until a fixed vendor image or JDK is deployed. Source: https://support.confluent.io/hc/en-us/articles/55810725278740-CONFSA-2026-37-CVE-2026-114938-Confluent-Cloud-and-Confluent-Platform-OpenJDK-vulnerability-Java4Shell; reviewed 2026-11-19.




## Redpanda BYOC

Managed Kafka-compatible streaming in your cloud account.

- Listing: https://launchinyourcloud.com/directory/redpanda/
- Publisher listing: No
- Entry kind: platform
- Documented cloud IDs: aws, azure, gcp
- Operating model: Vendor-operated BYOC
- Infrastructure IDs: servers
- License: Commercial
- Licensing model: commercial-only
- Installation: Redpanda Cloud BYOC provisioning
- Architecture: Vendor-managed cluster in customer network
- Operations: Redpanda manages provisioning, monitoring and upgrades with the permissions you grant.
- Product website: https://www.redpanda.com/
- Source review: 2026-11-18; cloud review: 2026-11-12; licensing review: 2026-11-10; infrastructure review: 2026-11-10

### Scope and qualifications

BYOC supports AWS and Google Cloud VPCs and Azure VNets. BYOVPC/BYOVNet lets the customer provision networking first. Review agent permissions and emergency support access. Redpanda Cloud's November update adds Load Factor dashboard metrics for BYOC deployments on version 26.2 or later. Treat the October BYOVNet, self-service scaling, and Azure tier announcements as separate earlier changes when planning upgrades.

This listing covers the commercially provided managed/BYOC service, not a separately licensed open-source engine or library.

BYOC uses a customer-cloud cluster and Kubernetes infrastructure. Redpanda’s separately hosted Serverless service is outside this listing.


### Category fit

- streaming: Managed Kafka-compatible streaming in your cloud account.

### Deployment boundaries


- aws: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

- azure: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

- gcp: Customer cloud account; Vendor / partner-operated; control plane: vendor-hosted. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-12). 

Operating responsibility: Redpanda provisions, monitors and upgrades the cluster using delegated access to the customer cloud account. Customer-managed networking is a separate BYOVPC/BYOVNet option. Source: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/ (checked 2026-11-20). Supporting source: BYOC managed control plane and customer data plane — https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/.


### Cloud deployment evidence

- Redpanda BYOC supported infrastructure (aws, azure, gcp): https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/
  Redpanda explicitly documents BYOC clusters in the customer AWS or Google Cloud VPC or Azure VNet, with a Redpanda-operated control plane. The architecture and provisioning requirements differ by provider; this is the BYOC offering, not Dedicated clusters in the vendor account.
  Source type: vendor-documentation; reviewed: 2026-11-12; vendor support: not-assessed.


### Sources

- BYOC deployment options: https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/

- BYOC cluster and Kubernetes architecture: https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/

- Redpanda Cloud what's new: https://docs.redpanda.com/cloud-data-platform/get-started/whats-new-cloud/

### Licensing sources

- https://docs.redpanda.com/cloud-data-platform/get-started/cluster-types/byoc/

### Infrastructure sources

- https://docs.redpanda.com/cloud-data-platform/get-started/byoc-arch/


### Buyer diligence


Research coverage: 5/12 fields (42%); 4 documented, 1 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Edition-dependent. Redpanda documents an AWS Marketplace private-offer subscription workflow and links it to BYOC cluster creation. Confirm that the order is for the intended BYOC deployment, not a vendor-account cluster. Scope: Redpanda Cloud marketplace subscription and BYOC path; selected offer terms apply. Source: https://docs.redpanda.com/cloud-data-platform/billing/aws-commit/ (reviewed 2026-11-14).

- Cloud commitment eligibility: Not researched.

- Single sign-on: Documented. Redpanda Cloud documents organisation user login through an OIDC-compliant identity provider with discovery. An organisation administrator configures and enables the connection, with optional enrolment and group-based permissions. The BYOC pricing page includes OIDC SSO in that service. Scope: Vendor-operated Cloud control-plane user SSO for a BYOC organisation; data-plane broker/client authentication is separate. Source: https://docs.redpanda.com/cloud-data-platform/security/cloud-authentication/ (reviewed 2026-11-21). Supporting source: BYOC service identity features — https://www.redpanda.com/pricing.

- SCIM provisioning: Not researched.

- Compliance attestations: Not researched.

- Security controls: Not researched.

- Air-gapped operation: Not researched.

- Deployment artifact / IaC: Documented. Redpanda documents a Cloud Terraform provider for networks, clusters and data-plane resources, with separate BYOVPC modules for AWS/GCP and a BYOVNet module for Azure. Select the BYOC cluster type, customer-managed resource configuration and throughput tier, pin provider/module versions and review replacement behavior. The provider automates the managed Cloud service, not installation of self-managed Community brokers. Scope: Redpanda Cloud BYOC control-plane automation and customer-cloud data plane; not self-managed Redpanda core Helm delivery. Source: https://docs.redpanda.com/cloud-data-platform/manage/terraform-provider/ (reviewed 2026-11-21). Deployment artifact: https://registry.terraform.io/providers/redpanda-data/redpanda/latest/docs. Artifact reference: Current Cloud provider documentation; pin the selected provider/module versions.

- Minimum footprint / sizing: Sources checked — unresolved. The BYOC tier reference maps throughput tiers to cloud machine types and directs buyers to a sizing calculator for broker count, machine type and RPU rate. Its connection examples are not a universal cluster minimum. A production configuration for 100 users/1 TB/HA still needs ingress/egress rate, partitions, retention, connections and recovery targets. Scope: Redpanda Cloud BYOC workload-based sizing; no complete reference-workload machine configuration verified. Source: https://docs.redpanda.com/cloud-data-platform/reference/tiers/byoc-tiers/ (reviewed 2026-11-21).

- License pricing: Documented. The vendor distinguishes Redpanda Cloud BYOC as a fully managed commercial service with an annual commitment and a sales-led trial/quote. Its customer-cloud infrastructure and agreed service charges require separate assessment; self-managed Community or Enterprise software terms are different offerings. Scope: Redpanda Cloud BYOC service pricing model; no Community licence or hosted Serverless price applied to BYOC. Source: https://www.redpanda.com/pricing (reviewed 2026-11-21).

- Operating cost estimate: Not researched.

- Release snapshot / cadence: Not researched.






