Simple method for providing API Discovery via Distributed Cloud for APIs that are not proxied by Distributed Cloud.
This approach doesn't require an actual service response, only request traffic.
- Flow
- Outcome
- Outcome Example
- Limitations
- Requirements
- Guide
- Custom Route Template
- Load Balancer Templates
-
Path Discovery (Leaf Creation)
-
Request Sensitive Data Detection (PUT, POST)
Note - Sensitive Data Detection requires request format of JSON
Path Discovery (Leaf Creation)
Request Sensitive Data Detection (PUT, POST)
-
No Response Sensitive Data Detection
-
No Authentication Detection
-
No Performance Statistics
Note - Limitation(s) are not a result of platform capability, but an outcome of not having a proper service response
-
HTTP(S) Request Traffic
-
Distributed Cloud Tenant
-
Load Balancer
-
Route
-
API Discovery
-
Under Multi-Cloud App Connect > Manage > Virtual Host > Routes
Create a Custom Route, Configure under Routes
Add Route Match Condition
Add Route Actions, Direct Response, Configure
Update Response Body (JSON Format)
Expand Advanced Fields, Response Header to Add
Update Response Header
Save and Exit
Under Multi-Cloud App Connect > Manage > Load Balancers > HTTP Load Balancers
Created a HTTP Load Balancer, specifying your desired configuration
- Load Balancer Name
- Domains
- Load Balancer Type
Additional References @ F5 Tech Docs - HTTP Load Balacer
Add a Route, Configuration under Routes
Attach Custom Route
Enable API Discovery
Save and Exit
Custom Route Direct Response
HTTP without Managed DNS
HTTP with Managed DNS
HTTPS with Auto Certificate
HTTPS with Custom Certificate (Multiple Certificate)