Cloud release notes

• RBAC is now available for Public Preview with predefined roles. Learn more. The supported roles are:
  • Org Admin (org-admin)
  • Org Read Only (org-readonly)
  • Tenant Admin (tenant-admin)
  • Tenant Read Only (tenant-readonly)
  • Topic Producer (topic-producer)
  • Topic Consumer (topic-consumer)
• Kafka Connect is now supported on Ursa Engine clusters. Try out the Kafka Connect connector with Ursa Engine Clusters.
• Self-service BYOC improvements
  • Bring Your Own Network and Bring Your Own DNS are now available on Azure, following the launch on AWS and GCP.

• Self-service BYOC improvements We have made several improvements to the self-service BYOC experience:
  • Self-service BYOC provisioning on Azure
    • You can now provision a BYOC cluster on Azure through the StreamNative Cloud Console. Learn more.
  • Bring Your Own Network [BYOC Pro Feature]
    • You can now use your own Virtual Private Cloud (VPC) when creating a BYOC Pro cluster. Learn more.
  • Bring Your Own DNS [BYOC Pro Feature]
    • You can now use your own DNS service when creating a BYOC Pro cluster. Learn more.
• Serverless available on AWS & Azure: We have expanded the Serverless offering to include AWS and Azure. Get started in seconds with Serverless clusters. Learn more.
• Azure Marketplace Launch: StreamNative Cloud is now available on Azure Marketplace, supporting Serverless, Dedicated, and BYOC deployment options through annual or pay-as-you-go subscriptions.
• RBAC support on Metrics API: Metrics API supports scraping metrics data from a normal service account with metrics-viewer role. Learn more about RBAC.
• Build-in Grafana Dashboard: You can now quickly set up Grafana dashboard and alert rules using our templates. Learn more.

​

What’s New

• Revamped Cloud Console: We continue to enhance the StreamNative Cloud Console, aligning additional pages with the new streamlined navigation to improve usability. Updates include:
  • Namespace Configuration pages
  • Organization List page
  • Users management pages
  • Function pages
  • pfSQL pages
  • Cloud Environment pages
• Name length limit enforcement: To ensure seamless resource management and avoid issues with excessively long names, we have introduced character limits for instance and cluster names:
  • Instance names: Maximum of 40 characters
  • Cluster names: Maximum of 10 characters
• Improved Log Console: Logging is essential for debugging and monitoring connectors and functions. The log console has been redesigned to enhance user experience. Key improvements include:
  • Viewing logs in an intuitive interface
  • Advanced filtering options
  • Search functionality for quick log analysis
  Explore the updated log console for a more efficient debugging and monitoring workflow!

​

What’s New

• Ursa Engine
  • Ursa Engine is now available in Public Preview for AWS BYOC clusters. Learn more.
• Geo Replication
  • StreamNative instance supports creating multiple Pulsar clusters and Pulsar clusters within the same StreamNative instance will now share the configuration store and built-in support geo-replication. Learn more.

​

What’s New

• Kafka Connect Support
  • StreamNative Cloud now supports the ability to upload and run a Kafka Connect based connector. Learn more.
• Serverless Cluster
  • StreamNative now supports a new type of deployment called Serverless that enables users to get started in seconds. Learn more. Read our announcement here.

​

What’s New

• Revamped Cloud Console Navigation: Our updated navigation is designed to make managing your resources easier and more efficient. The new interface dynamically displays menus and contextual actions relevant to each level of your information architecture. As you navigate from Instance to Cluster, and then to Tenant and Namespace, the relevant resources at each level will be prominently highlighted, allowing you to focus on what’s most important at every stage. To help you get familiar with the new navigation, we’ve created a short video tour that walks you through the updates. You can watch it here.
• GCP and Azure Support:
  • Both GCP and Azure now support Cloud Environment and Cloud Connection via the UI . Learn more)

​

Other Updates

