SKYLIFTAI
Case Stud

Scots Guards Digital Archive: Shared Hosting to Dedicated AWS Cloud Infrastructure

A major infantry regiment of the British Army migrated its critical digital archive platform — built on Plesk, AtoM, and WordPress — from a shared hosting provider to a secure, dedicated Amazon Web Services infrastructure, with zero data loss and no unplanned downtime.

Shared Hosting → AWS EC2 Zero Data Loss GDPR Compliant AtoM + WordPress Stability First
Scots Guards
Digital Archive Migration
BE Company Shared Hosting → AWS EC2 London
2
EC2 Servers Provisioned
0
Unplanned Downtime
100%
Data Integrity Preserved
4
Migration Phases

Securing a Regiment's History for the Future

A major infantry regiment of the British Army's digital archive platform is a critical repository of regimental history. To ensure long-term security and availability of these assets, the decision was made to migrate from a shared provider to dedicated AWS infrastructure — improving resilience and performance without the risks of changing operating systems or redesigning software.

🔒
Secured & No Data Loss
The migration was executed as a fully secured operation with zero data loss. All historical records, files, and databases were moved without alteration, preserving the complete integrity of the archive.
Improved Resilience & Performance
The platform now runs on dedicated AWS infrastructure, eliminating resource contention with other tenants and providing consistent high performance, automated snapshots, and enterprise-grade uptime.
🧩
No Application Redesign Required
By migrating the existing AtoM, WordPress, and Plesk stack without OS changes or code modifications, the team avoided the risks and costs of a full rebuild while gaining all the benefits of cloud infrastructure.
🛡️
GDPR & Data Governance
Moving to a dedicated AWS environment satisfies GDPR and data governance compliance requirements, isolating the archive from third-party vulnerabilities present in shared hosting environments.
📈
Elastic Scalability
As the regiment's digital collections grow, the AWS server can be expanded instantly without requiring another migration — a critical advantage for a long-lived historical archive with growing content.
🎓
Zero Retraining Needed
The Plesk Control Panel was preserved throughout the migration, meaning customer internal teams log into the same familiar dashboard and require no new training to manage the environment.
2
Dedicated EC2 t3.large instances on AWS London region
0
Data loss events — complete historical fidelity maintained
60–70%
Faster system updates and adjustments after migration
~100%
Availability ensuring near-zero income-impacting downtime

The Technology Stack

The customer's digital archive is built on two core applications — AtoM for archival search and WordPress for the regimental website — both managed via the Plesk control panel on Ubuntu Linux.

Server Purpose Location / Cloud Instance Type OS Control Panel Applications
Main Application Server Web Applications AWS EC2 London t3.large Ubuntu 18.04.6 LTS Plesk Obsidian 18.0.52 (Web Pro) WordPress
Atom Server Archival System AWS EC2 London t3.large Ubuntu 18.04.6 LTS Plesk Obsidian 18.0.73 (Web Admin) AtoM, PHP 7.4
ComponentDetails
Domain & DNSFasthost (Shared hosting — domains only)
Cloud ProviderAmazon Web Services (AWS)
ComputeEC2 Instances (2 Servers)
Operating SystemUbuntu 18.04.6 LTS
Web StackApache + NGINX Reverse Proxy
PHP VersionPHP 7.4.33
Database EngineMariaDB 5.5.68 & MariaDB 10.4.30
SSLLet's Encrypt (Auto Renew, Partial Wildcard)
BackupsLocal Plesk Backups → AWS Automated Snapshots

Complete Digital Ecosystem Migration

The project focused on the seamless transition of the entire digital ecosystem, ensuring that "business as usual" was maintained throughout. All key application and database components were migrated for end-to-end functionality.

🗄️

AtoM (AccessToMemory)

The core archival database and public-facing search portal, providing public access to the regiment's historical records and digital collections. Migrated with complete data integrity intact.

🌐

WordPress

The primary regimental website and content management system. All content, media files, theme configurations, and plugins were transferred without alteration to the new dedicated AWS environment.

⚙️

Plesk Control Panel

The existing management interface used by administrators to maintain data integrity. All files, historical records, and databases were moved without alteration, preserving the familiar admin experience.

Infrastructure Architecture Overview

The AWS environment provides a dedicated VPC in the London region with public and private subnets, isolating the application and database tiers for security and performance.

SkyliftAI Target-Side Relay Architecture Diagram

A Structured, Phased Approach

The migration was executed using a structured, phased approach to ensure minimal risk and downtime — with strong customer involvement at every stage and formal sign-off before production cutover.

