How to choose the right Koha on AWS setup

AWS gives libraries more than one way to run Koha. The best starting point depends on whether your library is still evaluating, ready for a live self-service launch, or needs a more resilient architecture.

This guide explains how to choose between Free Tier, Standard Self-Service, and Enterprise, and when Managed Services is worth adding.

Start with the simplest question

Are you still evaluating? If yes, start with Free Tier.

Are you ready to run live in your own AWS account? If yes, Standard Self-Service is the usual starting point.

Do you need stronger resilience, recovery options, or scaling capacity? If yes, evaluate Enterprise.

Do you want hands-on help? If yes, add Managed Services.

Free Tier

Best for

• evaluation
• training
• small pilots
• sandbox work before a live decision

What it looks like

Free Tier uses a simpler single-server design and is intended for evaluation rather than a full production rollout.

Good fit if

• your library is still exploring Koha
• you want a low-risk starting point
• you are not ready to commit to a live deployment yet

Standard Self-Service

Best for

• most live self-service deployments
• libraries that want Koha in their own AWS account
• libraries ready for a practical production starting point

What it looks like

Standard Self-Service keeps the environment simple enough for self-service while still giving libraries the practical pieces they usually need for a live deployment.

That can include:

• a stable public IP (Elastic IP)
• optional S3 backups
• optional custom domains using A records
• optional SSL after DNS is ready, enabled with koha-setup-domains
• credentials stored in AWS Systems Manager Parameter Store

Good fit if

• your library wants to run live
• your team can follow a guided launch process
• you want self-service as the default model
• you do not yet need a more complex Enterprise architecture

Enterprise

Best for

• libraries with stronger uptime and recovery requirements
• larger or heavier-demand environments
• libraries that need a more advanced AWS architecture

What it looks like

Enterprise uses a multi-component AWS architecture rather than a simpler single-server-style setup.

Depending on configuration, that can include:

• Application Load Balancer
• Auto Scaling Group with two or more application instances
• Aurora Serverless v2
• EFS shared storage
• optional S3 backups
• custom domains routed through the load balancer using CNAME records
• HTTPS via AWS Certificate Manager (ACM) — provide a pre-validated ACM certificate ARN at launch

Good fit if

• downtime risk matters more
• your library expects heavier use
• your library wants stronger recovery options
• your environment is operationally more demanding

Where Managed Services fits

Managed Services is not a separate architecture tier.

It is the help layer for libraries that want KohaSupport involved in:

• setup
• migration
• configuration
• training
• go-live planning
• ongoing operational help

A library can use Managed Services alongside Standard Self-Service or alongside Enterprise planning and rollout.

A practical way to choose

Choose Free Tier if:

• you are still exploring
• you want training or evaluation first

Choose Standard Self-Service if:

• you are ready for a live deployment
• your library wants self-service by default
• you want a simpler architecture than Enterprise

Choose Enterprise if:

• resilience, recovery, and scaling are higher priorities
• the library environment would be harder to support on a simpler deployment model

Add Managed Services if:

• your library wants help with the technical work
• your team is new to AWS
• migration or rollout needs guidance

Questions worth answering before launch

Before choosing a path, answer these questions:

• Is this evaluation or live use?
• How serious would downtime be?
• Does your library need a custom domain right away?
• Does your team want self-service only, or help from KohaSupport?
• Are migration and staff training part of the launch?

Related guides

• New to AWS? How Koha on AWS works for libraries
• Which Koha on AWS option is right for your library?
• Standard Self-Service Launch Checklist
• Who handles what? Self-Service, Managed Services, and AWS responsibilities
• Migrating to Koha from another library system

Need help choosing?

If your library is unsure whether Standard Self-Service or Enterprise is the better fit, talk to KohaSupport.