LogoLogo
Ockam.ioOpen Source CodeContact usSign up
  • Intro to Ockam
  • Ockam's core concepts
  • Get started demo
  • Quickstarts
    • Add secure connectivity to your SaaS product
    • Snowflake federated queries to Postgres
    • Postgres to Snowflake
    • Snowflake to Postgres
    • Kafka to Snowflake
    • Snowflake to Kafka
    • Snowflake stage as SFTP server
    • Snowflake stage as WebDAV file share
    • Snowflake hosted private APIs
    • Federated queries from Snowflake
  • ENCRYPTED PORTALS TO ...
    • Databases
      • PostgreSQL
        • Docker
        • Kubernetes
        • Amazon RDS
        • Amazon Aurora
      • MongoDB
        • Docker
        • Kubernetes
        • Amazon EC2
      • InfluxDB
        • Amazon Timestream
    • APIs
      • Nodejs
      • Python
    • AI
      • Amazon Bedrock
      • Amazon EC2
      • Azure OpenAI
    • Code Repos
      • Gitlab Enterprise
    • Kafka
      • Apache Kafka
        • Docker
      • Redpanda
        • Self Hosted
      • Confluent
        • Cloud
      • Warpstream
        • Cloud
      • Instaclustr
        • Cloud
      • Aiven
        • Cloud
  • Reference
    • Command
      • Nodes and Workers
      • Routing and Transports
      • Relays and Portals
      • Identities and Vaults
      • Secure Channels
      • Verifiable Credentials
      • Guides
        • AWS Marketplace
          • Ockam Node
          • Ockam Node for Amazon MSK
          • Ockam Node for Amazon RDS Postgres
          • Ockam Node for Amazon Timestream InfluxDB
          • Ockam Node for Amazon Redshift
          • Ockam Node for Amazon Bedrock
      • Manual
    • Programming Libraries
      • Rust
        • Nodes and Workers
        • Routing and Transports
        • Identities and Vaults
        • Secure Channels
        • Credentials and Authorities
        • Implementation and Internals
          • Nodes and Workers
        • docs.rs/ockam
    • Protocols
      • Nodes and Workers
      • Routing and Transports
      • Keys and Vaults
      • Identities and Credentials
      • Secure Channels
      • Access Controls and Policies
Powered by GitBook
On this page
  • Run
  • Walkthrough
  • Administrator
  • AI Corp
  • Health Corp
  • Recap
  • Cleanup

Was this helpful?

Edit on GitHub
Export as PDF
  1. ENCRYPTED PORTALS TO ...
  2. AI

Amazon Bedrock

PreviousAINextAmazon EC2

Last updated 4 months ago

Was this helpful?

Let's connect a nodejs app in one virtual private network with an application serving an Amazon Bedrock model in another virtual private network. The example uses the AWS CLI to create these virtual networks.

Each company’s network is private, isolated, and doesn't expose ports. To learn how end-to-end trust is established, please read: “”

Run

Then run the following commands:

# Clone the Ockam repo from Github.
git clone --depth 1 https://github.com/build-trust/ockam && cd ockam

# Navigate to this example’s directory.
cd examples/command/portals/ai/amazon_bedrock

# Run the example, use Ctrl-C to exit at any point.
./run.sh

If everything runs as expected, you'll see the answer to the question: "What is Ockham's Razor?".

Walkthrough

Administrator

  • 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.

AI Corp

First, the ai_corp/run.sh script creates a network to host the application exposing the Bedrock model API:

We are now ready to create an EC2 instance where the Ockam outlet node will run:

When the instance is started, the run_ockam.sh script is executed:

  • We then create an Ockam node:

Health Corp

First, the health_corp/run.sh script creates a network to host the client.js application which will connect to the Bedrock model:

We are now ready to create an EC2 instance where the Ockam inlet node will run:

The instance is started and the run_ockam.sh script is executed:

  • We then create an Ockam node:

We finally wait for the instance to be ready and install the client.js application:

Once the client.js application is started:

Recap

We connected a nodejs application in one virtual private network with an application serving an Amazon Bedrock model in another virtual private network over an end-to-end encrypted portal.

