Skip to main content

Launch from AWS Marketplace

Sign in to the AWS account that will run Mitzu. The subscription and the licence belong to that account, so subscribe and launch from the same one.

Subscribe​

  1. Open the Mitzu listing in AWS Marketplace and choose View purchase options.

    The Mitzu listing in AWS Marketplace
  2. On Subscribe to Mitzu, review the offer. Under Unit configuration, enter 1 for Mitzu platform, plus any Additional seat units you need, then choose Subscribe. Mitzu won't start without the platform unit: seats on their own aren't enough.

  3. When the subscription is ready, choose Launch your software.

Launch the stack​

  1. On Launch Mitzu, choose ECS as the service. Mitzu doesn't run on EKS. The newest version is already selected.

    The Launch Mitzu page with ECS selected
  2. Under Follow the vendor's instructions, open the link that starts with https://console.aws.amazon.com/cloudformation. Quick create stack opens in CloudFormation, with the template and ImageUri already filled in.

  3. Check the region in the top right of the console. The stack launches there, and your certificate must be in the same region.

  4. Fill in DomainName, CertificateArn and AdminEmail, and HostedZoneId if you use Route 53. The other parameters are described below, and their defaults suit most teams.

    The Quick create stack form with example values
  5. At the bottom of the page, tick I acknowledge that AWS CloudFormation might create IAM resources and choose Create stack.

    The IAM acknowledgement at the bottom of the form

While it runs​

The stack takes about 15 minutes, and its status shows on the Events tab. Most of the time goes to the database and the cache. Before any service starts, a one-off task creates the database schema and your organisation, and checks your Marketplace licence. If that task fails, the stack rolls back instead of starting a broken deployment.

AdminEmail gets its invitation within a minute of the start, but the link in it doesn't work yet. Wait until the status is CREATE_COMPLETE. The Outputs tab then holds what you need next, and you can continue with First sign-in.

Parameters​

ParameterWhat to enter
ImageUriAlready filled in. Leave it as it is.
CpuArchitectureLeave ARM64. The image is built for ARM64 only.
DomainNameThe host name, for example mitzu.example.com.
CertificateArnThe ACM certificate for that name, in this region.
HostedZoneIdYour Route 53 zone, or empty to create the DNS record yourself.
OrgNameThe name of your organisation in Mitzu.
AdminEmailThe first admin. Cognito emails this address a temporary password.
EditorSeatsIgnored: seats come from your Marketplace licence.
VpcCidrThe stack's own network range.
AllowedIngressCidrWho may reach Mitzu. Default: anyone, behind sign-in.
DbInstanceClass, DbAllocatedStorageDatabase size. The defaults suit most teams.
DbDeletionProtectionKeep true; it stops the database from being deleted with the stack by accident.
AlarmEmailOptional. Receives the stack's alarms (see Operate).
SmtpHost, SmtpPort, SmtpUsername, EmailSenderOptional. The server for alert and report emails (see Operate). You can add these later.
InviteEmailSesIdentityArn, InviteEmailFromOptional. Send invites from your own SES domain (see Invite emails). You can add these later.

Outputs​

OutputUse it for
UrlThe address to open.
LoadBalancerDnsNameYour CNAME target when HostedZoneId is empty.
EgressIpThe address to allow on your data warehouses. Mitzu also shows it on the connection form.
LogGroupWhere every Mitzu container logs.
ClusterThe ECS cluster, for upgrades and restarts.
UserPoolIdThe Cognito user pool that holds your users.
AnthropicApiKeySecretArnOptional stack-wide Anthropic key (see AI and MCP).
SmtpPasswordSecretArnThe password of your SMTP server (see Operate).
SsoClientSecretArnNot needed: you enter your identity provider's secret in Mitzu.

Some output descriptions mention make commands. Those are for Mitzu's own tooling; use the pages linked above instead.