snctl
): The unified command-line interface for deploying and managing StreamNative Cloud infrastructure and interacting directly with your Pulsar clusters and Kafka-protocol endpoints.pulsarctl
): For managing cluster-specific resources, such as tenants, namespaces, topics, functions, connectors, and more.my-aws-connection
.Connected
in the Cloud Connections tab.
my-aws-connection
. Then click Environment setup.
us-west-2
.poc
.10.0.0.0/16
. If you need to specify a different CIDR, you can enter it here.my-ursa-instance
.my-aws-connection
.URSA Engine
.my-ursa-cluster
.aws-usw2-poc-<random-suffix>
.produce
and consume
permissions for this namespace.
produce
permission to the public/__kafka_schemaregistry/__schema-registry
topic. This is required because the current implementation of Kafka Schema Registry uses this topic’s ACL to authorize access to the schema registry.
public / __kafka_schemaregistry
namepsace.
__schema-registry
.
produce
and consume
permissions for this namespace. You also grant the service account permission to access the Kafka Schema Registry. You can now continue on to building a Python app, connecting to the cluster, and producing and consuming messages.
pom.xml
file, and click Next.
e. Select the target tenant, namespace, topic, and subscription.
f. You are now ready to copy the auto-generated sample codes.
pom.xml
and add the following content:
src/main/java/org/example
.
c. Under src/main/java/org/example
, create a file named SNCloudTokenProducer.java
. Copy and paste the producer code to this file.
d. Under src/main/java/org/example
, create a file named SNCloudTokenConsumer.java
. Copy and paste the consumer code to this file.
e. In both files, replace <JWT Token>
with the API key you copied from the Service Account page.
c. Go to the root folder of your project and run the following command to build your project:
<org-id>-<cluster-name>-<randomized-string>-ursa
. There are two sub folders: storage
and compaction
. The storage
folder contains the raw WAL files and the compaction
folder contains the compacted lakehouse tables. Those lakehouse tables are organized by <tenant>/<namespace>/<topic>
.