Skip to main content

MTE Relay Server v4.6 Release Notes

· 2 min read
Trevor Blackman
Trevor Blackman
Engineering Director

MTE Relay Server v4.6 builds on the v4.5 Go rewrite with flexible cloud-marketplace billing, first-class Azure Kubernetes Service (AKS) marketplace packaging, and outbound-proxy reliability fixes.

This release focuses on how the relay is deployed and metered across cloud marketplaces and on-prem, without changing application traffic flow.

New​

  • Configurable billing strategies. Billing is now selected at startup through environment variables instead of being fixed in code:

    • BILLING_STRATEGY: eclypses_no_billing, register_usage, or request_based
    • BILLING_PROVIDER: aws or azure (when the strategy needs one)
    • BILLING_PRODUCT: mrs (MTE Relay Server) or mar (MTE API Relay)
    • BILLING_REPORT_INTERVAL: reporting window for request-based metering (default 15m)

    register_usage makes a one-time AWS RegisterUsage call at startup; request_based aggregates inbound and outbound request counts and reports them to AWS or Azure on each interval. Billing initializes before the HTTP listener opens: a startup failure stops the server from listening, while runtime reporting failures in request_based mode are logged and retried without interrupting traffic.

  • On-prem and immutable AWS Marketplace images. The repository now ships dedicated Dockerfiles: on-prem images with billing disabled, and immutable AWS images with the billing contract (register_usage or request_based) baked in at build time for both MRS and MAR.

  • Azure AKS marketplace extension. MTE Relay Server and MTE API Relay now ship as Azure AKS extensions, packaged as CNAB bundles and deployable directly from the Azure Marketplace, with an Azure portal create experience. The AKS extensions no longer require Redis.

  • external_meter billing strategy (4.6.4). A new AWS billing strategy for externally metered marketplace contracts.

  • Docker Scout reports. Documented commands to generate a SARIF vulnerability report and an SPDX software bill of materials (SBOM) for the relay images.

Changed​

  • Higher outbound pairing concurrency. In outbound proxy mode, the default number of encoder/decoder pairs per target increased from 2 to 24, improving throughput when the relay acts as an MTE client.
  • Updated Go toolchain. The build moved to Go 1.26.x (1.26.1 through 1.26.3).
  • Tuned Docker Compose defaults. Resource limits and DOMAIN_MAP examples in the Compose files were adjusted for more realistic deployments.

Fixed​

  • Outbound response headers. Fixed header copying in outbound proxy responses so upstream response headers are forwarded correctly when the relay operates in outbound mode.