Skip to content

Building an AWS Infrastructure for eventPower

For eventPower, a provider of event and conference software, makandra built a production-ready, highly available AWS infrastructure and migrated all applications to it within the planned time window.

eventPower provides companies with a toolset for preparing, planning and running events and conferences. Customers use the platform, each with their own domain and event website, plus speaker management and a conference app.

Following unreliability at their former provider, eventPower decided to move to AWS. They had also outgrown their previous, largely manually operated infrastructure: high availability was only partially in place, and automation was limited.

makandra was responsible for building a production-ready AWS setup and for migrating all applications to it.

At a Glance

Challenge

Migrating closely coupled applications to AWS within a 4-hour window without putting live operations at risk

Solution

Highly available AWS infrastructure as code, with lower costs through right sizing

Industry

Event and conference software

Technology

AWS, Rails, OpenTofu, Terragrunt, Puppet

Services

DevOps as a Service
Thank you for your hard work on our migration! It was a huge success that we could not have accomplished without your expertise and dedication.
Mike McCarthy CTO at eventPower

Key Challenges

The starting point brought several challenges at once: Existing applications were to be migrated from the former provider to AWS, and the setup was to be modernized without putting ongoing operations for existing customers at risk.

  • Lack of Redundancy
    The original setup was only partly designed with redundancy. Individual failures could affect larger parts of the platform, which no longer matched the growing requirements.
  • Manual Infrastructure Management
    Servers and configuration were managed manually and through custom scripts, which made setup and maintenance harder.
  • Limited Migration Window
    Because several applications are closely coupled, most of them had to be migrated within a single 4-hour window.
The tight migration window made careful preparation essential. Because everything was defined in code, we could test the move beforehand and go live with confidence.
Matthias Bruhse Project Lead

Our Solution for eventPower

We set up a complete, production-ready AWS environment for eventPower and migrated all applications to it within the planned time window.

Infrastructure as Code with OpenTofu and Terragrunt

Manual processes were replaced by OpenTofu, Terragrunt and Puppet, which makes the infrastructure reproducible and maintainable.

High Availability through AWS-native Services

RDS Aurora, ElastiCache, Elastic File System and Application Load Balancer provide redundancy.

Focus

AWS Cost Optimization

During the migration, the stability of the infrastructure came first. Right sizing followed as a second step, once we had usage data from live operations, which did not exist in the old setup. Based on that data, server and database sizes were adjusted without any impact on performance. Right sizing RDS and EC2 alone led to cost savings. With the optimized values, AWS Savings Plans were then purchased, long-term usage commitments that bring additional discounts. This way, infrastructure costs keep falling without eventPower giving up stability or performance.

Project Scope

Our Services for eventPower