AWS ELB monitoring with Topologix

Infrastructure & Networking

Application and Network Load Balancer health from CloudWatch — request rate, per-class HTTP code counts with computed 4xx/5xx error rates and target response time on ALBs, connection counts and processed bytes on both — one card per load balancer.

Requirements

  • An IAM user with ElasticLoadBalancingReadOnly + CloudWatchReadOnlyAccess (minimum permissions: elasticloadbalancing:DescribeLoadBalancers, cloudwatch:GetMetricData) and an access key.
  • Server-side only — AWS APIs are public endpoints, so no proxy agent is involved. One integration covers one region.

1 · Set up the integration

  1. Open the Integrations pageClick Integrations in the toolbar and pick AWS ELB from the catalogue.
  2. Create the IAM userAWS Console → IAM → create a user with ElasticLoadBalancingReadOnly and CloudWatchReadOnlyAccess, then generate an access key.
  3. Enter credentials and regionAccess Key ID, Secret Access Key, and the Region from the picker.
  4. Create, then verifyClick Create, then reopen the integration and click Test — it reports how many load balancers are visible in the region.
The integration catalogue — AWS ELB found via search.
The integration catalogue — AWS ELB found via search.
The AWS ELB configuration drawer with example values. Every screen in this guide is the real product.
The AWS ELB configuration drawer with example values. Every screen in this guide is the real product.
Target on a private network? Route it through a proxy agent. Proxy agents run inside your network — behind NAT, on a management VLAN, in an air-gapped segment — and reach targets the Topologix server can't. The agent polls the server every 15 seconds for its assignments, runs the checks locally, and pushes results back every 5 seconds, so no inbound firewall rules are ever needed. Set a default proxy on the integration; every metric source can override it. If a proxy goes offline, its sources are marked stale within ~90 seconds and the last known values stay visible.

2 · Add it to a flow

  1. Select the load-balancer nodeClick the node, open Metrics, then + Add and choose the ELB integration.
  2. Pick load balancersThe discovered list labels each entry ALB or NLB with its state and scheme. Multi-select fans out one source per load balancer.
  3. Choose the period and savePeriod — 1 minute to 24 hours, default 5 minutes — then Add Source. ALB cards show requests, 2xx/3xx/4xx/5xx counts, computed 4xx/5xx error rates, and target response time; NLB cards show connections and processed bytes (per-request HTTP metrics don’t exist for NLBs).
Live canvas screenshots for this integration require a real AWS ELB environment, so this guide shows the configuration screens only — the flow steps above work exactly like every other integration.

Good to know

  • Covers Application and Network Load Balancers via the ELBv2 API — Classic Load Balancers are not listed.
  • HTTP code counts are the target-generated HTTPCode_Target_* series, so the 5xx rate reflects what your targets actually returned rather than mixing in LB-generated codes.
  • Each poll looks back two periods so a completed CloudWatch datapoint is always found despite CloudWatch’s arrival lag.

All integrations →

See it on your own infrastructure

Book a demo and we will walk you through Topologix with your systems in mind: on our cloud, or self-hosted in your own network.

Book a demoContact us