MTE Relay v5.0.1: AWS Marketplace images and a larger outbound pool
· 2 min read
MTE Relay 5.0.1 is a patch release of MTE Relay Server and MTE API Relay. It puts both v5 servers on the AWS Marketplace, lets the MTE API Relay outbound pool grow with demand, and closes two control plane secret exposures. v5 clients and configuration work unchanged.
AWS Marketplace
- The Marketplace images,
eclypses/mrs-hocandeclypses/mar-hoc, register with AWS Marketplace metering at startup. The subscription is the license, and AWS bills each running container, control plane included. - A container without the
aws-marketplace:RegisterUsagepermission, or outside ECS, Fargate, and EKS, logs the AWS error and exits before it serves. - The AWS pages now walk through a control plane and relay service on ECS with Service Connect, EFS, SSM Parameter Store, and an Application Load Balancer: MTE Relay Server on AWS and MTE API Relay on AWS.
Outbound pair pool
- The MTE API Relay outbound pool grows to demand: refills keep running until the pool covers the requests waiting, and requests get a pair in arrival order.
CLIENT_MAX_PAIRSis 1024 (was 100),MAX_PAIRS_PER_CLIENTis 2048 (was 200), andCLIENT_PAIR_ACQUIRE_WAIT_MSis 1000 (was 250). See Outbound pair pool.
Prometheus metrics
- Relays and the control plane can serve Prometheus metrics on their own
listener. It stays off until
METRICS_PORTis set,9090by convention, andMETRICS_TOKENcan require a bearer token.
Control plane security
- A session signing secret shorter than 32 bytes, or one copied from a published example, is replaced by a generated one at startup. Panels seeded from such a value sign every admin out once after the upgrade.
- Credentials in an upstream URL, such as
https://user:pass@api.example.com, no longer appear in logs, read scope answers, redacted exports, history, or worker reports.
Upgrading
Change the image tag to 5.0.1 on the control plane and every relay, control
plane first. Relays keep serving their last configuration while it restarts.