Memento Hub: CloudOps for travel technology on AWS

Operating the platform behind travel software

Memento Hub is the technology arm of Christian Tour. Its work brings together the software and infrastructure needs of a travel business. CloudHero’s responsibility was to manage the infrastructure and provide support to the developers building on it.

The engagement covered the running platform as well as the needs of the development team. Infrastructure questions and application questions often meet at the same boundary: deployment, service communication, logs or resource usage. CloudHero provided an engineering counterpart across that boundary.

CloudOps across AWS and Kubernetes

The platform combined AWS with Kubernetes and Istio. GitLab was part of the development toolset. The recorded stack also included Amazon RDS, EC2, S3, MySQL and Nginx.

These components cover distinct responsibilities. Kubernetes runs containerised workloads; AWS supplies the surrounding cloud services. Databases, storage and application traffic remain part of the operating picture alongside the cluster.

CloudHero managed the infrastructure as an ongoing CloudOps engagement. This meant the relationship extended beyond advice about which cloud services to choose: it included responsibility for the environment the developers used.

Developer support and visibility into the platform

The engagement included Elasticsearch, Fluent, Prometheus and Grafana. Together, logging and metrics make it possible to examine an application from several directions: its reported errors, the behaviour of its services and the state of the infrastructure.

Developer support was an explicit part of CloudHero’s role. Memento Hub had a team it could work with on the platform underneath its software, bringing cloud operations into the same conversation as application development.

One engagement spanning infrastructure and developers

For Memento Hub, CloudHero supplied CloudOps services across the infrastructure and support for the people building on it. The case demonstrates an engagement model for a product team that needs both platform management and hands-on engineering collaboration.

Teams considering the same model should define which infrastructure responsibilities they want a partner to own and where their developers need additional support. Those boundaries give the engagement a practical starting point.