# Forward Proxy

A forward proxy is an intermediary that makes outbound connections to destination servers on behalf of clients.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/forward-proxy

> A forward proxy provides a controlled point through which clients access external resources, allowing organizations to enforce destination policies, authenticate clients, and record outbound activity. In cloud networks, it helps secure internet-bound traffic, but effective enforcement also requires preventing workloads from bypassing the proxy.

Practice exams covering Forward Proxy: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of Forward Proxy

Forward proxies centralize client egress policy, but their effectiveness depends on protocol visibility, bypass prevention, and resilient operation.

1. **Client-side mediation**: The proxy connects to destinations on behalf of clients, creating a separate outbound connection. Unlike a reverse proxy, it governs access originating from clients rather than publishing an application to callers.
2. **Application-aware outbound policy**: A proxy can permit approved destinations, restrict methods or ports, and authenticate clients when supported. Match controls to the protocol visibility available rather than assuming every proxy can inspect every request.
3. **Explicit or transparent deployment**: Explicit deployments require application configuration and proxy support. Transparent deployments require compatible interception software and traffic steering; route changes alone do not provide proxy functionality.
4. **Encryption-aware inspection**: HTTPS tunneling allows destination-level authorization without exposing encrypted request contents. Payload inspection requires TLS termination, trusted certificates, and compatibility testing.
5. **Bypass-resistant enforcement**: Restrict workload connectivity so applications cannot circumvent the proxy using direct internet connections or alternative network paths. Account for IPv6, DNS behavior, and protocols that do not support the selected proxy.
6. **Availability and accountable logging**: Distribute capacity across failure domains and test whether outages fail closed as required. Record client identity, destination, and policy decisions while limiting exposure of sensitive data.

## Cloud services for Forward Proxy

Amazon EC2 can host the forward proxy that authorizes client requests and records outbound activity. A public NAT gateway can provide internet connectivity for proxy instances in private subnets, while workload connectivity is restricted to prevent direct bypass. AWS Network Firewall can add network-level controls along the egress path. For transparent appliance designs, Gateway Load Balancer steers traffic to compatible inspection appliances rather than acting as an explicit proxy itself. These components have distinct roles: proxying mediates client requests, firewalling enforces traffic rules, load balancing distributes appliance flows, and NAT translates addresses. Routing and return paths must preserve any required stateful inspection.

- **[Amazon EC2](https://blowstack.com/tools/cloud-services-hub/amazon-ec2)**: EC2 instances can host forward-proxy software for explicit client access or supported transparent deployments. Engineers manage software configuration, patching, capacity, authentication, and availability.
- **[AWS Network Firewall](https://blowstack.com/tools/cloud-services-hub/aws-network-firewall)**: AWS Network Firewall provides managed network filtering that can complement proxy-based egress controls and restrict unauthorized paths. Its supported TLS inspection capabilities are separate from operating an explicit HTTP forward proxy.

## Forward Proxy exam questions

Real practice exam questions on Forward Proxy, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company runs build workers on dual-stack Amazon EC2 instances in private subnets. The subnet route tables provide IPv4 internet access through a NAT gateway and IPv6 internet access through an egress-only internet gateway. The workers run third-party build scripts.

The company has deployed an explicit HTTP forward proxy on separate EC2 instances in the same VPC. The proxy listens on TCP port 3128, permits HTTPS CONNECT requests only to approved repository hostnames, and denies other destinations. The build tools are configured to use the proxy's private IPv4 endpoint. However, a security test shows that a build script can ignore the proxy settings and download files directly from an unapproved internet destination.

The workers and proxy instances each have a dedicated security group, with no additional security groups attached. The workers need no outbound application connections other than connections to the proxy. The proxy already has working internet connectivity.

Which change will enforce the destination policy for HTTPS downloads over both IPv4 and IPv6?

**Correct answer:** Replace all worker security group outbound rules with a single rule allowing TCP port 3128 to the proxy security group. Allow that traffic inbound on the proxy security group, and retain the proxy's required outbound internet access.

**Explanation:** The workers can establish application connections only to the proxy instances on the proxy port. Removing both IPv4 and IPv6 allow-all egress rules prevents direct HTTPS connections through either internet path. The proxy establishes a separate connection to each permitted destination and enforces the CONNECT hostname policy. Security groups automatically permit response traffic for allowed connections.

## Practice Forward Proxy in a full exam

Questions on Forward Proxy in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 1 question

## What is Forward Proxy

A forward proxy acts on behalf of clients rather than the servers they contact. A workload connects to the proxy, and the proxy establishes a separate connection to the destination. This creates a policy enforcement point between internal applications and external services. A reverse proxy serves the opposite role: it receives requests on behalf of destination applications. The distinction is about which side the intermediary represents, not whether it runs in a public or private subnet.

Forward proxies commonly control outbound HTTP and HTTPS traffic. An explicit proxy requires clients to know its address, typically through application settings, proxy environment variables, or automatic configuration. Support varies by application and library; setting HTTPS\_PROXY does not guarantee that every process uses it. A transparent deployment steers traffic through a compatible interception appliance without explicit client configuration, but requires careful routing and protocol support. An ordinary HTTP proxy cannot become a transparent proxy merely by making it a route-table target.

For example, build workers in private AWS subnets might need access to approved package repositories but not arbitrary internet destinations. Engineers can run proxy software on Amazon EC2, configure the workers to use its private endpoint, and restrict workload egress to that endpoint and other required private services. The proxy permits approved repository destinations and denies other requests. Its own internet connectivity can use a public NAT gateway or another suitable egress design. Workloads should not retain an alternative unrestricted internet path over either IPv4 or IPv6.

HTTPS requires particular care. With HTTP CONNECT, the proxy can authorize a tunnel using the requested destination hostname and port, but the application payload remains encrypted between client and server. The proxy cannot automatically inspect URL paths, headers, or downloaded files inside that tunnel. TLS interception requires terminating client TLS and creating a separate upstream TLS connection. Clients must trust the inspection certificate authority, and certificate pinning or mutual TLS can make interception incompatible with an application. Inspection also introduces privacy, certificate-management, and compliance obligations.

A NAT gateway is not a forward proxy: it translates network addresses without providing application-aware request authorization. AWS Network Firewall can enforce network and supported application-layer policies, but it is not an explicit HTTP proxy endpoint. Gateway Load Balancer distributes traffic to compatible network appliances; the appliances, not the load balancer, supply inspection or proxy behavior. These components can complement a forward proxy rather than replace its specific functions.

Operationally, deploy enough proxy capacity across Availability Zones, monitor connection counts and resource usage, and test failover behavior. Decide whether failures must block outbound access rather than permit bypass. Protect against becoming an open proxy by restricting reachable clients, authenticating where appropriate, and denying unnecessary destinations, including sensitive internal addresses. Centralized egress improves policy consistency and auditability, but adds latency, processing costs, and a shared dependency. Proxy logs should capture useful policy decisions while protecting credentials and sensitive request data.
