Overview
Silverthon runs two business-critical application servers called Market Data and Market Sorter. These were running on their own on-premises infrastructure, which over time became harder to manage, harder to secure, and difficult to scale as workload demands grew.
Silverthon engaged Teleglobal International to migrate these workloads to AWS. The project covered everything from initial infrastructure assessment through to final go-live, using AWS Application Migration Service to move the servers securely with no loss of data and minimal disruption to operations.
The result is a production-ready AWS environment with proper network segmentation, centralised access controls, automated monitoring, and load balancing built in from day one.
About Silverthon
Silverthon operates workloads that need to be available, secure, and manageable. The two servers at the centre of this migration, Market Data and Market Sorter, handle important business functions that the company relies on daily.
Like many organisations that built their infrastructure on-premises years ago, Silverthon reached a point where the existing setup was holding them back. Managing physical servers manually, without centralised monitoring or identity controls, was becoming a risk rather than just an inconvenience.
The Challenge
Several things had built up over time that made the on-premises setup difficult to work with.
- No room to scale easily
Adding capacity to on-premises infrastructure takes time and money. There is no quick way to spin up more compute when workloads grow. Silverthon needed the ability to scale application servers without waiting on hardware procurement or manual setup.
- Too much manual work
Monitoring, patching, and managing infrastructure manually is fine when things are small. At a certain point it becomes a drain on the team. Silverthon needed automation and better tooling to reduce the time spent on routine infrastructure tasks.
- No central identity management
Without a proper identity and access management system, controlling who has access to what is difficult. Silverthon lacked the governance controls needed to enforce least-privilege access and keep an audit trail of who did what and when.
- Migration had to be clean
Moving business-critical servers is risky if not done properly. Silverthon needed a migration approach that would replicate their servers accurately, allow for testing before cutover, and include a clear rollback plan if anything did not go as expected.
- Network security needed work
The existing setup did not have the network segmentation or security controls that a properly architected cloud environment provides. Isolating workloads, controlling inbound and outbound traffic, and reducing the attack surface all needed to be addressed.
- High availability was not built in
On-premises setups often rely on single points of failure. Silverthon needed an architecture where traffic could be distributed and availability maintained even if individual components had issues.
Migration Approach
Teleglobal approached this as a structured four-phase migration. Each phase was planned to reduce risk and give the team visibility and control at every step.
Phase 1: Assessment and architecture design
The project started with a proper look at what existed. Teleglobal reviewed the server landscape, mapped application dependencies, and assessed compute, storage, and networking requirements. From this, an AWS architecture was designed using Amazon VPC with appropriate subnets, route tables, security groups, and IAM role definitions.
Phase 2: AWS environment setup
Before any servers were moved, the destination environment was built and configured. VPC, subnets, Internet Gateway, route tables, and security groups were provisioned. IAM users, roles, and access policies were set up with MFA and audit logging enabled. AWS MGN replication configuration was established and ready to receive incoming servers.
Phase 3: Server replication and validation
AWS Replication Agents were installed on the on-premises servers. Replication was initiated, continuously syncing server state to AWS. Once replication was stable, Teleglobal ran infrastructure validation, data integrity checks, and network and access control testing before anything was switched over.
Phase 4: Cutover and go-live
A final synchronisation was performed to bring replication up to date, then the cutover was executed. Production workloads switched to AWS. Final validation checks were run and the environment was handed over to Silverthon’s team.
The Solution
Compute
Amazon EC2 instances were provisioned to host the Market Data and Market Sorter application servers within the new AWS environment. The instances were sized and configured based on the requirements identified during assessment.
Networking
An Amazon VPC was designed with public subnets, an Internet Gateway, route tables, and security groups. This gives Silverthon proper network isolation, controlled traffic flow, and a clear security boundary around their workloads.
Identity and access management
AWS IAM was configured with role-based access control, MFA enforcement, and audit logging. This replaces informal access management with a proper governance framework where access is granted by role, can be revoked quickly, and leaves a clear audit trail.
Traffic distribution
An Application Load Balancer was set up to distribute traffic across workloads. This improves availability and means that if one component needs maintenance, traffic can continue flowing without interruption.
Monitoring
Amazon CloudWatch was configured across the environment. The team now has a single place to view infrastructure health, set alerts, and respond to issues before they become problems.
Encryption and data protection
AWS KMS was implemented for encryption key management. Data at rest and in transit is protected, and key rotation and access policies are managed centrally.
Migration tooling
AWS Application Migration Service handled the server replication from on-premises to AWS. MGN’s agent-based approach meant replication was continuous and encrypted, with no significant disruption to the on-premises servers while the migration was in progress.
AWS Services Used
| Service | What It Does in This Project |
| AWS Application Migration Service (MGN) | Continuous encrypted server replication from on-premises to AWS, with test launch and cutover capability |
| Amazon EC2 | Hosts the migrated Market Data and Market Sorter application servers |
| Amazon VPC | Private network environment with subnets, Internet Gateway, route tables, and security groups |
| Application Load Balancer (ALB) | Distributes traffic across application workloads for availability and resilience |
| AWS IAM | Role-based access control with MFA and audit logging across the AWS environment |
| AWS KMS | Encryption key management for data protection at rest and in transit |
| Amazon CloudWatch | Infrastructure monitoring, metrics, and alerting across all deployed services |
| Security Groups | Network-level access control defining allowed inbound and outbound traffic per workload |
What Changed
The migration addressed each of the problems that had been building up in the on-premises environment.
| Area | Before | After |
| Scalability | Fixed capacity, hardware-limited | On-demand EC2 scaling as workloads grow |
| Infrastructure management | Manual, time-consuming processes | Centralised, with CloudWatch monitoring and alerting |
| Access control | No central identity governance | AWS IAM with RBAC, MFA, and full audit logging |
| Network security | Limited segmentation and controls | VPC with security groups, subnets, and defined traffic rules |
| Availability | Single points of failure | Application Load Balancer for traffic distribution |
| Data protection | No centralised encryption management | AWS KMS for key management and data encryption |
“Teleglobal International provided a structured and professional migration approach that helped us transition our workloads from on-premise infrastructure to AWS with minimal disruption. The new AWS environment provides improved scalability, centralised management, and enhanced operational visibility for our business workloads.”
— Silverthon Infrastructure Team
What’s Next
With the two critical servers now running on AWS and the core infrastructure in place, Silverthon has a strong foundation to build on:
- Right-sizing EC2 instances based on actual usage patterns observed through CloudWatch
- Exploring Reserved Instance or Savings Plans pricing once workload patterns are stable
- Expanding CloudWatch coverage with custom dashboards and automated alerting
- Evaluating additional AWS security services such as Amazon GuardDuty for threat detection and AWS Config for continuous compliance monitoring
- Using this AWS foundation to support any future workloads the business wants to move to the cloud
About Teleglobal International
Teleglobal International is an IT consulting company that helps businesses move their infrastructure to the cloud. The team handles on-premises to AWS migrations, multi-cloud consolidations, and cloud architecture projects across industries. The approach is practical: assess properly, build the destination environment right, migrate cleanly, and hand over something the client’s team can actually manage.