Multi-Cloud Networking with F5 Distributed Cloud

 You are a Network Engineer and you have been asked by the Application Team to help connect a application that is in the Data Center with a new cloud Front End.This Team supports internally developed traditional and modern apps, vendor provided and SaaS applications. They have started utilizing some public cloud (AWS) IaaS for several applications and have come to you with a new requirement that an on-prem backend server must be able to securely communicate with the AWS workloads over a secure connection.For lab simplicity, the backend server in the "Data Center" is a LAMP Server and needs to communicate with the AWS frontend. It could just as easily be thought of as a API to API, container to container or frontend to backend. Other backends or frontends may be added in the future.

 As the Network Engineer, you are tasked with evaluating how to securely connect the Data Center network to the AWS network. At first you consider the classic methods of deploying and managing your own IPSec solution but realize that this will be complex and costly.

 You recently saw a post on LinkedIn about a SaaS product that F5 has, claiming to solve multi-cloud network complexities. In this lab you will be taking a first-hand look at how F5 makes Multi-Cloud Networking (MCN) simple and secure.

Several of the core principles of F5 Distributed Cloud (XC) are highlighted in this lab environment.

• You will be tasked with creating two Customer Edge (CE) sites, one in a Public Cloud (AWS) and one in a private Data Center (ATC).  
• You will then securely connect each of these CE sites to F5's Regional Edges, using F5's SaaS platform. 
• Finally, you will set up routing between these sites and test the connectivity.

The goal of this lab is to show how easily it is to connect sites securely to the F5 Distributed Cloud and establish routing between these sites.

• 1 x Ubuntu Jump host which is also a KVM Hypervisor for 2 guests
• 1 x pre-installed OVA (confiured and running) as a KVM Guest which will be our DC CE
• 1 x KVM Guest which will act as our Data Center Backend Server (LAMP Server)
• 1 x Chrome Browser with the toolbar shortcuts