* feat: render X-Forwarded-For, -Proto and -Port headers in ALB HAProxy frontends
Append joins every client X-Forwarded-For line and adds the client address as AWS does, preserve and remove follow the load balancer attribute, and Proto and Port are always overwritten.
* feat: validate the ALB forwarding attributes and re-render config when they change
ModifyLoadBalancerAttributes rejects bad xff_header_processing.mode and xff_client_port.enabled values with ValidationError before storing anything, and regenerates the stored config when either key changes.
* test: assert the ALB X-Forwarded headers and the remove mode in the lb e2e
The app instances echo the request headers on /__headers. The internal ALB is driven from the probe client and the HTTPS ALB from the runner, covering the caller address, a client value, spoofed Proto and Port, mode remove and a rejected mode.
* test: let the lb probe client trigger accept a null header list
* docs: document the ALB forwarding headers and their attributes
Which AWS API Operations Spinifex Implements — Spinifex Docs
The AWS API operations Spinifex serves, generated from its gateway dispatch tables and the pinned AWS SDK service models on each build, service by service.
Coverage
overview
aws
compatibility
coverage
api
operations
AWS API Coverage
Overview
The platform serves 405 operations across the AWS APIs below. Every page names the operations its service implements from the pinned model, generated from the dispatch tables on each build rather than written by hand.