Multi-Cloud Tool Access

The Problem

Traditional agents need cloud credentials hardcoded or injected via environment variables:

# ❌ The old way — credentials everywhere
import boto3
session = boto3.Session(
    aws_access_key_id="AKIA...",        # Leaked in git
    aws_secret_access_key="wJalr...",   # Rotated manually
)

The Hexr Way

# ✅ The Hexr way — identity-based access
from hexr import hexr_agent, hexr_tool

@hexr_agent(name="multi-cloud-agent", tenant="acme-corp")
def main():
    # AWS — automatic STS credential exchange
    s3 = hexr_tool("aws_s3")
    obj = s3.get_object(Bucket="reports", Key="sales.csv")
    s3_data = obj["Body"].read()

    # GCP — automatic Workload Identity Federation
    bq = hexr_tool("gcp_bigquery")
    bq_data = bq.query("SELECT * FROM dataset.table LIMIT 10")

    # Azure — automatic federated identity
    blob_client = hexr_tool("azure_storage")
    blob = blob_client.get_blob_client(container="data", blob="report.pdf")
    blob_data = blob.download_blob().readall()

Zero credentials in your code. The platform exchanges your agent’s SPIFFE identity for short-lived cloud tokens automatically.

How It Works

Agent requests AWS tool

Your agent calls hexr_tool("aws_s3", ...). The request goes through Envoy to the Credential Injector.

SPIFFE → AWS credential exchange

The Credential Injector calls AWS AssumeRoleWithWebIdentity with the JWT-SVID. AWS returns temporary credentials (15-minute TTL).

Agent requests GCP tool

Your agent calls hexr_tool("gcp_bigquery", ...). Same flow through Envoy to the Credential Injector.

SPIFFE → GCP credential exchange

The Credential Injector calls GCP STS for token exchange. GCP returns an access_token (60-minute TTL).

Agent → Envoy → Credential Injector → AWS STS (15min creds) / GCP STS (60min token)

Setup

Build with Multi-Cloud

hexr build agent.py --tenant acme-corp --multi-cloud aws,gcp,azure

Cloud Provider Configuration

AWS

Create an IAM OIDC Identity Provider pointing to oidc.hexr.cloud
Create an IAM Role with a trust policy for your agent’s SPIFFE ID
Configure the role ARN in Helm values:

credentialInjector:
  aws:
    roleArn: arn:aws:iam::123456789:role/hexr-agent-role

GCP

Create a Workload Identity Pool
Add an OIDC Provider pointing to oidc.hexr.cloud
Create a service account and grant the pool access
Configure in Helm values:

credentialInjector:
  gcp:
    workloadIdentityProvider: projects/123/locations/global/workloadIdentityPools/hexr/providers/spire

Azure

Create an App Registration with Federated Identity Credentials
Set the issuer to oidc.hexr.cloud
Configure in Helm values:

credentialInjector:
  azure:
    tenantId: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    clientId: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

Per-Process Cloud Access

In a CrewAI crew, each role can have different cloud permissions:

@hexr_agent(name="data-crew", tenant="acme", framework="crewai")
def main():
    # researcher → spiffe://.../data-crew/researcher → BigQuery read-only
    # writer → spiffe://.../data-crew/writer → S3 write-only
    # No code changes needed — OPA policies enforce the scoping
    ...

​The Problem

​The Hexr Way

​How It Works

​Setup

​Build with Multi-Cloud

​Cloud Provider Configuration

​Per-Process Cloud Access