Self Hosted
Last updated
Last updated
In this hands-on example we send end-to-end encrypted messages through Redpanda.
Ockam encrypts messages from a Producer all-of-the-way to a specific Consumer. Only that specific Consumer can decrypt these messages. This guarantees that your data cannot be observed or tampered with as it passes through Redpanda or the network where it is hosted. The operators of Redpanda can only see encrypted data in the network and in service that they operate. Thus, a compromise of the operator's infrastructure will not compromise the data stream's security, privacy, or integrity.
To learn how end-to-end trust is established, please read: “How does Ockam work?”
This example requires Bash, Git, Curl, Docker, and Docker Compose. Please set up these tools for your operating system, then run the following commands:
If everything runs as expected, you'll see the message: The example run was successful 🥳
The run.sh script, that you ran above, and its accompanying files are full of comments and meant to be read. The example setup is only a few simple steps, so please take some time to read and explore.
The run.sh script calls the run function which invokes the enroll command to create an new identity, sign in to Ockam Orchestrator, set up a new Ockam project, make you the administrator of this project, and get a project membership credential.
The run function then generates three new enrollment tickets, each valid for 10 minutes, and can be redeemed only once. The first ticket is meant for the Ockam node that will run in Redpanda Operator’s network. The second and third tickets are meant for the Consumer and Producer, in the Ockam node that will run in Application Team’s network.
In a typical production setup, an administrator or provisioning pipeline generates enrollment tickets and gives them to nodes that are being provisioned. In our example, the run function is acting on your behalf as the administrator of the Ockam project. It provisions Ockam nodes in Redpanda Operator’s network and Application Team’s network, passing them their tickets using environment variables.
The run function takes the enrollment tickets, sets them as the value of an environment variable, and invokes docker-compose to create Redpanda Operator’s and Application Team’s networks.
Redpanda Operator’s docker-compose configuration is used when run.sh invokes docker-compose. It creates an isolated virtual network for Redpanda Operator.
In this network, docker compose starts a container with a Redpanda event store . This container becomes available at redpanda:9092 in the Redpanda Operator network.
In the same network, docker compose also starts a Redpanda console , connecting directly to redpanda:9092. The console will be reachable throughout the example at http://127.0.0.1:8080.
Once the Redpanda container is ready, docker compose starts an Ockam node in a container as a companion to the Redpanda container described by ockam.yaml, embedded in the script. The node will automatically create an identity, enroll with your project using the ticket passed to the container, and set up Kafka outlet.
The Ockam node then uses this identity and membership credential to authenticate and create a relay in the project, back to the node, at relay: redpanda. The run function gave the enrollment ticket permission to use this relay address.
Application Team’s docker-compose configuration is used when run.sh invokes docker-compose. It creates an isolated virtual network for the Application Team. In this network, docker compose starts a Kafka Consumer container and a Kafka Producer container.
The Kafka consumer node container is created using this dockerfile and this entrypoint script. The consumer enrollment ticket from run.sh is passed to the container via environment variable.
When the Kafka consumer node container starts in the Application Team's network, it runs its entrypoint. The entrypoint creates the Ockam node described by ockam.yaml, embedded in the script. The node will automatically create an identity, enroll with your project, and setup Kafka inlet.
Next, the entrypoint at the end executes the command present in the docker-compose configuration, which launches a Kafka consumer waiting for messages in the demo topic. Once the messages are received, they are printed out.
In the producer container, the process is analogous, once the Ockam node is set up the command within docker-compose configuration launches a Kafka producer that sends messages.
You can view the Redpanda console available at http://127.0.0.1:8080 to see the encrypted messages
We sent end-to-end encrypted messages through Redpanda.
Messages are encrypted with strong forward secrecy as soon as they leave a Producer, and only the intended Consumer can decrypt those messages. Redpanda and other Consumers can only see encrypted messages.
All communication is mutually authenticated and authorized. Keys and credentials are automatically rotated. Access can be easily revoked.
To delete all containers and images:
