Processing EO Data and Serving www services
In this scenario the Third Party uses: several cloud VMs as web servers (3x 8 vCores and 32 GB RAM). They are connected via virtual networks. They serve WWW services via a Firewall as Service and a Load Balancer as a Service modules.
On the other end several bare metal servers (2x 8 physical cores HT and 32 GB RAM) access EO data via file system interface and via search API. These machines make processing of the EO data to obtain results that are going to be served via web servers.
| qnty | descr | monthly | yearly budget | yearly (per month) | yearly budget | ||
| FWaaS | 52,65 | 631,80 | 45,81 | 549,67 | |||
| LBaaS | 79,65 | 955,80 | 69,30 | 831,55 | |||
| Internet access | 208,29 | 2 499,43 | 208,29 | 2 499,43 | average 100 Mbit/s of outbound traffic | ||
| VMs | 3 | eo2.xlarge | 403,96 | 4 847,47 | 233,87 | 2 806,43 | |
| BareMetal | 2 | bm.medium | 428,00 | 5 136,00 | 363,80 | 4 365,60 | |
| total: | 1172,54 | 14 070,50 | 921,06 | 11 052,67 |