Skip to content

Commit 73c311b

Browse files
committed
Added network diagrams
1 parent 2bd0e37 commit 73c311b

21 files changed

+2154
-973
lines changed

Diff for: docs/dedicated/networking.md

+22
Original file line numberDiff line numberDiff line change
@@ -18,3 +18,25 @@ Common configurations include:
1818
regions to provide high availability and disaster recovery.
1919

2020
To discuss your networking requirements, please contact your account manager.
21+
22+
## Example: Zuplo Ingress to Customer VPC
23+
24+
The default setup for dedicated managed Zuplo is to use your Zuplo API Gateway
25+
as the public ingress to your API. This is the simplest setup and allows Zuplo
26+
to manage things like SSL certificates on your behalf.
27+
28+
In this setup your VPC is not exposed to the public internet at all. Instead,
29+
your Zuplo API Gateway will use a network connection such as AWS Transit
30+
Gateway, PrivateLink, or VPC Peering to connect to your backend services.
31+
32+
<ZuploIngressWithManagedDedicated />
33+
34+
## Example: Customer VPC Ingress to Zuplo API Gateway
35+
36+
If you have custom networking requirements, such as using a static IP address
37+
you already own, or if you want to run services such as WAFs, IDS/IPS, or other
38+
security products in front of your API Gateway, Zuplo can be configured to
39+
accept traffic from your VPC then route it to your backend. Your backend could
40+
be in the same VPC as your ingress or in another VPC.
41+
42+
<CustomerIngressWithManagedDedicated />

0 commit comments

Comments
 (0)