Odigos Enterprise

Odigos Enterprise 2026.09.28: EKS 1.34, AL2023, Linux amd64; one install per cluster. Requires a subscription, Helm 3, kubectl, AWS CLI, Python 3 and boto3. Metering requires IRSA.

1. Subscribe to Odigos Enterprise. The AWS principal fetching the license must have lambda:InvokeFunctionUrl and lambda:InvokeFunction on arn:aws:lambda:us-east-1:061717858829:function:odigos-marketplace-issuer-pr3797-Issuer-avwccmrw5rLo (InvokeFunction via Function URL only).

2. Authenticate Helm and download this exact chart: aws ecr get-login-password --region us-east-1 | helm registry login --username AWS --password-stdin 709825985650.dkr.ecr.us-east-1.amazonaws.com helm pull oci://709825985650.dkr.ecr.us-east-1.amazonaws.com/odigos/chart --version 2026.9.28 --untar --untardir odigos-marketplace

3. With the purchasing account's AWS credentials, retrieve the token and create the Kubernetes Secret. The deployment account also needs an active Marketplace entitlement. Select its Kubernetes context first: python3 odigos-marketplace/chart/fetch-marketplace-token.py https://dmaoivlk72vrl5zct27s3h4xjq0cesyl.lambda-url.us-east-1.on.aws/token  --output odigos-marketplace-token kubectl create namespace odigos-system --dry-run=client -o yaml | kubectl apply -f - kubectl -n odigos-system create secret generic odigos-pro --from-file=odigos-onprem-token=odigos-marketplace-token --dry-run=client -o yaml | kubectl apply --server-side -f -

4. Configure IRSA for an existing service account named odigos-instrumentor in namespace odigos-system. Trust must match that service account and the cluster's OIDC provider, with audience sts.amazonaws.com. The role policy is {"Version":"2012-10-17","Statement":[{"Effect":"Allow","Action":"aws-marketplace:MeterUsage","Resource":"*"}]}. Annotate the service account with eks.amazonaws.com/role-arn set to that role. See the packaged MARKETPLACE.md. When using AWS's managed Helm launch, use the service account prepared by AWS Marketplace instead; the delivery maps its name to marketplace.serviceAccountName.

5. In odigos-marketplace/chart/values.yaml, set marketplace.serviceAccountName to odigos-instrumentor and ResourceSizePreset to size_s. Install: helm upgrade --install odigos odigos-marketplace/chart --namespace odigos-system -f odigos-marketplace/chart/values.yaml --wait --timeout 10m kubectl -n odigos-system get pods kubectl -n odigos-system port-forward svc/ui 3000:3000 Open http://localhost:3000  to select workloads and a destination. Keep the UI private. Allow outbound Marketplace metering, STS, ECR and your destination. Insights is excluded. The node agent requires privileged host access for instrumentation. Images use values.yaml repository fields for AWS regionalization.

6. Before the license expires (maximum 30 days, capped at agreement end), repeat step 3 into a new token file, update the same Secret, and restart the token-consuming workloads: instrumentor, UI and the Odiglet DaemonSet including collector sidecars. Recreate autoscaler-managed gateway pods one at a time and wait for readiness. Secret updates alone do not refresh existing environment variables. Each renewal verifies an active purchase; no renewal controller is included. Remove local token files after securely storing/applying them.

7. To uninstall, run helm uninstall odigos --namespace odigos-system and wait for its cleanup hook to finish. Retain the namespace and odigos-mp-* ledger ConfigMaps for two full UTC hours after final removal, including during reinstall, to preserve duplicate-charge protection. Do not delete the namespace to perform a same-hour reinstall. AWS billing counts distinct Ready Odiglet nodes observed during each UTC hour, including partial hours, and reports the preceding closed hour. Removal before the report can leave the last hour unbilled. Cancel the subscription after stopping the workloads if ending use. Contact support@odigos.io  for assistance.