A cultural platform
that crashed when people
needed it most.
The Subsecretaría de las Culturas y las Artes document manager — hosting thousands of books and cultural content for public download — couldn't scale. The on-premise platform built on WordPress and DSpace crashed under traffic. We executed a re-platform migration to AWS with native services, delivering the scalability and resilience that access to public culture deserves.
A document platform
that couldn't handle demand.
Inaccessible digital cultural heritage serves no one. And a platform that crashes when the most people try to access it is exactly that.
On-Premise with No Scalability or Resilience
Access to culture, at risk
The Subsecretaría de las Culturas y las Artes maintained its document manager — thousands of books in multiple formats for public download — on on-premise infrastructure built on WordPress and DSpace. The system couldn't scale: when traffic increased, the platform crashed. The cultural content existed, but it wasn't reaching the people who needed it.
Traffic Spikes with No Response
Demand the infrastructure couldn't handle
The on-premise architecture had no capacity to adjust dynamically. Every cultural campaign, academic period, or event that increased traffic was a real threat to service availability.
Fixed VMs, High Costs
Expensive infrastructure that doesn't scale
Maintaining virtual machines to sustain the platform meant high operational costs and constant administrative overhead — without guaranteeing availability during critical moments.
Not just moving to the cloud.
Actually adopting it.
A re-platform isn't copying on-premise infrastructure to the cloud — it's redesigning it to leverage native services and let AWS manage what shouldn't be managed manually.
Native AWS Migration — Not a Lift-and-Shift
We proposed and executed a re-platform migration: taking the existing elements — WordPress, DSpace, and all content — and moving them to AWS by adopting native services rather than replicating the same VMs in the cloud. This transfers infrastructure management to the cloud provider and eliminates the operational burden from the internal team.
EC2 + ELB + RDS + EFS: The Right Stack for Digital Content
We implemented a High Availability architecture with EC2 for elastic compute, Elastic Load Balancer to distribute traffic across instances, RDS for the managed relational database, and EFS for shared file storage — ideal for a download platform with thousands of documents. Every service managed by AWS, not by the Subsecretaría's IT team.
Scalability, Resilience, and Reduced Costs
The migrated platform scales automatically with traffic, maintains availability during demand peaks, and eliminated the need to manually manage instances. Operational costs dropped by replacing fixed VMs with managed services that are paid based on actual usage — no overprovisioning, no shortfalls.
A platform that now
scales with culture.
Subsecretaría de las Culturas y las Artes
Government of Chile · Public Sector
On-Premise with No Scale
Document management platform (WordPress + DSpace) on on-premise infrastructure. No ability to scale under traffic spikes, site crashes, and high operational costs from manual VM management.
Re-platform to Native AWS
Re-platform migration of WordPress and DSpace to native AWS services. High Availability architecture with EC2, Elastic Load Balancer, RDS, and EFS — management delegated to the cloud provider.
Guaranteed Scalability and Resilience
Platform that scales automatically with traffic. Operational continuity during demand peaks. Reduced costs by eliminating fixed VMs. IT team freed from infrastructure management.
Technologies
deployed.
The AWS stack used to bring the cultural platform to the cloud with native services.
Is your on-premise platform
struggling under traffic?
We execute re-platform migrations to AWS with native services — scalability, resilience, and cost reduction from day one. Let's talk.
Schedule a meeting →