liveBook · Manning

Public subnet

As explained in Secure APIs

A public subnet is a cloud network subnet with a route or configuration that permits internet connectivity.

A public subnet is a cloud network segment with internet access. It belongs to a larger segmented topology in which different subnets provide different degrees of access. section 9.2

Internet exposure changes an API’s threat model. Use public subnets as an entry boundary for hardened components such as API gateways, reverse proxies, load balancers, or WAFs, rather than placing application services directly there. Keep internal services in private subnets and connect segments only through deliberate network bridges. section 9.2

Figure 9.10 The DMZ is a region of our network that is exposed to the internet. It’s good practice to channel inbound traffic through the DMZ and keep all our services in private subnets. The DMZ can include elements such as an API gateway and bastion server.
figure

A DMZ illustrates the boundary role of an internet-exposed network region: channel inbound traffic through an API gateway or bastion server while keeping services in private subnets. section 9.2

How Secure APIs covers it

How deep it goes
Defines internet access and explains segmentation, but stops short of provider-specific configuration steps.
Examples
Illustrates public-subnet design through DMZ diagrams and cloud VPC segmentation.
What it assumes
Assumes basic cloud networking and explains subnet segmentation from a security-oriented starting point.
What you can do after
Evaluate how subnet placement affects API exposure and channel inbound traffic through hardened boundary components.
How it connects
Connects public subnets with private subnets, network segmentation, DMZs, API gateways, and bastion servers.

Also explained in

Compare how 2 books explain public subnet →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Secure APIs. The section links point to the parts of the book it draws on.