← CloudCédric MerlinFREN

Cloud galaxy Case 2 of 7

One foot at OVH, one foot at AWS

The problem

Services running on virtual machines, paid for day and night, even when nobody is using them.

The constraint

The data stays in place and outbound traffic is controlled.

What I did

01

A private link

I connect OVH and AWS with a private link: nothing goes over the internet.

02

Containers

I split the application into containers, one per module.

03

Filtered egress

Outbound traffic is filtered.

04

One button to deploy

Teams deploy on their own, in one click.

Diagram: from two machines at OVH to containers at AWSA private link connects OVH and AWS. The four modules of the application leave OVH and become containers at AWS. Outbound traffic to the internet is filtered. One button deploys the whole thing, which shuts down at night.OVHAWSprivate linkprivate networkone container per modulefilterInternetallowed egresscontrolled egressDeployoff at night

The result

A test environment that shuts itself down at night.

Stack

  • OVH
  • AWS
  • Containers
  • Continuous deployment