Meta tags:

Headings (most frequently used words):

and, affinity, http, service, support, session, backends, load, based, backend, for, in, cookie, balancer, vpc, cross, project, client, internal, application, of, networks, tls, the, header, timeout, with, resources, shared, referencing, retries, failover, limitations, console, gcloud, proxy, forwarding, ip, health, rules, region, over, protocol, example, frontend, projects, keepalive, balancers, overview, stay, organized, collections, save, categorize, content, on, your, preferences, modes, operation, architecture, gke, architectures, timeouts, accessing, connected, websocket, grpc, what, next, identify, mode, only, subnet, rule, address, target, ssl, certificates, url, maps, checks, firewall, access, api, types, losing, high, availability, cleartext, tcp, mutual, products, pricing, engage, forwarded, handling, preserving, ips, intermediate, proxies, scope, to, network, interfaces, subsetting, check, all, components, serverless, environment, usage, notes, different, host, hash, meaning, zero, ttl, affinities, regional, max, concurrent, streams, dynamic, table, size, none, generated, stateful,

Text of the page (most frequently used words):
the (832), load (421), #balancer (308), and (240), #backend (233), for (154), application (153), internal (145), service (137), http (137), backends (109), you (107), can (103), region (101), that (91), affinity (89), with (88), instance (88), vpc (86), cloud (83), network (80), regional (77), proxy (77), balancers (74), use (74), client (69), session (67), cookie (65), from (63), cross (62), address (62), set (61), google (58), project (56), must (56), same (56), are (54), following (53), traffic (53), your (52), based (49), forwarding (48), this (47), timeout (46), managed (46), balancing (44), using (44), subnet (42), neg (42), clients (40), rule (40), see (39), only (38), overview (38), group (38), configure (37), negs (37), requests (37), when (36), mode (36), value (35), tcp (35), header (35), support (34), between (34), health (34), more (33), services (32), shared (31), https (31), supported (31), other (29), information (29), access (29), connection (29), protocol (28), zonal (28), any (27), tls (27), request (27), all (26), global (26), uses (25), target (25), certificates (25), url (25), type (25), endpoint (24), ipv6 (24), default (23), create (23), certificate (22), hybrid (22), envoy (21), one (21), not (21), ssl (21), over (21), seconds (21), keepalive (21), each (20), multiple (20), connections (19), custom (19), configured (19), response (19), frontend (19), check (19), its (18), table (18), used (17), instances (17), map (17), rules (17), doesn (16), server (16), might (16), headers (16), selected (16), groups (16), websocket (15), serverless (15), time (15), run (15), addresses (15), compute (15), external (15), deployment (15), healthy (15), checks (15), ttl (15), send (14), example (14), projects (14), different (14), host (14), policies (13), types (13), isn (13), either (13), mtls (13), proxies (13), failover (13), dns (13), routing (13), components (13), management (13), number (12), networks (12), both (12), where (12), also (12), required (12), specific (12), endpoints (12), stateful (12), generated (12), connected (12), terms (11), architecture (11), resources (11), idle (11), requirements (11), subnets (11), gke (11), reference (11), allow (11), single (11), regions (11), vip (11), policy (11), none (11), internet (11), referencing (10), within (10), there (10), grpc (10), created (10), configuration (10), than (10), add (10), localitylbpolicy (10), always (10), which (10), buckets (10), forwarded (10), don (9), engine (9), long (9), setting (9), feature (9), maximum (9), values (9), need (8), how (8), have (8), section (8), specify (8), open (8), port (8), manager (8), console (8), aren (8), features (8), then (8), h2c (8), communicate (8), source (8), available (8), high (8), defined (8), includes (8), hash (8), admins (8), premises (8), firewall (8), capabilities (8), code (7), thumb (7), down (7), after (7), changes (7), software (7), subsetting (7), resource (7), name (7), instead (7), new (7), distributed (7), these (7), click (7), enlarge (7), located (7), shows (7), availability (7), break (7), autoscaling (7), capacity (7), has (7), specifies (7), ranges (7), connectivity (7), stack (7), authorization (7), storage (7), about (6), options (6), insert (6), private (6), running (6), flag (6), valid (6), rfc (6), range (6), remain (6), enable (6), protocols (6), classic (6), automatically (6), require (6), describes (6), upgrade (6), regiona (6), references (6), two (6), want (6), route (6), deploy (6), remove (6), means (6), across (6), such (6), explicitly (6), maglev (6), parameter (6), consistenthash (6), packet (6), associated (6), intermediate (6), peering (6), downstream (6), amount (6), supports (6), pre (6), maps (6), except (5), details (5), enabled (5), data (5), path (5), connect (5), through (5), next (5), non (5), api (5), error (5), environment (5), gcloud (5), communication (5), mutual (5), itself (5), standard (5), those (5), controller (5), returns (5), logs (5), because (5), streams (5), settings (5), modes (5), sends (5), fails (5), whether (5), distribution (5), behavior (5), losing (5), web (5), entire (5), second (5), nanoseconds (5), 600 (5), remains (5), field (5), original (5), nat (5), share (5), examples (5), close (5), packets (5), they (5), however (5), user (5), roles (5), diagram (5), gce_vm_ip_port (5), ingress (5), tunnels (5), attachments (5), scheme (5), troubleshooting (5), metrics (5), redirect (5), português (4), español (4), events (4), understand (4), content (4), without (4), closed (4), into (4), standalone (4), first (4), 100 (4), retry (4), version (4), sent (4), authentication (4), during (4), helps (4), before (4), terminating (4), end (4), logging (4), gateway (4), encryption (4), rate (4), monitoring (4), dynamic (4), initial (4), many (4), contains (4), provides (4), full (4), another (4), return (4), closest (4), virtual (4), get (4), best (4), automatic (4), unhealthy (4), least (4), removes (4), case (4), depending (4), fractions (4), specified (4), affinitycookiettlsec (4), httpcookie (4), product (4), needs (4), match (4), destination (4), security (4), vpn (4), retries (4), modify (4), minutes (4), update (4), recommend (4), role (4), organization (4), control (4), optional (4), probes (4), probe (4), limited (4), dual (4), ipv4_ipv6 (4), internal_managed (4), method (4), tools (4), view (4), monitor (4), troubleshoot (4), terraform (4), manage (3), samples (3), system (3), status (3), last (3), negotiate (3), logic (3), functions (3), app (3), reserve (3), shared_loadbalancer_vip (3), 1918 (3), guarantee (3), systems (3), limitations (3), authenticate (3), handshake (3), industry (3), ensure (3), authority (3), requires (3), accepts (3), still (3), some (3), make (3), sure (3), handle (3), part (3), extension (3), cases (3), but (3), important (3), cleartext (3), represented (3), per (3), lets (3), result (3), hpack (3), compression (3), making (3), size (3), performance (3), advertised (3), determine (3), zero (3), regionb (3), gracefully (3), accessible (3), geolocation (3), 503 (3), passes (3), constant (3), occurs (3), existing (3), autohealing (3), ways (3), attribute (3), expires (3), affected (3), locality (3), directs (3), cannot (3), live (3), strong_cookie_affinity (3), implied (3), ring_hash (3), inclusive (3), 999999999 (3), http_cookie (3), generated_cookie (3), header_field (3), receive (3), tuple (3), client_ip (3), select (3), weighted (3), retried (3), responses (3), configurable (3), keepalive_timeout (3), keepalivetimeout (3), common (3), greater (3), possible (3), called (3), represents (3), command (3), process (3), complete (3), loadbalancerserviceuser (3), usage (3), maintain (3), costs (3), development (3), documentation (3), vlan (3), disabled (3), summarizes (3), ngfw (3), allocated (3), scope (3), subject (3), offerings (3), general (3), launch (3), stage (3), descriptions (3), preview (3), interfaces (3), nic0 (3), ipv4 (3), association (3), self (3), ephemeral (3), tier (3), identify (3), globally (3), enables (3), concepts (3), guides (3), networking (3), explore (3), tutorials (3), directory (3), registration (3), udp (3), migrate (3), 한국어 (2), 日本語 (2), עברית (2), brasil (2), italiano (2), indonesia (2), français (2), américa (2), latina (2), deutsch (2), english (2), sign (2), third (2), cookies (2), site (2), youtube (2), center (2), started (2), notes (2), community (2), pricing (2), products (2), updated (2), 2026 (2), utc (2), otherwise (2), page (2), licensed (2), under (2), apache (2), license (2), feedback (2), timeouts (2), follow (2), periodically (2), restarts (2), serving (2), longer (2), additional (2), extensions (2), apis (2), container (2), native (2), gateways (2), setup (2), inside (2), purpose (2), public (2), directly (2), underlying (2), entirety (2), implement (2), relying (2), periods (2), known (2), exactly (2), connecting (2), later (2), cli (2), cdn (2), zone (2), trust (2), issued (2), unlike (2), authenticated (2), present (2), established (2), accept (2), unsecured (2), transformed (2), additionally (2), encrypted (2), http2 (2), negotiates (2), alpn (2), applications (2), independent (2), latency (2), framework (2), special (2), significantly (2), reduces (2), improves (2), like (2), faster (2), could (2), concurrent (2), forward (2), settings_max_concurrent_streams (2), even (2), websockets (2), works (2), 502 (2), duration (2), related (2), follows (2), particular (2), detect (2), responding (2), outage (2), most (2), optimal (2), achieve (2), checking (2), among (2), transitioning (2), total (2), empty (2), adds (2), situations (2), does (2), assign (2), treats (2), definition (2), varies (2), affinities (2), removed (2), unless (2), methods (2), plus (2), 209 (2), done (2), mapping (2), index (2), met (2), nanos (2), units (2), parameters (2), provided (2), gcilb (2), httpheadername (2), conditions (2), delivered (2), effective (2), vms (2), others (2), keep (2), mind (2), forwards (2), hashing (2), consists (2), option (2), determines (2), them (2), whenever (2), configuring (2), splitting (2), note (2), further (2), interconnect (2), post (2), body (2), necessary (2), gfe (2), fin (2), race (2), condition (2), reset (2), rst (2), stay (2), perspective (2), permitted (2), 610 (2), regionbackendservices (2), 500 (2), file (2), deliver (2), sending (2), byte (2), grant (2), who (2), here (2), therefore (2), unique (2), names (2), owners (2), their (2), iam (2), teams (2), while (2), organizations (2), central (2), optimize (2), quota (2), model (2), attached (2), well (2), including (2), ips (2), read (2), combination (2), permits (2), list (2), typically (2), originate (2), interface (2), hub (2), handling (2), unmanaged (2), back (2), take (2), passthrough (2), incoming (2), appends (2), come (2), record (2), way (2), allocates (2), meet (2), specification (2), comparison (2), static (2), delete (2), differences (2), premium (2), implemented (2), multi (2), fail (2), sdk (2), languages (2), frameworks (2), infrastructure (2), observability (2), migration (2), solutions (2), multicloud (2), databases (2), analytics (2), pipelines (2), hosting (2), pools (2), tags (2), optimizations (2), workload (2), identity (2), pool (2), convert (2), constraints (2), technology (2), areas (2), subscribe, newsletter, our, decade, climate, action, join, privacy, tech, twitter, blog, engage, training, certification, getting, github, release, forums, contact, sales, marketplace, easy, easytounderstand, solved, problem, solvedmyproblem, otherup, hard, hardtounderstand, incorrect, sample, incorrectinformationorsamplecode, missing, missingtheinformationsamplesineed, otherdown, tell, noted, java, registered, trademark, oracle, affiliates, developers, creative, commons, attribution, learn, active, tasks, likely, task, replacements, will, terminate, classified, categories, pods, attaching, deploying, what, trace, 1st, gen, named, reserved, omit, dynamically, allocate, literal, utilized, privately, creating, doing, triggers, validation, stating, deployed, issue, warn, runs, out, compatible, reduce, zones, store, validate, chain, verifying, holds, trusted, confirming, identities, parties, unencrypted, configurations, layered, design, designing, accurate, efficient, language, developing, mobile, low, highly, scalable, remote, procedure, calls, include, mesh, string, 7540, volume, visible, report, 200, push, stream, 8441, pooling, optimization, latencies, made, frequently, upon, multiplexing, enhances, everything, impact, improve, bug, various, libraries, cause, issues, refer, article, respects, direction, frame, simultaneously, advertises, higher, errors, initiated, peer, effectively, meaningless, initiate, max, modern, controlled, major, revision, closes, 426, bidirectional, current, 101, switching, recognizes, followed, relevant, duplex, channel, 6455, ensuring, stays, outages, vips, geographically, benefits, individual, routes, origin, spanning, becomes, redirected, removing, just, adding, component, fullness, change, unpredictable, should, minimize, utilization, treat, discarding, immediately, browsers, retain, browsing, persists, until, meaning, identifies, encoding, subsequent, representing, weeks, strongsessionaffinitycookie, 315576000000, slash, applies, true, routed, distribute, processed, being, performed, mean, eligible, fields, calculate, consistent, algorithm, flags, rely, purposes, takes, precedence, according, round_robin, outlines, discussed, detail, effort, attempt, previously, detailed, accessing, generate, log, entry, final, unsuccessful, once, 504, hours, pertrytimeout, numretries, 620s, 75s, nginx, 620, recommended, lists, less, avoids, operating, fixed, changed, maintains, period, termination, secondary, defines, apply, occur, considers, happens, responds, 1200, timeoutsec, larger, practical, 147, 483, 647, longest, expect, order, increase, download, expects, insufficient, situation, received, much, obtain, waits, corresponding, allowed, returning, hasn, returned, limit, remaining, dropped, description, differentiate, environments, autonomy, exposure, users, achieved, having, functional, separation, focus, building, provision, hundreds, centrally, associate, hostnames, needed, lower, manageability, operational, backing, separate, administration, responsibilities, desired, comes, primary, referenced, regardless, securely, efficiently, already, familiar, architectures, ingresses, choosing, gatewayclass, protect, essentials, originates, translated, manually, allowing, certain, exceptions, why, regionhealthchecks, healthchecks, although, practice, whose, matches, accurately, tests, contrast, succeed, allows, reach, centralized, mechanism, monitors, readiness, risk, working, enabling, scalability, assigning, subset, whatever, vnics, import, export, filters, ncc, spokes, ipv4_only, since, exchanges, satisfy, added, template, restrictions, depend, deployments, combinations, signals, exception, iap, armor, fall, unable, backendservices, indicates, direct, regionurlmaps, urlmaps, determination, attributes, decision, actions, rewriting, redirects, keys, untouched, inject, verified, reliably, preserve, recommendations, reaching, stripped, preserving, append, untrusted, strips, prevent, spoofing, alter, sanitization, stripping, employs, measures, account, proxied, own, recorded, preserved, connects, regiontargethttpsproxies, regiontargethttpproxies, targethttpsproxies, targethttpproxies, preserves, terminates, consults, specifying, random, prefix, allocation, ipv6_only, ula, exist, taken, been, thus, explicit, implicit, forwardingrules, globalforwardingrules, depends, ports, overall, 65535, sometimes, records, let, newly, assigned, described, below, regional_managed_proxy, global_managed_proxy, previous, behalf, edit, output, describe, forwarding_rule_name, tab, blank, optionally, balanced, rich, balance, directed, relative, placing, avoid, failures, operation, layer, scale, behind, distributes, hosted, variety, platforms, kubernetes, document, introduces, save, categorize, preferences, organized, collections, home, clean, audit, operate, draining, advanced, customize, quantum, secure, switch, spoke, hop, party, appliances, hops, testing, published, domain, improved, protection, practices, rewrite, query, roll, bucket, permissions, choose, discover, start, free, skip, main,

