Organize address space
Create supported networks and subnets, then connect the relevant service interfaces. Use an address plan that leaves each application dependency and administrative path understandable.
Connect / Networking
Connect the services that belong together.
Configure networks, subnets and service interfaces. Define routing, NAT and firewall rules around the traffic your application needs.
- Client → application
- Public application endpoint
- Application → database
- Configured subnet and database port
- Administrator → guest
- Restricted administration path
- Controls
- Interfaces, routes, NAT and firewall rules
Plan the allowed paths, then verify both permitted and blocked connections.
- Configuration
- Networks, subnets and service interfaces
- Traffic controls
- Routes, NAT and firewall rules
- Best fit
- Multi-service application connectivity
Application architecture / Networking
A public application. Deliberate internal connections.
Map the public entry point, application dependencies and administration path. Configure their allowed sources, protocols and ports, then test the resulting connections.
What this gives you
An application traffic map your team can understand and maintain as services change.
Where it fits
What you can do with networking.
For applications whose public entry points and private service connections need to be configured deliberately.
Define routes and NAT
Manage available route tables and NAT gateways to describe where traffic goes. The chosen network mode and address pools determine which paths the environment can provide.
Express access with firewall rules
Describe allowed traffic by the controls available in your environment. Review application listeners and guest firewalls alongside platform rules when checking access.
Follow applied configuration
Inspect the operation behind a network change and verify the connections it affects. A saved request, an applied rule and an application response describe different stages of the same change.
In practice
Give every connection a purpose.
Plan networking around the connections your application actually needs: its public entry point, private dependencies and administrative access.
A public web service
Allow traffic to the application entry point and keep administrative access limited to the intended sources.
Plan for
Listening ports, service interfaces and allowed sources.
Private application dependencies
Connect application services through supported networks and subnets. Keep a database reachable only where it is needed.
Plan for
Address ranges, routes and both allowed and denied traffic.
A controlled configuration change
Record the current route and firewall settings before changing how a workload can be reached.
Plan for
An access path, verification steps and a way to restore the previous configuration.
The workflow
From setup to everyday use.
- 01
Map traffic
Identify public entry points, internal connections and required outbound access.
- 02
Configure the network
Create the supported network resources, routes and firewall rules.
- 03
Verify reachability
Check service connectivity and observe whether configuration changes have applied.
Configuration checks
Prepare the operating environment.
- Map inbound, internal and outbound traffic before creating rules.
- Check address space for overlaps with connected environments.
- Verify connectivity after the operation applies, including connections that should fail.
Responsibilities
Know what you maintain.
Networking / Questions
A few details before you start.
Do I need a public address for every service?
Design around the entry points your application needs. Where the selected environment supports private connections, dependencies can use those paths while the public service handles incoming requests.
Does saving a rule mean traffic has changed?
Check the applied operation state and then test the connection. A saved control-plane configuration and the resulting network behavior are separate observations.
Which network options are available?
Available subnets, routes, NAT and address pools depend on the environment and service configuration. Review the offered options before relying on a particular traffic path.
Connected products