Phase 1
Discovery & Planning
Foundation

The existing environment was comprehensively assessed to understand infrastructure, applications, data, and constraints. Migration feasibility was confirmed, risks were identified, and an AWS-based target architecture was designed and formally approved before any migration work began.

Full infrastructure, application, and data inventory of the shared hosting environment
Risk identification and mitigation planning for AtoM and WordPress dependencies
AWS target architecture design: dedicated VPC, EC2 instances, subnets, security groups
Formal architecture approval and project sign-off before proceeding
Phase 2
Build & Validation
Sandbox Testing

A full sandbox environment was deployed in AWS to validate the architecture before any production data was touched. Applications and data were rigorously tested for functionality, performance, and security in the new environment, followed by formal customer review and sign-off.

AWS sandbox environment provisioned mirroring target production architecture
AtoM archival search portal tested end-to-end for functionality and data retrieval accuracy
WordPress site tested for performance, plugin compatibility, and SSL configuration
Security testing including network isolation, IAM, and firewall rule validation
Customer review session and formal sign-off before production deployment
Phase 3
Production Deployment & Cutover
Go-Live

The production environment was provisioned based on the validated design from the sandbox phase. Final testing was completed in the live environment, and a planned cutover was executed with DNS updates — achieving zero unplanned downtime during the transition.

Production EC2 instances provisioned and configured per validated architecture
All AtoM and WordPress data, files, and databases migrated without alteration
Plesk control panel configuration restored identically for seamless admin continuity
DNS cutover via Fasthost executed with planned maintenance window
Zero unplanned downtime — "business as usual" maintained throughout
Phase 4
Go-Live & Stabilisation
Outcome ✓

Post go-live monitoring, backup configuration, and operational handover were completed to ensure long-term stability and reliability. The team ensured the customer's staff were fully confident managing the new environment before closing the engagement.

Post go-live monitoring confirming performance, availability, and data consistency
Automated AWS Snapshot backup configuration replacing manual Plesk backups
Operational handover documentation and runbooks provided to the customer team
Successful migration from legacy hosting to AWS with improved performance, security, and maintainability

Minimal Change, Maximum Improvement

A core requirement of this project was to maintain the existing application functionality intact. To minimize operational risk, the following critical elements remained completely unchanged throughout the migration.

Operating System Preserved

Ubuntu 18.04.6 LTS was retained on both EC2 instances to ensure full application compatibility with AtoM and WordPress, eliminating OS migration risks entirely.

Application Logic Unchanged

No changes were made to the AtoM or WordPress code. The applications run in the new environment exactly as they did in the shared hosting setup — no rewrites, no patches.

Plesk UI Identical for Staff

The management experience via Plesk remains identical for administrators. Staff log into the exact same dashboard interface with no workflow changes or retraining required.

Database Structure Native

Data remains in its native, proven MariaDB format. No schema changes, no data transformations — the complete database structure migrated as-is with full integrity verification.

The Infrastructure Advantage

While the applications remain the same, the foundation they sit on has been significantly upgraded. Migrating from shared hosting to AWS provides five core infrastructure advantages that directly benefit the long-term viability of the archive.

8.1 · Dedicated Resources

No More Resource Contention

The platform no longer competes for CPU or memory with other organisations on the same server, leading to consistently faster page load times and higher system stability — critical for public-facing archival access.

8.2 · Enhanced Resilience

Minutes to Full Recovery

AWS provides Infrastructure Snapshot technologies, allowing for a full-server recovery in minutes should a critical error occur — replacing the previous manual Plesk backup approach with automated, enterprise-grade protection.

8.3 · Hardened Security

AWS-Grade Isolation

The environment is now protected by AWS-grade firewalls, IAM access controls, and completely isolated networking — eliminating exposure to vulnerabilities from shared tenants on legacy hosting infrastructure.

8.4 · Scalability

Elastic, On-Demand Growth

As the regiment's digital collections grow over the coming years and decades, the AWS server can be expanded instantly without requiring another disruptive migration — a fundamental advantage for a long-term archive.

8.5 · Security Compliance

GDPR & Data Governance

A dedicated hosted environment secures applications and databases from third-party vulnerabilities. Security compliance including GDPR and data governance requirements are fully satisfied by the dedicated AWS hosting model.

Bonus · Cost Visibility

Optimized Cost Management

The customer gained flexibility in managing costs with full visibility into infrastructure usage, enabling optimization over time. The pay-as-you-scale model replaces the fixed costs and hidden limitations of shared hosting plans.

