F5 Distributed Cloud > F5 Distributed Cloud - Service Policies & Rate Limiting Source | Edit on
Lab 1: Deploying an Application with F5 Distributed Cloud¶
Warning
If you are using multiple labs in one course, understand that some steps below may be redundant depending on labs deployed. To gain full benefits from this lab, please delete any objects created in your prior lab and continue with this lab as all necessary objects will be recreated.
Lab 1 will focus on the deployment and security of an existing hosted application using F5 Distributed Cloud Platform and Services. This lab will be deployed in a SaaS only configuration with no on-premises (public or private cloud) elements. All configurations will be made via the F5 Distributed Cloud Console and within the F5 Distributed Cloud Global Network services architecture.
For the tasks that follow, you should have already noted your individual namespace. If you failed to note it, return to the Introduction section of this lab, follow the instructions provided and note your namespace accordingly. The Delegated Domain and the F5 Distributed Cloud Tenant are listed below for your convenience as they will be the same for all lab attendees.
Delegated Domain: .lab-sec.f5demos.com
F5 Distributed Cloud Tenant: https://f5-xc-lab-sec.console.ves.volterra.io
Following the tasks in the prior Introduction Section, you should now be able to access the F5 Distributed Cloud Console, having set your Work Domain Roles and Skill levels. If you have not done so already, please login to your tenant for this lab and proceed to Task 1.
Expected Lab Time: 15 minutes
Task 1: Configure Load Balancer and Origin Pool¶
The following steps will allow you to deploy and advertise a globally available application. These steps will define an application, register its DNS and assign a target as an origin.
|
Note
You have defaulted to your specific namespace as that is the only namespace to which you have administrative access.
|
|
|
|
|
|
|
Note
The above selection controls how/where the application is advertised. The “Internet” setting means that this application will be advertised globally from the F5 Distributed Cloud Global Network utilizing Anycast.
|
|
|
|
Task 3: Testing the Application¶
You will now perform basic testing to ensure you can reach the application through the F5 Distributed Cloud platform.
|
Note
As you have not run many requests, summary analytics may not be available in the dashboard view yet.
|
|
Note
Security Event data may take 15-20 seconds to populate in the Console. Please force a refresh using the Refresh icon next to the Time Period selection in step 6.
|
|
|
Note
The available Key list to search is dynamically updated based on the requests in the selected time view.
|
|
Note
Individual forensic categories can be changed using the noted pencil icon to surface additional top data details.
End of Lab 1: This concludes Lab 1, feel free to review and test the configuration. A brief presentation will be shared prior to the beginning of Lab 2. |