private endpoints for S3 services

[cambierr]

As a S3 service user using VRACK I want to have a dedicated S3 service access So that I can access the S3 services with a decent speed without having to pay for internet bandwidth

---

Description: All of our infrastructure hosted at OVH are based on a very simple topology, that is everything (80% dedicated, 20% cloud) in a vrack with a couple of two VMs acting as egress gateways for our traffic (We are using this since cloud gateways are not compatible with dedicated servers).

The issue is thus that, to access OVH managed S3 services, those gateways have to "proxy" all of the traffic both in ingress (fetch from S3) and egress (put to S3). From an OVH perspective, this is considered as "internet traffic" which means two things:

• First, this is limited in term of bandwidth and any augment of that bandwidth is to be paid the same price as if it was bandwidth towards internet... while this is not
• Then, on region with limited free bandwidth (such as SYD), this is invoiced with a high price while this actually is just local traffic.

To solve that issue and make the S3 service actually usable at scale, we would thus need some sort of "private" endpoint to access the service... this could be either...

• a hostname with custom resolution on a private IP (range) of the VRACK (like what we do with IPLB pack2) this is the preferred solution
• a hostname with a set of private IPs routable with public interfaces of dedicated servers with without being counted in the public bandwidth of the server)
  • for public cloud, virtual gateways should probably route it without limit of bandwidth
• just keep the current model but do NOT limit the bandwidth towards internal OVH services and do NOT count in the monthly quota of region with limited traffic
• anything else you can come up with...

Thank you guys :-)