Legacy Shared Hosting vs. New AWS Environment

A direct comparison of capabilities across every dimension shows the step-change improvement delivered by migrating to dedicated AWS infrastructure.

Feature ❌ Legacy Shared Hosting ✅ New AWS Environment
Server Model Shared with other organisations Dedicated to the customer, enhancing security compliance
Performance Variable — dependent on other tenants Consistent & high speed at all times
Backups Manual / Local (Plesk only) Automated AWS Snapshots — full server recovery in minutes
Control Limited by the hosting provider Full administrative control over all infrastructure
Reliability Basic — shared infrastructure SLA Enterprise-grade AWS SLA and availability
Scalability Fixed resources, limited ability to scale with traffic growth Elastic, on-demand scaling to handle peak and future workloads
Security Basic, shared security controls with limited customization Enterprise-grade security with encryption, IAM, and network isolation

Seamless Operations from Day One

The inclusion of the Plesk Control Panel within the migration ensures that customer internal teams require no new training and experience zero disruption to their established workflows.

🔧

Maintenance Continuity

Routine updates and file management continue through proven Plesk workflows. No new tools, no new processes — administrators work exactly as before with improved infrastructure underneath.

👁️

Familiar Interface

Users log into the same Plesk dashboard they are accustomed to. The management experience is identical, ensuring zero learning curve and immediate productivity from day one post-migration.

🔑

Automatic SSL Management

SSL certificates via Let's Encrypt are managed and renewed automatically in the new environment, eliminating manual certificate management and ensuring continuous HTTPS protection for all users.

A Professional-Tier Service Model for the Long Term

The migration to AWS transitions the archive to a professional-tier service model, providing the foundations for sustainable, cost-effective, and future-ready operations for decades to come.

📊

Predictable Performance

Dedicated infrastructure reduces the likelihood of downtime-related costs. With guaranteed resources on AWS, the archive delivers consistent response times regardless of what other workloads exist elsewhere on the platform.

👀

Managed Oversight

The setup allows for clear monitoring of server health, performance metrics, and security patching through AWS CloudWatch and Plesk dashboards — providing full visibility that shared hosting could never offer.

🚀

Futureproofing

By moving to the cloud leader (AWS), the customer is no longer tied to the limitations of a specific regional hosting provider. The archive can grow, scale, and evolve with AWS's expanding global service catalogue.

💰

Optimized Cost Management

The customer gained flexibility in managing costs with full visibility into infrastructure usage. This enables ongoing optimization over time, helping the regiment save money and make efficient use of their hosted infrastructure.

Six Pillars of ROI

The migration delivers measurable return across six distinct value dimensions — from eliminating security risks to enabling faster system improvements and ensuring the archive remains always accessible.

1
Reliable & Secure System
Eliminating outages and security concerns with dedicated infrastructure — no more shared vulnerabilities, no more unpredictable performance from other tenants.
2
Always Accessible
Ensuring near 100% availability to prevent income loss. The archive is publicly accessible at all times with AWS enterprise-grade uptime SLAs backing the infrastructure.
3
Faster Improvements
Accelerating system updates and adjustments by 60–70%. Dedicated resources and full administrative control mean changes can be deployed rapidly without provider restrictions.
4
Long-Term Planning & Risk Reduction
Supporting long-term planning and reducing operational risks. The archive's digital future is secured on scalable, enterprise-grade infrastructure that grows with the collection.
5
Better Profits from Digital Assets
Increasing digital asset value through improved uptime and performance. A consistently fast, always-available archive delivers more value to the regiment and the public it serves.
6
Expert, Future-Ready Configuration
Providing a scalable, enterprise-grade AWS environment configured by specialists. The regiment benefits from cloud-native best practices without needing in-house cloud expertise.

A Significant Step Forward for the Archive

The migration of the customer's digital assets to AWS represents a significant step forward. By moving the "already working" setup into a more robust environment, the archive's future has been secured without the downtime or disruption of a total rebuild.

The platform is now faster, more secure, and fully recoverable — providing a professional and stable home for the Regiment's historical record for years to come. The Stability First approach ensured zero disruption to operations while delivering a foundational infrastructure upgrade that will serve the regiment for decades.

Faster
Dedicated resources, no contention
Secure
AWS-grade isolation & GDPR compliant
Recoverable
Full snapshots, minutes to restore

Your Data.
Any Cloud. Any Time.

Ready to migrate your critical infrastructure to AWS with zero data loss and minimal disruption? Talk to a SkyliftAI expert today.

Get Started Today