Dedicated AWS Deployment
Overview
A single-tenant OpsWorker instance running in a dedicated AWS account, completely isolated from other customers. Provides maximum isolation with full customization options.
How It Works
| Component | Where It Runs |
|---|---|
| Investigation engine | Dedicated AWS account |
| Data storage | Dedicated AWS account |
| Portal | Dedicated AWS account |
| AI models | Configurable (Bedrock, Azure OpenAI, BYO LLM) |
| Kubernetes Agent | Your clusters |
Benefits
- Complete isolation — Single-tenant infrastructure, no shared components
- Custom configuration — LLM provider, data retention, region, scaling
- Maximum compliance — Meets the strictest regulatory requirements
- Dedicated support — Priority support and custom SLAs
- Custom networking — PrivateLink, VPN, or direct connect options
Considerations
- Higher cost than SaaS (dedicated infrastructure)
- Longer setup timeline
- Infrastructure costs borne by customer (with OpsWorker management)
Best For
- Large enterprises with strict compliance requirements
- Regulated industries requiring single-tenant infrastructure
- Organizations needing custom SLAs and dedicated support
Getting Started
Contact the OpsWorker team to discuss your dedicated deployment requirements:
- Requirements assessment (compliance, region, LLM, networking)
- Architecture planning and approval
- Deployment and configuration
- Ongoing management and support
Next Steps
- Private Cloud — Deploy in your own account
- Security & Compliance — Security architecture details