Text of the page (random words):
p udp overview external load balancer regional load balancer backend service based architecture traffic distribution concepts target pool based architecture set up a load balancer vm instance group backends tcp udp only vm instance group backends multiple protocols zonal neg backends target pool based load balancer add capabilities configure failover configure weighted load balancing migrate from target pools to backend services service directory registration explore tutorials use udp with network load balancers monitor and troubleshoot view logs and metrics troubleshooting internal load balancer architecture overview traffic distribution concepts set up load balancer terraform examples vm instance group backends vm instance group backend for multiple protocols zonal neg backends add capabilities configure failover zonal affinity load balancers as next hops overview set up load balancing for third party appliances forwarding rules that use a common ip address service directory registration load balancing and connected networks explore tutorials set up load balancer as next hop with tags deploy a hub and spoke network set up a load balancer with internal ipv6 only backends monitor and troubleshoot view logs and metrics troubleshooting protocol forwarding overview set up protocol forwarding switch between a target instance and a backend service secure ssl certificates overview use self managed ssl certificates use google managed ssl certificates encryption to the backends troubleshooting ssl policies overview use ssl policies mutual tls frontend mtls overview set up frontend mtls with user provided certificates set up frontend mtls with a private ca backend mtls overview set up backend authenticated tls set up backend mtls backend mtls with managed workload identity overview set up backend mtls using managed workload identity post quantum tls authorization policies overview set up authorization policies customize load balancer advanced load balancing optimizations backend buckets backend services connection draining firewall rules forwarding rules health checks overview use health checks internal dns names ipv6 network endpoint groups overview hybrid connectivity negs internet negs serverless negs zonal negs overview set up zonal negs proxy only subnets tags target pools target proxies url maps overview use url maps url map size and quota units operate and maintain audit logging information health check logging information clean up a load balancer setup ai and ml application development application hosting compute data analytics and pipelines databases distributed hybrid and multicloud industry solutions migration networking observability and monitoring security storage access and resources management costs and usage management infrastructure as code sdk languages frameworks and tools home documentation networking load balancing guides send feedback internal application load balancer overview stay organized with collections save and categorize content based on your preferences this document introduces the concepts that you need to understand to configure internal application load balancers a google cloud internal application load balancer is a proxy based layer 7 load balancer that enables you to run and scale your services behind a single internal ip address the internal application load balancer distributes http and https traffic to backends hosted on a variety of google cloud platforms such as compute engine google kubernetes engine gke and cloud run for details see use cases modes of operation you can configure an internal application load balancer in the following modes cross region internal application load balancer this is a multi region load balancer that is implemented as a managed service based on the open source envoy proxy the cross region mode enables you to load balance traffic to backend services that are globally distributed including traffic management that helps ensure that traffic is directed to the closest backend relative to the forwarding rule this load balancer also enables high availability placing backends in multiple regions helps avoid failures in a single region if one region s backends are down traffic can fail over to another region regional internal application load balancer this is a regional load balancer that is implemented as a managed service based on the open source envoy proxy the regional mode requires that backends be in a single google cloud region clients can be limited to that region or can be in any region based on whether global access is disabled or enabled on the forwarding rule this load balancer is enabled with rich traffic control capabilities based on http or https parameters after the load balancer is configured it automatically allocates envoy proxies to meet your traffic needs the following table describes the important differences between cross region and regional modes load balancer mode feature virtual ip address vip of the load balancer client access load balanced backends high availability and failover cross region internal application load balancer allocated from a subnet in a specific google cloud region vip addresses from multiple regions can share the same global backend service you can configure dns based global load balancing by using dns routing policies to route client requests to the closest vip address always globally accessible clients from any google cloud region in a vpc can send traffic to the load balancer global backends load balancer can send traffic to backends in any region automatic failover to healthy backends in the same or different regions regional internal application load balancer allocated from a subnet in a specific google cloud region not globally accessible by default you can optionally enable global access regional backends load balancer can only send traffic to backends that are in the same region as the proxy of the load balancer automatic failover to healthy backends in the same region identify the mode console in the google cloud console go to the load balancing page go to load balancing on the load balancers tab you can see the load balancer type protocol and region if the region is blank then the load balancer is in the cross region mode the following table summarizes how to identify the mode of the load balancer load balancer mode load balancer type access type region cross region internal application load balancer application internal regional internal application load balancer application internal specifies a region gcloud to determine the mode of a load balancer run the following command gcloud compute forwarding rules describe forwarding_rule_name in the command output check the load balancing scheme region and network tier the following table summarizes how to identify the mode of the load balancer load balancer mode load balancing scheme forwarding rule cross region internal application load balancer internal_managed global regional internal application load balancer internal_managed regional important after you create a load balancer you can t edit its mode instead you must delete the load balancer and create a new one architecture and resources the following diagram shows the google cloud resources required for internal application load balancers cross region internal application load balancer this diagram shows the components of a cross region internal application load balancer deployment in premium tier within the same vpc network each global forwarding rule uses a regional ip address that the clients use to connect cross region internal application load balancer components click to enlarge regional internal application load balancer this diagram shows the components of a regional internal application load balancer deployment in premium tier regional internal application load balancer components click to enlarge the following resources are required for an internal application load balancer deployment proxy only subnet in the previous diagram the proxy only subnet provides a set of ip addresses that google uses to run envoy proxies on your behalf you must create a proxy only subnet in each region of a vpc network where you use internal application load balancers the following table describes the differences between proxy only subnets in the cross region and regional modes cross region and regional load balancers cannot share the same subnets load balancer mode value of the proxy only subnet purpose flag cross region internal application load balancer global_managed_proxy the cross region envoy based load balancer must have a proxy only subnet in each region in which the load balancer is configured cross region load balancer proxies in the same region and network share the same proxy only subnet regional internal application load balancer regional_managed_proxy all the regional envoy based load balancers in a region and vpc network share the same proxy only subnet further proxy only subnets are only used for envoy proxies not your backends backend vms or endpoints of all internal application load balancers in a region and vpc network receive connections from the proxy only subnet for regional internal application load balancers and cross region internal application load balancers the proxy only subnet can be configured with a stack type of ipv4_ipv6 dual stack the virtual ip address of an internal application load balancer is not located in the proxy only subnet the load balancer s ip address is defined by its internal managed forwarding rule which is described below forwarding rule and ip address preview cross region regional external and regional internal application load balancers support terminating ipv6 traffic this feature is subject to the pre ga offerings terms in the general service terms section of the service specific terms pre ga features are available as is and might have limited support for more information see the launch stage descriptions forwarding rules route traffic by ip address port and protocol to a load balancing configuration that consists of a target proxy and a backend service ip address specification each forwarding rule references a single regional ip address that you can use in dns records for your application you can either reserve a static ip address that you can use or let cloud load balancing assign one for you we recommend that you reserve a static ip address otherwise you must update your dns record with the newly assigned ephemeral ip address whenever you delete a forwarding rule and create a new one clients use the ip address and port to connect to the load balancer s envoy proxies the forwarding rule s ip address is the ip address of the load balancer sometimes called a virtual ip address or vip clients connecting to a load balancer must use http version 1 1 or later for the complete list of supported protocols see load balancer feature comparison the internal ip address associated with the forwarding rule can come from a subnet in the same network and region as your backends port specification each forwarding rule for an application load balancer can reference a single port from 1 65535 to support multiple ports you must configure multiple forwarding rules you can configure multiple forwarding rules to use the same internal ip address vip and to reference the same target http or https proxy as long as the overall combination of ip address port and protocol is unique for each forwarding rule this way you can use a single load balancer with a shared url map as a proxy for multiple applications the type of forwarding rule ip address and load balancing scheme used by internal application load balancers depends on the mode of the load balancer cross region internal application load balancer forwarding rule globalforwardingrules insert method regional ip address addresses insert method load balancing scheme internal_managed ip address optional shared_loadbalancer_vip routing from the client to the load balancer s frontend global access is enabled by default to allow clients from any region in a vpc to access your load balancer backends can be in multiple regions regional internal application load balancer forwarding rule forwardingrules insert method regional ip address addresses insert method load balancing scheme internal_managed ip address optional shared_loadbalancer_vip routing from the client to the load balancer s frontend you can enable global access to allow clients from any region in a vpc to access your load balancer backends must also be in the same region as the load balancer forwarding rules and vpc networks this section describes how forwarding rules used by internal application load balancers are associated with vpc networks load balancer mode vpc network association cross region internal application load balancer regional internal application load balancer depending on whether you use an ipv4 address or an ipv6 address range there is always an explicit or implicit vpc network associated with the forwarding rule regional internal ipv4 addresses and ipv6 address ranges always exist inside vpc networks when you create the forwarding rule you re required to specify the subnet from which the internal ip address is taken this subnet must be in the same region and vpc network where a proxy only subnet has been created thus there is an implied network association network and subnet requirements for ipv6 traffic your network and subnets must meet the following configuration requirements vpc network you must use a custom mode vpc network configured with the enable ula internal ipv6 flag forwarding rule subnet this subnet must be a dual stack ipv4_ipv6 or ipv6_only subnet with the ipv6 access type set to internal ipv6 address allocation options the forwarding rule must reference a 96 range of ipv6 addresses from the subnet s 64 internal ipv6 address range when you configure the forwarding rule with the ip version ipv6 flag google cloud automatically allocates a random 96 ipv6 prefix from within the range of the subnet limitations to specify a custom ephemeral ipv6 address you must use the google cloud cli or the api the google cloud console doesn t support specifying custom ephemeral ipv6 addresses for forwarding rules target proxy a target http or https proxy terminates http s connections from clients the http s proxy consults the url map to determine how to route traffic to backends a target https proxy uses an ssl certificate to authenticate itself to clients the load balancer preserves the host header of the original client request depending on the type of traffic your application needs to handle you can configure a load balancer with either a target http proxy or a target https proxy the following table shows the target proxy apis required by internal application load balancers load balancer mode target proxy cross region internal application load balancer targethttpproxies targethttpsproxies regional internal application load balancer regiontargethttpproxies regiont...