Solutions

Deploy internal apps in your own AWS account

Deploying internal apps in your own AWS account means each app's service, database, files and secrets run in infrastructure your company owns, rather than on a vendor's hosting. Diakrin does this with a bring your own cloud (BYOC) model: you create one reviewed DiakrinAccess CloudFormation stack, Diakrin creates a company cloud setup from a reviewed template, and apps built with AI coding agents run on ECS on Fargate with Amazon RDS PostgreSQL and Amazon S3, after IT approves each release.

Last reviewed

Deploying internal apps in your own AWS account means each app's service, database, files and secrets live in infrastructure your company owns and can audit. Diakrin is built on this bring your own cloud (BYOC) model. Teams build apps with AI coding agents, Diakrin plans and checks each release against company policy, and the app runs in your AWS account after IT approves it.

Why run internal tools in your own AWS account?

Internal apps usually sit next to sensitive data: finance records, customer lists, employee details. When those apps run on a vendor's hosting, the data and credentials move with them. Running them in your own account keeps them under your existing AWS controls: your organization policies, your network, your encryption keys, your logs and your bill. It also fits the AWS shared responsibility model ↗, where you already own security in the cloud for your workloads.

What stays in your AWS account and what does not?

Stays in your AWS accountHeld by Diakrin
Each app's service, database, file storage, secrets and logsApp definitions, policies, approvals and memberships
Source builds, images and running appsCost accounting and audit
Row values, file contents and secret valuesSizes and names reported by the runner, such as table names and row estimates

Diakrin's data view reports what is there, never what it contains. See Manage access and security.

What access does Diakrin need in AWS?

An owner or administrator connects each AWS account once. Diakrin opens the CloudFormation page for the DiakrinAccess stack with everything filled in, and lists every role and policy and what Diakrin can never do before you create it. The stack creates three roles:

  • Reader. Read-only metadata and, if you allow it, billed cost.
  • Controller. Assumed by Diakrin to start reviewed changes.
  • Execution. Used only by CloudFormation to create resources.

Every resource Diakrin creates is tagged diakrin:managed=true, and every role it creates is capped by a permissions boundary. Diakrin never holds long-lived AWS keys. To remove all access, delete the stack.

What does Diakrin create in AWS?

A company cloud setup is the shared foundation apps run on. On AWS it comes from the AWS Container Apps template, which is pinned by version and digest and never upgrades silently.

PartAWS service
App runtimeECS on Fargate
NetworkPrivate VPC with endpoints and an internal load balancer, or an existing VPC you choose
ImagesPrivate Amazon ECR registry
DatabaseAmazon RDS PostgreSQL, encrypted, deletion-protected, with backups
FilesAmazon S3
Secrets and keysAWS Secrets Manager and AWS KMS
LogsAmazon CloudWatch

Each app adds its own service when it is deployed. Apps are published through CloudFront, and IT can give an app a company hostname with HTTPS from a certificate in your own account. See Company domains.

How it works with Diakrin

  1. Connect the account. Create the DiakrinAccess stack from Settings → Cloud accounts, then choose Verify. Diakrin checks the account, the template and every role's trust and permissions. See Set up your company cloud.
  2. Create a setup. Choose the region, Starter or Resilient, the network and a monthly budget ceiling. Diakrin shows the template, estimate and ceiling before you create it.
  3. Build an app. A builder describes it and builds it with Claude Code, Cursor or Codex. See Connect your coding tool.
  4. Build and scan in your account. The Diakrin runner builds an immutable image from an exact source commit and scans it inside your account.
  5. Approve the plan. A reviewer approves the exact image, target, cost estimate and access implications. See Preview, approve and deploy.
  6. Employees sign in. They open the app at its address with Diakrin company sign-in, which checks membership and the app's audience. See Sign in to company apps.

What should you check before you start?

  • Outbound access. The chosen private subnets need outbound HTTPS to ECR, CloudWatch Logs, Secrets Manager and S3, through a NAT gateway or your own VPC endpoints.
  • Internet gateway. CloudFront needs an internet gateway on the VPC. Diakrin uses the internet gateway already attached, or attaches a new one only if the VPC has none, and never adds routes to it, detaches it or deletes it.
  • Budget ceiling. It is the most Diakrin will approve for the estimated cost. It is not a cloud billing cap.
  • Current limits. Scheduled jobs, queues and general internet access from apps are not offered yet.

If you also need the console and API inside your own AWS account, see self-hosted internal tools.

Frequently asked questions

What does BYOC mean for internal tools?

Bring your own cloud means the vendor runs the control plane while your cloud account runs the apps and holds their data. With Diakrin BYOC, the console, API and MCP server are run by Diakrin, and apps, builds, data and secrets stay in your AWS account.

What access does Diakrin need in my AWS account?

You create one DiakrinAccess CloudFormation stack per account. It has a Reader role for read-only metadata, a Controller role Diakrin assumes to start reviewed changes, and an Execution role that only CloudFormation can use. Every created role is capped by a permissions boundary and Diakrin holds no long-lived AWS keys.

Which AWS services do apps use?

The AWS Container Apps template uses ECS on Fargate, a private VPC with endpoints, an internal load balancer, a private ECR registry, Amazon S3, Amazon RDS PostgreSQL, Secrets Manager, CloudWatch logs and a KMS key. Apps are published through CloudFront.

Can I use an existing VPC?

Yes. By default Diakrin places the setup in an existing VPC with two private subnets in different Availability Zones, or you can choose a new dedicated VPC. In an existing VPC, Diakrin creates no subnets, routes or endpoints.

Which AWS regions are supported?

The AWS template offers the current commercial AWS regions. GovCloud and China are not offered, because they need different trust roots.

How do I remove Diakrin's access?

Delete the DiakrinAccess stack. Deleting a setup in Diakrin never deletes anything in your cloud, so resources and data stay until you remove them yourself.

Sources

Facts about other products come from their public pages, checked on the dates shown. Products change; tell us if something is out of date.

See Diakrin with your own cloud

Let your team build internal apps with the AI tools they already use, while IT keeps control of identity, data, approvals and spend.