Dedicated AWS Deployment
Dedicated AWS is an enterprise offering. It is not self-service and is not provisioned automatically. Contact the OpsWorker team to discuss whether it fits your requirements.
Overview
A single-tenant OpsWorker instance running in a dedicated AWS account, isolated from other customers. This option is intended for organizations that need stronger isolation than the default SaaS deployment provides.
How It Works
| Component | Where It Runs |
|---|---|
| Investigation engine | Dedicated AWS account |
| Data storage | Dedicated AWS account |
| Portal | Dedicated AWS account |
| AI models | AWS Bedrock (Amazon Nova and Claude) |
| Kubernetes Agent | Your clusters |
The Kubernetes Agent works the same way as in SaaS: read-only (built-in view role), outbound-only, and communicating over SQS with an assume-role credential.
What It Offers
- Single-tenant infrastructure. No shared OpsWorker components with other customers.
- Stronger isolation. Helps meet stricter regulatory and compliance requirements.
- Dedicated support. Priority support and custom SLAs can be arranged.
Considerations
- Higher cost than SaaS because infrastructure is dedicated.
- Longer setup timeline than self-service SaaS.
- Infrastructure costs are borne by the customer, with OpsWorker handling management.
Best For
- Enterprises with strict compliance requirements
- Regulated industries that require single-tenant infrastructure
- Organizations needing custom SLAs and dedicated support
Getting Started
This deployment is arranged directly with the OpsWorker team. Contact OpsWorker to start a requirements discussion covering compliance needs, AWS region, and networking. The team will scope the architecture, deployment, and ongoing management with you.
Next Steps
- SaaS Deployment is the default model
- Private Cloud deploys in your own account (available on request)
- Security & Compliance covers the security architecture