EEhasanAWS-hostedplatformknownas‘M2MConnect’whichprovidestheirbusinesscustomerswithasolutionfortherapid,low-costdeploymentoftelemetryformachine-to-machine(M2M)services.
It first started being used in 2003, before migrating to AWS Cloud in 2013. As a legacy product, the M2M Connect service was fully reviewed, and EE outlined the following key challenges:
Availability
Legacy AWS instance types were running on old Amazon hardware, resulting in frequent Amazon maintenance alerts. With no support for high availability, downtime had to be arranged on a regular basis.
Performance
Performance bottlenecks were apparent during peak load.
Reliability
Inherent design decisions and insufficient consideration given to high availability exposed the platform to several single points of failure.
Security
The platform was non-compliant with Amazon’s standards for secure application hosting.
Management
The platform was not deployed through Infrastructure as Code (IaC) but relied on manual configuration, prone to human error.