Several of the fundamental principles of F5 Distributed Cloud (XC) are highlighted in this lab environment. You will be simulating a customer during the lab who needs to verify the safety of an application. The objective is to verify the applications safety of on-premises or application on cloud before and after enabling F5 Distributed Cloud Console WAAP Capabilities by sending attacks to the application.

In the current AI market, the demand for scalable and secure deployments is increasing. Public cloud providers (AWS, Google, and Microsoft) are competing to provide GenAI infrastructure, driving the need for multi-cloud and hybrid cloud deployments. However, distributed deployments come with challenges, including: Complexity in managing multi-cloud environments. Lack of unified visibility across clouds. Inconsistent security and policy enforcement. F5 Distributed Cloud provides a solution by offering a seamless, secure, and portable environment for GenAI workloads across clouds. This lab will guide you through setting up and securing GenAI applications with F5 Distributed Cloud on AWS EKS and GCP GKE.

Welcome to the F5 Distributed Cloud (XC) with Customer Edge Deployment mode This lab, presented by WWT and powered by F5 vesctl command line tool, will guide you through aspects of managing configuration within GCP, Kubernetes using F5 Distributed Cloud (XC) in Customer Edge deployment mode. This hands-on experience guides you through deploying a multi-cloud application across GCP, which is accessible via Private IP through an F5 By harnessing the capabilities of the F5 HTTPS Load Balancer, routing traffic within GCP environments privately.

F5 Distributed Cloud WAF deployed on Regional Edge and App Connect Deployment mode. This deployment model offers an optimal solution for scenarios where backend applications are inaccessible from the internet, lacking a Fully Qualified Domain Name (FQDN) or Public IP. In this case Customer Edge sites can be deployed to connect these "private" customer sites to the XC Global Network via IPSEC tunnels opened from Distributed Cloud Customer Edges to the closes two REs sites. Distributed Cloud WAF is deployed on the Regional Edges, where the services are being advertised to the Internet through anycast IPs. Customer Edges are being deployed on the customer sites and connect to the closest RE and traffic will be inspected by the WAAF security policy. The traffic will then be forwarded across the distributed cloud global network towards an egress Regional Edge and then over an IPSEC tunnel to the Customer edge site where it will be forwarded to the backend applications as pure IP-based traffic.