Architecture
Everything below runs in your account, ineu-west-3 (Paris), the one supported region.
Networking
By default the Terraform creates a VPC (10.10.0.0/16) across two availability zones, with public and private subnets, a NAT gateway, and private endpoints for SSM, Secrets Manager, ECR and CloudWatch Logs.
You can deploy into a VPC you already run instead. You then provide two private subnets in different availability zones and outbound access, through your own route or a NAT gateway the Terraform adds.
The VPC must resolve private hosted zones through the Amazon-provided DNS resolver, because the agent reaches the dashboard service by a private name. If your VPC uses its own DNS servers or Resolver forwarding rules, read BYOC troubleshooting.
Compute and storage
The deployment uses these AWS services, all in your account:
Your security policies must allow these services in the account.
AI models
The agent calls Amazon Bedrock in your account, so prompts and model outputs never leave AWS, and Bedrock usage is billed to you.- Your account owner enables the models and accepts their Marketplace terms. Ewake gives you the current list.
- You can choose the Bedrock model behind each of the agent’s model tiers.
- The default models are EU cross-region inference profiles, which Bedrock can serve from another EU region.
Access control
- Users sign in through your own OIDC identity provider: Okta, Entra ID, Google Workspace, Auth0, or any compliant provider. Until you connect one, the dashboard shows a username and password form, for an admin password the Terraform generates into your Secrets Manager.
- The first user from your company’s email domain to sign in becomes the administrator, and grants roles to the others.
- Ewake has no access to your AWS account. Ewake staff can sign in to the dashboard only if your identity provider lets them. If you want Ewake to help operate the deployment, you grant that access yourself, with the permissions you choose, and you can remove it at any time.
Telemetry
Nothing is sent to Ewake. Application logs go to CloudWatch Logs in your account.Data security
- The database and the knowledge graph are encrypted at rest, and backed up daily in your account.
- The load balancer accepts TLS 1.2 and 1.3 only.
- Terraform state holds credentials, including SSO client secrets. Keep it in an encrypted, access-restricted bucket.
Network security
Inbound
Only these services call the deployment from the internet:- Slack
- Datadog
- incident.io
- FireHydrant
- Sentry
- GitHub
- Your CI
- Any tool you connect with a generic webhook
Deployment
- Prepare a dedicated AWS account in
eu-west-3: a delegated Route53 zone, Bedrock model access, and a Lambda memory quota of 10240 MB. - Send Ewake the account ID. Ewake grants it read access to the container images.
- Copy
terraform.tfvars.example, set your company, domain and version, and runterraform apply. The first apply takes 15 to 20 minutes. - Configure sign-in, then create your Slack app and your GitHub App.