Deployment
Run Avra in Avra's cloud, or in your own environment, with the data layer in your Kubernetes cluster and Avra RFM in your AWS account.
Avra runs in one of two places. In Avra’s cloud, Avra operates everything for you. In your own environment, Avra’s software runs next to your data: the data layer in your Kubernetes cluster, and Avra RFM in your AWS account on Amazon SageMaker. Avra’s control plane manages the data layer from outside, and nothing connects into your network. Your data is protected in both.
This page explains what runs where in each option, what crosses the boundary between Avra and your environment, and how to choose.
Avra's cloud
Avra runs everything for you. Your workspace is a tenant of its own, isolated from every other customer, and your data, your models, and their records stay inside it.
Your environment
Avra’s data layer runs in your Kubernetes cluster, installed with Helm. Avra RFM runs in your AWS account on Amazon SageMaker, through AWS Marketplace. Avra’s control plane manages the data layer from outside, with no inbound connection.
Deploying in your environment
A deployment in your environment follows five steps. You provide the infrastructure and run one install command, and your Avra team configures the rest with you.
Plan with your Avra team
Agree on what you provide: a Kubernetes cluster, a bucket, a PostgreSQL database, outbound network access, and an AWS account. See Before you start.
Install the data layer
Run the install command Avra sends you. A deployment agent installs the data layer in your cluster, and the Avra agent starts polling Avra’s control plane. See Install the data layer.
Bring your data
Agree on the data contract, and Avra sets up your pipelines with you. Each run that passes the contract’s checks publishes a new version in your bucket. See Data ingestion.
Subscribe to Avra RFM
Subscribe to the Avra RFM listing on AWS Marketplace from the account where your data lives, then prepare S3 and an execution role. See Avra RFM on AWS SageMaker.
Predict
Run inference jobs to score records, and training jobs to adapt or fine-tune a copy of the model, all in your AWS account.
What runs where
| Component | Runs in | What it does |
|---|---|---|
| Control plane | Avra’s cloud | The dashboard, the API, and the model registry. It queues commands for your environment and receives their results |
| Avra agent | Your Kubernetes cluster | Polls the control plane over outbound HTTPS, runs the commands it receives, and reports back |
| Ingestion pipeline | Your Kubernetes cluster | Validates and versions your data, with Spark doing the processing. Its tables live in your bucket, and its run state in your database. See Data ingestion |
| Deployment agent | Your Kubernetes cluster | Installs and upgrades the data layer, and reports the status of each release |
| Telemetry collector | Your Kubernetes cluster | Forwards operational telemetry to Avra |
| Avra RFM | Your AWS account | Runs on Amazon SageMaker: training jobs for adaptation and fine-tuning, inference jobs for predictions |
| Avra GFM | Avra’s cloud only | Never deployed to your environment. Models built on its embeddings can run in your environment with a snapshot of the embeddings they use |
What returns to Avra is execution metadata, such as each command’s status and result, and operational telemetry. Your data, the models adapted to it, and their outputs stay in your environment.
What crosses the boundary
Every connection between your environment and Avra opens from your side, over HTTPS. The Avra agent asks the control plane for work, the commands come back in the reply, and the agent sends each result in a request of its own. Nothing in your environment listens for connections from Avra, so your network needs no inbound rule.
| Flow | Opened by | What it carries |
|---|---|---|
| Polls | Avra agent | The agent’s version, your cluster name, and the health of its layer. The reply carries pending commands, cancellations, and when to poll next |
| Reports | Avra agent | Each command’s status, its progress, and its result or error |
| Telemetry | Telemetry collector | Logs, metrics, and traces from Avra’s components, and the resource metrics the kubelet reports for the node the collector runs on and the pods on it, labeled with your cluster name |
| Releases | Deployment agent | Fetches your deployment’s versions and values, pulls the data layer’s charts, and reports the status of each release and its own logs. Depending on its settings, it also sends the logs and resource usage of the layers’ containers, and the cluster’s CPU and memory totals |
| Images | Your nodes’ container runtime | Pulls the images the layers run: Avra’s from Avra’s registries, and those of the open-source components from their public registries |
Your data, the versions the ingestion pipeline publishes, its run state, the copies of Avra RFM adapted to your data, and the scores they produce stay in your environment. Avra RFM’s jobs on SageMaker run network-isolated: they can’t open a connection to Avra or anywhere else.
Avra’s cloud or your environment
| Avra’s cloud | Your environment | |
|---|---|---|
| Control plane | Avra | Avra |
| Data ingestion | Avra’s cloud, inside your isolated workspace | Your Kubernetes cluster |
| Where your data stays | Isolated by tenant and workspace in Avra’s cloud | Your bucket and your database |
| Avra RFM | Avra’s cloud | Your AWS account, on Amazon SageMaker |
| Predictions | Live through the API, or in batches | Inference jobs that write scores to your S3 |
| Adapted and fine-tuned copies | Inside your workspace | Your S3, encrypted |
| Avra GFM | Avra’s cloud | Avra’s cloud only |
| What returns to Avra | Not applicable, since everything runs in Avra’s cloud | Execution metadata, and operational telemetry |
| Who runs the infrastructure | Avra | You run the cluster, the bucket, the database, and the AWS account. Avra installs and upgrades its software |
Who does what
In your environment, the work splits between you and Avra:
| You | Avra | |
|---|---|---|
| Cluster, namespace, and network access | Provide | Specify what’s needed |
| Bucket, database, and identities | Provide | Specify what’s needed |
| Charts, images, and their versions | Build and publish | |
| Installing and upgrading the layers | Run the install command | Configure the deployment and roll out versions |
| Pipelines | Agree on the data contract | Write and run them with you |
| AWS account, S3, and execution role | Provide, and subscribe on AWS Marketplace | Specify what’s needed |
| The RFM algorithm and its releases | Build, govern, and release |
Choosing
Avra’s cloud asks the least of you. There’s nothing to install or operate, and Avra RFM serves live predictions through the API as well as batches. Your workspace is isolated from every other customer’s, and nothing about your business trains another customer’s model.
Choose your environment when regulation, data sovereignty, or your own policy requires your data to stay in infrastructure you control. It takes a Kubernetes cluster for the data layer and an AWS account for Avra RFM, and a team to run them. In a customer’s environment, Avra RFM runs only on Amazon SageMaker, so if yours isn’t on AWS, talk to your Avra team before you plan. Avra GFM stays in Avra’s cloud either way, and its outputs reach you through Avra Core.
Contact your Avra representative to plan a deployment in your environment.
Install the data layer
What you provide, how the installation runs, and how to verify and upgrade it
Avra RFM on AWS SageMaker
Subscribe on AWS Marketplace, then run training and inference jobs in your account
Data ingestion
How your data becomes validated, versioned inputs for Avra’s models
Data privacy & compliance
How Avra keeps your data isolated, wherever it runs