New to AWS? How Koha on AWS works for libraries

If your library is new to AWS, you are not alone.

Many libraries want the flexibility and control of running Koha in AWS, but do not want to become cloud experts before they can move forward. This guide explains how Koha on AWS works in practical terms, what your library still needs to decide, and when it makes sense to use self-service or ask KohaSupport for help.

What AWS means in practice

AWS is the cloud platform where your Koha environment runs.

In practical library terms, that means:

• your Koha system runs on Amazon’s infrastructure instead of on a server in your building
• your library can choose the AWS region where the system runs
• your library can see the AWS infrastructure costs directly in its own AWS account
• your library keeps control of the environment instead of relying on a closed hosting platform

What “runs in your AWS account” means

When KohaSupport says Koha runs in your AWS account, it means:

• the AWS environment belongs to your library
• AWS bills your library directly for AWS infrastructure usage
• your library can see how the environment is set up
• your library can decide whether to stay self-service or add help later

That ownership model is one of the main differences between Koha on AWS and a traditional black-box hosting arrangement.

What KohaSupport provides

KohaSupport provides the Koha-ready AWS deployment path, documentation, and optional implementation help.

Depending on the route you choose, that can include:

• self-service CloudFormation deployment
• Standard Self-Service for live libraries in their own AWS account
• Enterprise architecture for libraries that need stronger resilience and recovery options
• Managed Services if your library wants help with setup, migration, training, or rollout

What your library still needs to decide

Even with automation, a few decisions still matter.

Your library usually needs to decide:

• whether you are evaluating, launching self-service, or planning Enterprise
• which AWS region to use
• whether you want to use your own domain name
• whether you want self-service only or help from KohaSupport
• when you want to launch and when go-live is likely to happen

You do not need to hand-build the infrastructure yourself from scratch.

What self-service looks like

Self-service is the default path.

For most libraries, that means:

• subscribe to the KohaSupport AMI in AWS Marketplace
• launch the CloudFormation template
• wait for the deployment to complete
• retrieve credentials from AWS Systems Manager Parameter Store
• complete Koha’s post-installation setup
• configure optional items such as domain names, SSL, and backups where applicable

For Free Tier and Standard Self-Service, the deployment stays deliberately simple compared with Enterprise.

What Managed Services looks like

Managed Services is available separately if your library wants hands-on help.

That can include:

• account and setup guidance if your library is new to AWS
• migration planning and implementation
• setup and configuration for your workflows
• training and onboarding for staff
• go-live planning and support

Managed Services is not a separate cloud platform. Koha still runs in your AWS account.

How the infrastructure differs by route

Free Tier

Free Tier is for evaluation, training, and small pilots.

It uses a simpler single-server design and is meant to help your library explore Koha before moving to a live setup.

Standard Self-Service

Standard Self-Service is the main live self-service option for most libraries.

It uses a simpler deployment model than Enterprise, with optional backup and domain features, while keeping the environment in your AWS account.

Enterprise

Enterprise is for libraries that need stronger resilience, recovery options, and scaling capacity.

It uses a multi-component AWS architecture rather than a single-server setup. Depending on how it is configured, that can include a load balancer, multiple application instances, Aurora Serverless v2, shared file storage, and more structured recovery options.

When self-service is realistic

Self-service is realistic if your library:

• is comfortable following documentation
• can make a few AWS choices such as region and instance size
• wants direct control of the AWS account and billing
• is happy to handle basic setup tasks or coordinate them internally

When to talk to KohaSupport instead

Talk to KohaSupport if:

• your team is new to AWS and wants a guided start
• you are migrating from another ILS
• you need help planning cutover and go-live
• you are unsure whether Standard Self-Service or Enterprise is the better fit
• you want training, configuration, or ongoing operational help

A good starting path for most libraries

If you are new to AWS, the simplest path is usually:

1. read the setup overview
2. decide whether you are evaluating or launching live
3. choose Free Tier, Standard Self-Service, or Enterprise
4. use Managed Services only if your library wants extra help

Related guides

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

Need help?

If your library is new to AWS and you want a more guided start, talk to KohaSupport.