• Improvements
  • Security:
    • Optimized TLS Performance by reducing unnecessary buffer copies, significantly improving performance of encrypted communications.
    • AES-GCM Cipher Optimizations: Enhanced the performance of the AES-GCM cipher for TLS encryption, resulting in faster data encryption and decryption.
  • Improved Bundle Ownership Notifications : More accurate and timely notifications during the load management process ensure smoother transitions and balanced workloads, enhancing scalability and reducing the risk of performance bottlenecks.
  • Pulsar Admin Connection Management: The new maxConnectionsPerHost and connectionMaxIdleSeconds settings give users more granular control over client connections, leading to better resource management and lower operational costs.
  • ServiceUrlProvider Failover Support: This new feature increases reliability and uptime by automatically failing over to secondary clusters in the event of an issue with the primary cluster, ensuring continuous availability.
  • Improved Topic Load Failure Metrics: Enhanced metrics provide better visibility into topic loading failures, allowing administrators to quickly identify and resolve issues, leading to improved uptime and system reliability. To see all bug fixes and improvements, go through our weekly change logs.

​

What’s New

• Redesigned Topic Page:
  • Detail Tub Improvements: We’ve restructured the detail tub to be more intuitive, making it easier for users to find the information they need quickly.
  • Optimize Schema Tub: The redesign of the schema tub focuses on improving the ease of managing schemas, ensuring a more user-friendly and visually appealing experience.
• Enhanced Organization Usage Page:
  • Tailored Time Window: The usage time window is now automatically aligned with your organization’s contractual periods, eliminating the need to manually select dates.
  • Quick Usage Snapshots: High-level doughnut charts provide an instant overview of your usage, offering key insights at a glance.
  • Enriched CSV Exports: Downloaded usage data now includes additional metadata, improving clarity and enabling more precise offline analysis.
  • Consistent Legends: Graph legends are standardized, making it easier to compare resource usage across different instances.
• Support JVM metrics on Source and Sink connector metrics endpoint:
  • You can find the newly added JVM metrics on Source Connector metrics.
  • You can find the newly added JVM metrics on Sink Connector metrics.

​

Other Updates

• Deprecate Service Account JWT token
  • Service Account deprecated the JWT token generation and replaced by the API Key.

​

What’s New

• Self-Service Console UI to setup Bring Your Own Cloud Infrastructure
  • Users can now leverage a self-service user experience within StreamNative Cloud to set up the infrastructure for the StreamNative Bring Your Own Cloud (BYOC) offering. This enhancement eliminates the need to file support tickets and wait for the StreamNative engineering team to set up the infrastructure, allowing users to create clusters more efficiently and independently. Learn more.
• JVM metrics are now supported on Function Metrics endpoint
  • You can find the newly added JVM metrics on this link within the Function metrics section.
• Lakehouse Storage Support for Delta Lake is now in Private Preview
  • Lakehouse Storage is part of the Ursa Engine, which seamlessly integrates with Pulsar brokers. It offers the capability to write streaming data to popular lakehouse products like Delta Lake and Apache Iceberg, while supporting open table formats. This feature enables both streaming and batch-read operations from the lakehouse, enhancing data accessibility and processing efficiency. Learn more at the links listed below.
    • LakeHouse Storage Support in StreamNative Managed Cloud
    • LakeHouse Storage Support in StreamNative Private Cloud
• Pinecone Connectors is now available in Private Preview
  • This connector allows access to pinecone.io with a pulsar topic. The sink connector takes in messages and writes them if they are in a proper format to a Pinecone index. Learn more

​

What’s New

• Paymentless Trial
  • We understand that you want to try our platform and do not want to go through corporate approvals to spin up a trial and evaluate our platform. Now, you no longer need a credit card to spin up for a trial to avail the $200 credit. You only need to enter a payment method once you have consumed the$200 credit.
• Function Auto-Scaling
  • Functions can now be configured to scale automatically. This allows you to build your streaming data pipelines without worrying about unforeseen spikes and reduce costs when the load reduces. All of this, with just a few settings. This feature is currently in Private Preview. We blogged about it a while back
• Cloud API Documentation
  • Watch our for our Cloud API documentation (currently in Private Preview). You will be able to get full details on using API’s to access resources like Clusters, Instances, API Keys, Users and Service Accounts. We can’t wait to see how you have used these API’s. Here is a sneak preview
• Cloud Resource Metrics
  • You now have access to metrics around Pulsar resources, functions, source and sink connectors so that you can get full insights into your streaming data infrastructure. You can find all the metrics endpoints here as well as integration with top Observability vendors.

​

What’s New

• Release Channel support
  • StreamNative Hosted and Bring Your Own Cloud managed launched the Release Channel as a Public Preview feature. Learn more.
