Phase I
Actual infrastructure is running with EC2 services on East AWS. After official launch on June 3th 2018, The BP is separated into two network zones to secure a front network and a back network for increased security and service access. Each node will be monitored and managed through our NOC that uses the tool Kaseya Traverse. The service will scale on phases thanks to the scalability on Public Cloud Providers for hardware capabilities, storage and network
Phase II
A Private cloud will be created in the following configuration
- Servers: 2U with double processor, RAM of 192 GB, 2 SSD of 200 GB each and additional 8 HDD of 4 TB for the operation
- Shared storage between the servers
- Interconnection switches of 1GbE y 10 GbE interconnection
- Access switches with 1GbE y 10 GbE access connection
- High Speed Firewalls with 5 to 7 Gbps Throughput
- Uninterruptible power Supply (UPS) of 20 KV
- Isolated Power Plant for power shortage
The information obtained through the monitoring platform will give us the capability to stablish business rules and KPI’s which will allow us to take automated decisions and generate better scaling processes on real communication between our Private Cloud and Public Cloud so that we won’t depend on Internet connectivity only
Phase III
AWS scenario replicated on Azure in West US each one with Web App Firewall, DDoS security service and load balancers
Phase IV
Depending of service analysis, extra replication on each of the service providers (AWS & Azure) will extend to additional Availability Zones on Europe to expand service availability.
