---
title: "1.15.28 — Application-owned fleet health checks"
description: "Brownfield AWS fleets can now bind each load-balancer target group to the application’s real readiness endpoint while existing managed deployments keep the historical `/api/version` behavior."
date: "2026-08-22"
tags: ["release"]
canonical: "https://django-mojo.sitesmojo.com/changelog/1-15-28/"
---

Brownfield AWS fleets can now bind each load-balancer target group to the application’s real readiness endpoint while existing managed deployments keep the historical `/api/version` behavior.

### Added

- Optional, independently configurable API and Certbot health-check paths in strict brownfield fleet manifests.
- Validation that accepts only bounded absolute HTTP paths and rejects hosted URLs, queries, fragments, whitespace, and control characters.

### Changed

- Target-group previews and drift digests now bind the exact desired health configuration, so an operator reviews the same path AWS will create or modify.
- Existing owned target groups safely converge health-path changes in place; managed deployments and omitted brownfield fields still default to `/api/version`.

### Upgrade notes

- Applications may point API target health at a deeper readiness route, but every registered compatibility target must serve that route before the manifest changes.
- No DNS, EIP, listener, certificate, data-plane, or target-membership behavior changed.