• Broker Auto-Scaling support
  • StreamNative Hosted launched the Auto-Scaling as a Public Preview feature. Learn more.
• New observability dashboards
  • StreamNative Cloud Console added extra observability dashboards for Pulsar namespaces, Pulsar topics, Pulsar functions and Pulsar connectors.
• Terraform Provider for StreamNative
  • StreamNative Cloud launched the Terraform Provider for StreamNative to support manage StreamNative Cloud resources with the Terraform. Learn more.

​

What’s New

• StreamNative Support On Azure
  • StreamNative Hosted and Bring Your Own Cloud managed offerings are now supported on Microsoft Azure . Learn more .
• Datadog agent’s support for StreamNative Cloud Metrics
  • The updated Datadog agent allows users to pull metrics from StreamNative Cloud Metrics API with oauth2 authentication. Learn more.
• New connectors on StreamNative Cloud
  • Google Pub/Sub Source Connector
  • Google Pub/Sub Sink Connector
• New feature in BigQuery Sink connector
  • BigQuery Sink Connector is enhanced with protobuf-native support.
• Delete subscription from StreamNative Cloud
  • StreamNative Console now supports the ability to delete subscriptions.
• Improved console uptime
  • Now, users can access the console while the cluster environment is getting set up.```
• MOP Default on New Clusters
  • MQTT on Pulsar (MOP) is now available by default on new clusters. Learn more.
• Updated Breadcrumb
  • In order to ensure each user has access to the right resources, the breadcrumb has been updated to require users to select their cluster, tenant, and namespace when navigating around the StreamNative Console. Learn more.

​

What’s New

• ACH Payment Option
  • ACH is now accepted as a valid payment option on StreamNative Cloud. To use ACH, click the Billing & Payment button on the dashboard, and enter bank details within the Stripe portal.

​

Other Updates

• The Oxia Java client library has now been open-sourced, laying the groundwork for a direct integration between Oxia and in Pulsar 3.3, which will allow Pulsar to scale beyond one million topics. See the announcement blog for more details.

​

Bug Fixes

• Fixed a bug in graph display logic on the Organization Usage page that would cause usage to appear as if it dropped to zero if there are gaps in the data returned from Prometheus.

• New Connectors Experience in Cloud Console
  • The Cloud Console now features a new Connectors experience, including a refreshed user interface and the ability to use secrets to reference credentials in the StreamNative Console.
  • Logs and exceptions are now available for connectors, allowing for greater visibility into connector operations, and easier debugging. These can be viewed by clicking into an individual connector from the Connectors page on the StreamNative Console.
• Cluster Default Settings Updates
  • Newly created Pulsar clusters on StreamNative Cloud will now have the following features enabled by default:
    • Kafka Protocol
    • Transactions
    • Pulsar Functions
    • IO Connectors
    • pfSQL
• Automatically select a location when creating secret
  • When creating a new secret, the Location of the secret will now be automatically prefilled. Check out our documentation to learn more about secrets.
• Usage Page Updates: The Organization Usage page has been updated to grant users greater insight into how cluster usage connects to cost.
  • Hourly Cost Available on Usage Page: Hourly cost, as well as pending charges, are now available on the Organization Usage page, as well as the csv export. While the Hourly Cost chart can be filtered by Instance, the Pending Charges metric is always an Organization-wide metric spanning across all Instances.
  • Compute and Storage Units Grouped By Instance: Usage charts for Compute Units and Storage Units are now broken down by instance, giving insight into how each instance contributes to overall usage.
  • The Usage Page now supports TB on the y-axis, for organizations where compute or storage usage extends to terabytes.
• Cluster Page Enhancements: The Cluster page of the StreamNative Console has been expanded to give you more insight on your clusters.
  • Broker Node Count and Bookie Replica Count on Dashboard: Charts showing the broker and bookie replicas have been added to the Dashboard tab of the Cluster page, to create a record of configuration changes over time.
  • New Configuration Tab: A new Configuration tab has been added to the cluster details page, containing information on which settings are enabled, as well as general configuration information.
• Service Account Permissions for Functions: Users can now view and edit which service accounts have permissions to work with functions and connectors on the Service Accounts page. To make changes to a service account’s bindings, open the ... menu on the service accounts page, and select the poolmember to which you want to give your service account access.
• Instance and cluster names can now be up to 64 characters: instances and clusters can now have more descriptive names, making it easier to manage several of them.

​

What’s New

• Documentation Site Refresh StreamNative’s documentation site has been redesigned. There are now two separate sub-sites for StreamNative Cloud and StreamNative Platform, and each section is organized by the type of work that you are trying to do:
  • Build Applications: This section is for Pulsar users within companies that are using Pulsar to build applications, such as application development teams. (They do not need to know anything about managing or architecting/administering Pulsar.)
  • Administer: This section is for Pulsar power users and core platform teams that manage Pulsar components. This section includes information on creating tenants, namespaces, and topics, as well as managing organizations and instances.
  • Manage Infrastructure: This section is primarily for customers who are managing clusters and infrastructure. (That is, SRE folks - cluster, metrics, logs.)
  

​

Other Enhancements

• Show memory and CPU when configuring Brokers and Bookies The Advanced tab for configuring a Pulsar cluster now surfaces both memory and CPU for Brokers and Bookies, making it easier to understand your cluster’s compute and storage capabilities.
• Pulsar version 2.11.1.2 for newly deployed Hosted clusters Updates from version 2.10.3.7 include the following:
  • Upgrade Pulsar server Java build version to 17.
  • Support chunking with shared subscriptions.
  • Support the pluggable topic factory.
  • Support configuring the compression type for ManagedCursorInfo to balance storage resource usage.
  To learn more about updates included in this version, see What’s New in Apache Pulsar 2.11. You can see what version your Pulsar cluster is on by checking the Details tab on the cluster configuration page. If you want to upgrade your existing clusters, please submit a ticket.
• Pulsar Admin Go version 0.1.1 Pulsar Admin Go library v0.1.1 has been released, and includes the following updates:
  • Add two new parameters (BrokerClientTrustCertsFilePath and BrokerClientTlsEnabled) to support TLS when creating a cluster.
  • Add GetMessageID to the API, which returns the message ID by timestamp(ms) of a topic.
  To learn more about Pulsar Admin Go, check out the blog post here.
• Functions Usage Chart The Organization Usage page on StreamNative Cloud Console now includes a chart showing an organization’s function usage in Compute Units (CUs), for organizations that have functions enabled.

​

Bug Fixes

​

What’s New

• New Connector: AWS EventBridge Sink Connector
  • The StreamNative team has built a new connector for open source Pulsar - the AWS EventBridge Sink Connector! With it, you can pull data from a Pulsar cluster and persist it to AWS EventBridge, making it easier to build scalable event-driven applications. To learn more, check out our recent blog post.
  • Additionally, the AWS Eventbridge Sink Connector is also available on StreamNative Cloud! For a detailed setup tutorial, check out our blog post announcing the integration. If you would like to use it, please reach out to the StreamNative Support Team.
• StreamNative Hub The StreamNative Hub has a new design and is quickly accessible from the StreamNative Docs site, making it easier to find connectors and understand which connectors are supported on StreamNative Cloud.
• Pulsar 3.0 available on StreamNative Cloud Pulsar 3.0, the next evolution of Pulsar, is now available on StreamNative Cloud. Pulsar 3.0 allows teams to run even bigger workloads, and is easier for developers to work with on their local machines. Updates include LTS support, an improved load balancer, several performance improvements, and Docker images for M1/M2 Macs. You can try Pulsar 3.0 on a new cluster or reach out to the StreamNative Support Team about upgrading existing clusters.

​

Other Enhancements

• Additional Version Details available on StreamNative Cloud Console Pulsar, BookKeeper, and ZooKeeper versions are now available on the cluster details page, giving you greater insight into your cluster’s configuration details.
• Improved experience on the Organization Usage page It is now easier to understand how many resources your clusters consume. You can view usage metrics (such as compute, storage and data) for a specific instance and then compare it to the organization’s usage across all instances.
• AWS Marketplace listing update We have updated our product listing on AWS Marketplace. With the more streamlined listing, you can view usage data via the Organization Usage page.

​

What’s New

• New Setup Guide. A new setup guide has been added to the Dashboard page and contains everything that you need to get up and running with a hosted cluster. On the Dashboard page, you will see step-by-step instructions on adding a payment method, creating and configuring Pulsar clusters, creating topics, setting up clients, and sending messages. The setup guide can be viewed by logging in to the StreamNative Cloud Console and clicking Dashboard on the left navigation pane.
• Organization Usage Page. Customers with StreamNative Managed Clusters (Hosted + BYOC) can now view both real-time and historical cluster usage data on the new Organization Usage page. This page features charts visualizing the usage dimensions (Compute Units, Storage Units, Throughput, and Storage Size) for all clusters within an organization. You can view usage by instance or in aggregate across your organization and narrow the date range to hone in on usage over a specific time period. You can view up to the past 60 days of usage.
• Improved Usability for Kafka Clients. Customers with clusters that have Kafka protocol enabled will include a new Kafka Clients page that walks you through using Kafka clients to connect to your clusters. The Kafka client setup wizard enables application developers using Kafka clients to easily connect to their organization’s Pulsar cluster. This page includes client libraries (Java, Go, Python, C++, Node.js), Apache Kafka CLI tools, KStream applications, and KSQL. In addition, the Kafka protocol is also enabled by default on all new managed Pulsar clusters (Hosted + BYOC).

​

Other Enhancements

• Refreshed Dashboard for managing instances and user accounts on StreamNative Cloud Console. You will see two new cards on the Dashboard page, surfacing additional information about your organization’s instances and user accounts, allowing you to manage instances and user accounts directly from the Dashboard page without going to a separate screen.
• New hosted clusters on Pulsar 2.10.3.7. New hosted Pulsar clusters (clusters hosted on StreamNative’s public cloud account) will now be on version 2.10.3.7, where they were previously on version 2.9.3.21. As a result, you will benefit from the following enhancements:
  • Pulsar provides automatic failure recovery between the primary and backup clusters.
  • With the lazy-loading feature added to PartitionedProducer, fewer producers are needed and the broker memory utilization is improved.
  • Topic map support added with a new TableView type using key values in received messages.
  To learn more about features offered in this version, see What’s New in Apache Pulsar 2.10. If you would like to upgrade your cluster, please submit a ticket.
• Audit log now includes produce and consume events. For clusters on Pulsar 2.10.3.7 and later, Produce and Consume events can now be tracked in the audit log.
• Streamlined instance deletion experience. You can now delete an instance and all Pulsar clusters within it in one step, rather than having to individually delete all associated clusters before deleting the instance.
• Snowflake Sink Connector upgrade. The Snowflake Sink Connector on StreamNative Cloud Console has been upgraded from 2.9.4.1 to 2.10.3.4. In addition to smaller bug fixes, this connector now supports concurrency where it previously did not, meaning the replicas can now be set to more than 1 when configuring a connector.

​

Bug Fixes

• Fixed an issue preventing the creation of a Debezium-Postgres connector via the StreamNative Cloud Console.
• Fixed an issue where namespaces with lots of topics would sometimes show a spurious error on the Namespace page of the StreamNative Cloud Console.
• Fixed an issue causing configuration details on the Functions page to display without formatting.

​

What’s New

• New Clients Page. The Clients page makes it easier to connect to a Pulsar cluster with your client of choice. You’ll find comprehensive example snippets with better syntax highlighting, more programming languages (Java, Go, Python, C++, Node.js, Rust, Spring, C#), and more REST API and CLI tool examples. You can download authentication tokens (either an OAuth2 credential file or a JWT token) directly from the Clients page. To view the new page, select a programming language, CLI tool, or REST API. Then, you can see installation and connection instructions. Watch the video below for an example of connecting to a cluster using the Java client.
• Pulsar Transactions on StreamNative Cloud. You can now configure Pulsar Transactions using the StreamNative Cloud Console. Pulsar Transactions (in Beta on StreamNative Cloud) enable event-streaming applications to consume, process, and produce messages in one atomic operation, including:
  • Atomic writes across multiple topic partitions
  • Atomic acknowledgments across multiple topic partitions
  • All the operations made within one transaction either all succeed, or all fail
  • Consumers are ONLY allowed to read committed messages

​

Improvements

• Navigation bar refresh. The new design for the navigation bar on the StreamNative Cloud Console includes a lighter theme and updated icons, making it easier to navigate the console. To colocate all Admin tasks, the Clients tab was moved to the Admin section.
• Pulsar cluster names. With this release, the maximum number of characters for Pulsar cluster names is 10 characters. (Note: Existing Pulsar clusters with names longer than 10 characters are not affected by this change.)
• Request a region. If you are creating a new cluster using StreamNative Cloud Console and a region is not currently supported, you can request support for that region.

​

Bug Fixes

• Previously, it was possible to delete instances with active clusters. Now, before you can delete an instance, you must first delete all clusters within that instance.
• Previously, you could not disable the audit log once it was turned on (enabled). With this release, it is now possible to toggle the audit log on and off.

​

Breaking Changes

• Deprecation of free cloud. New customers can no longer sign up for free clusters. If you are interested in requesting access to StreamNative Cloud, please Contact us.

​

New provisioning changes for hosted clusters

• You can provision new clusters through StreamNative Cloud console, with a prompt to update payment information.
• New changes will not impact existing clusters. To adjust the sizing of existing clusters, please submit a ticket, and our team will assist with this one-time migration.

​

Audit Log

​

New connectors

• Debezium / Microsoft SQL Server Source - Pulls messages from the SQL Server and persists the messages to Pulsar topics.
• Google BigQuery Source - Feeds data from Google Cloud BigQuery tables and writes data to Pulsar topics.
• Google BigQuery Sink - Pulls data from Pulsar topics and persists data to Google Cloud.
• Snowflake Sink (available through the CLI) - Loads data from Pulsar topics to Snowflake in real time.

​

Cluster Metrics in Beta

​

Pulsar Functions on Cloud in Beta

​

REST API

• Produce, consume, and acknowledge messages
• Monitor the state of your Pulsar clusters
• Perform a wide range of administrative actions

​

Improvements for new clusters

• All new clusters are based on Pulsar v2.9.3.21.

​

Cluster configurations added to the cluster Overview tab

​

Cloud Console optimizations

​

Instance selection made clearer

​

Documentation updates

• A card-style landing page.
• Enhanced navigation with breadcrumbs and back/next links on every page.
• A new search engine for faster, more accurate search results.

• The procedure for creating a StreamNative Cloud account through the AWS Marketplace was updated and the help topic now reflects the correct workflow. For details, see the AWS billing page.
• The Google BigQuery sink was added as a new connector and the documentation page was updated accordingly. For details, see the Create Connectors.
• The name StreamNative Cloud Manager was updated to StreamNative Cloud Console throughout the documentation site. This change was made to be consistent with the app.

• In StreamNative Cloud Manager Release 2.2.2, a new sign in flow was added for first-time users. For details, see the quick start.
• The Flink SQL UI option has been deprecated. However, you can still work with Flink SQL through the CLI.
• A new source connector, Debezium Microsoft SQL Server, was added. For details, see the Create Connectors.

• For StreamNative Cloud Manager Release 2.1.7, support for SSO was added to the login process. For details, see the Quick start.
• A default organization is now created for you when you sign up for StreamNative Cloud, saving you time in the set up process. For details, see Work with organizations.
• Clusters include more choices in cloud provider regions. For details, see Work with clusters.

​

Highlights

• New Dashboard page that serves as a quick health check of your instances with your most important tasks close at hand.
• Updated navigation menu to simplify and streamline the management of StreamNative and Pulsar resources.
• Significant internal re-architecture to make the UI faster and more responsive, without some of the previous delays of API changes not being shown in the UI.

​

What’s New

• Cloud Console Dashboard and login changes
  • This new home page is designed to make it easy for you to see the status of your instances and to quickly get started with StreamNative Cloud.
  • The Cloud Console now remembers your most recent organization and instance.
• New Navigation
  • The navigation menu has been significantly changed to make navigation more intuitive.
  • A new quick switcher for tenants and namespaces has been added to the navigation bar.

​

Changes

• Update your bookmarks! The links have changed. The previous links did not allow for deep linking.
• Certain metrics, such as number of topics in a namespace, traffic, and others have been removed. These metrics were a point-in-time snapshot that was often out-of-date, potentially leading to confusion.
• Numerous bug fixes and performance improvements have been implemented. These bug fixes include issues with changes via the Pulsar REST API not being visible within the UI and issues with large numbers of topics or namespaces.

​

Future plans

• Additional dashboard cards with contextual actions to simplify managing your Pulsar infrastructure.
• Richer, historical metrics to see how your instance and applications are performing.
• Additional improvements to the provisioning workflow to make it easier to deploy and manage instances and clusters.

​

Documentation improvements

• Several topics were updated to reflect the updated StreamNative Cloud Manager UI. This was a major update to the UI, reflecting StreamNative’s commitment to continuous improvement.
• The Node.js client topic was updated to reflect support for OAuth2 authentication. For details, see connect to Pulsar clusters through the Node.js client.
• The AWS Lambda sink connector is onboarding to StreamNative Cloud. For details, see the Create Connectors.

• A new topic on StreamNative Cloud Secrets was added to the Managed Access section. StreamNative Cloud Secrets allow you to store and manage sensitive data such as passwords, tokens, and private keys. You can create Secrets and refer to them for computing purposes (Pulsar connectors, Pulsar Functions, Flink SQL and general Flink jobs). For details, see work with Secrets.
• Per-topic throughput limit and storage limit for clusters was updated in the Clusters topic.
• Billing information was removed from the Billing topic, as up-to-date billing information is on the StreamNative website.
• The snctl reference topic was updated with an improved order of information.

• New layout and formatting
• Clear, consistent language for faster reading
• Improved cross-referencing for easier navigation
• Streamlined procedures
• Updated organization
• New sections for specific use cases

• Overview
• Quick Start with StreamNative Cloud Manager
• snctl reference

​

CLI updates

• Added support for enabling WebSocket service at the cluster level. The Pulsar WebSocket API provides a simple way to interact with Pulsar using languages that do not have an official client library. For details, see connect to cluster through WebSocket API.
• Added support for customizing some cluster configurations. You can customize their clusters either by defining spec.config custom field in the cluster YAML file or specifying cluster configurations using StreamNative Cloud Manager. For details, see work with clusters.

​

Feature Enhancements

• Debezium MongoDB: the Debezium MongoDB source connector pulls messages from MongoDB and persists the messages to Pulsar topics.
• Debezium MySQL: the Debezium MySQL source connector pulls messages from MySQL and persists the messages to Pulsar topics.
• Debezium PostgreSQL: the Debezium PostgreSQL source connector pulls messages from PostgreSQL and persists the messages to Pulsar topics.

​

AWS Marketplace

​

Feature enhancements

​

StreamNative Cloud Console

• Added more fine-grained and easy-to-use configuration of Pulsar connectors. You can specify each configuration from the StreamNative Cloud console.
• Added monitoring support for connectors. You can view the status of a connector including when a connector fails to be created, updated, or cloned. For details, see here.

​

snctl CLI tool

• Added support for installing snctl CLI tools on Linux and MAC OS using Homebrew.

​

General changes

• StreamNative Cloud supports Pulsar 2.8.0.
• Connectors are now available in StreamNative Cloud. They provide a convenient way to move data in and out of the cloud without writing any code.
  • This release supports pre-approved connectors for SQS, Kinesis, AWS S3, and Lambda functions on AWS and Google Cloud cloud-hosted platforms.
  • You can configure and manage connectors using the pulsarctl CLI tool or the StreamNative Cloud Manager. For details, see here.

​

Bug fixes

• Basic (select, insert, filter, aggregate)
• TimeSeries Aggregation (watermark, event time, session time, processing time)
• Joins

• You can create a Flink Cluster through either snctl or StreamNative Cloud Manager.
• You can interact with Flink SQL through StreamNative Cloud Manager to perform the following operations:
  • Run streaming queries on data stored in Pulsar topics using Flink SQL.
  • Explore query results.

• StreamNative Cloud now enables to deploy clusters on AWS cloud platform. The pricing has also been defined for newly created clusters on AWS cloud platform.
• Support different locations for clusters deployed on the Google Cloud and AWS cloud platforms.
• Add an Instance Setting option on the left navigation pane of the StreamNative Cloud Manager, where you can check detailed information about created instances and delete the target instance.

• StreamNative Cloud provides a promotion code for users who want to use the StreamNative Cloud service. Contact us to get a promotion code. For details about how to apply the promotion code, see apply promotion code.
• Updated the layout of the Sign up page.

​

Security

• Secure clusters based on OAuth 2.0 and TLS.

​

Functionality

• StreamNative Cloud resources
  • Organizations
  • User accounts
  • Service accounts
  • Instances
  • Clusters
  • Billing
• Pulsar components
  • Tenants
  • Namespaces
  • Topics
  • Subscription
  • Schema