Health Corp. does not get unfettered access to AI Corp.’s network. It gets access only to run API queries. AI Corp. does not get unfettered access to Health Corp.’s network. It gets access only to respond to queries over a TCP connection. AI Corp. cannot initiate connections.

Cleanup

To delete all AWS resources:

./run.sh cleanup

This example requires Bash, Git, Curl, and the AWS CLI. Please set up these tools for your operating system. In particular you need to with aws sso login.

The script, that you ran above, and its 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 calls the which invokes the to create an new identity, sign into Ockam Orchestrator, set up a new Ockam project, make you the administrator of this project, and get a project membership .

The run function then . The tickets are valid for 10 minutes. Each ticket can be redeemed only once and assigns to its redeemer. The is meant for the Ockam node that will run in AI Corp.’s network. The is meant for the Ockam node that will run in Health Corp.’s network.

The run function passes the enrollment tickets as variables of the run scripts provisioning and .

We and tag it.

We . This will be used to create the private link below.

We and attach it to the VPC.

We and to the Internet via the gateway.

We , with associate it to the route table.

We so that there is:

,

And to install the application accessing the model.

We finally to allow the Bedrock client inside the server application to access the Bedrock model.

We .

We in order to access the EC2 instance via SSH.

We . Starting the instance executes a start script based on ai_corp/run_ockam.sh where:

created by the administrator and given as a parameter to ai_corp/run.sh.

We

We

We .

The .

The .

With .

A . The policy authorizes identities with a credential containing the attribute ai-inlet="true".

With capable of forwarding the TCP traffic to the TCP outlet.

The model used in this example is the "Titan Text G1 - Lite" model. In order to use it, .

We and tag it.

We and attach it to the VPC.

We and to the Internet via the gateway.

We , and associate it to the route table.

We finally so that there is:

,

And to download and install the nodejs client application.

We .

We above and a start script based on run_ockam.sh where:

created by the administrator and given as a parameter to run.sh.

The .

The .

With .

Forwarding messages to

A . The policy authorizes identities with a credential containing the attribute ai-outlet="true".

The is (this uses the previously created key.pem file to identify).

We can then and:

.

.

It will .

It and waits for a response from the model.

The response is then .

Sensitive business data coming from the model is only accessible to AI Corp. and Health Corp. All data is with strong forward secrecy as it moves through the Internet. The communication channel is and . Keys and credentials are automatically rotated. Access to connect with the model API can be easily revoked.

All are secure-by-default. Only project members, with valid credentials, can connect with each other. NAT’s are traversed using a relay and outgoing tcp connections. AI Corp. or Health Corp. don’t expose any listening endpoints on the Internet. Their networks are completely closed and protected from any attacks from the Internet.

login to your AWS account
run.sh script
accompanying files
AI Corp.'s network
Health Corp.'s network
create a VPC
enable DNS attributes and hostnames for the VPC
create an Internet gateway
create a route table
create a route
create a subnet
create a security group
One TCP egress to the Internet
one SSH ingress
server
create a private link to the Amazon Bedrock service
select an AMI
create a key pair
start an instance using the selected AMI
ENROLLMENT_TICKET is replaced by the enrollment ticket
tag the created instance
create an IAM profile with a role allowing the EC2 instance to access the Bedrock API
wait for it to be available
ockam executable is installed
enrollment ticket is used to create a default identity and make it a project member
a TCP outlet
policy associated to the outlet
a relay
you will need to request access to this model
create a VPC
create an Internet gateway
create a route table
create a route
create a subnet
create a security group
One TCP egress to the Internet
one SSH ingress
select an AMI
start an instance using the AMI
ENROLLMENT_TICKET is replaced by the enrollment ticket
ockam executable is installed
enrollment ticket is used to create a default identity and make it a project member
a TCP inlet
the ai relay
policy associated to the inlet
client.js file
copied to the instance
SSH to the instance
Install nodejs
Start the client.js application
connect to the Ockam inlet at port 3000
sends a query
printed on the console
encrypted
mutually authenticated
authorized
access controls
How does Ockam work?
run.sh script
run function
enroll command
generates two new enrollment tickets
first ticket
second ticket
credential
attributes