Document TLS termination tradeoffs in Azure HA/autoscale READMEs#5
Merged
Merged
Conversation
The default frontend on ha-hot-hot/azure and unlimited-scale/azure is the Standard Load Balancer (TCP passthrough on 443), so the browser terminates TLS against the VM's self-signed cert. The marketplace AMI's setup.sh now generates that cert with the per-VM IMDS hostname as the CN, which never matches the LB public IP or any DNS record customers point at it. Existing behavior, previously undocumented. Steer production customers at enable_application_gateway = true with a real PFX (or a BYO upstream L7). https://claude.ai/code/session_018piCyGQ4rHxkdBdYXa5zGf
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Added documentation to the Azure
ha-hot-hotandunlimited-scalemodule READMEs explaining TLS termination behavior and production deployment recommendations. This clarifies an existing behavior that was previously undocumented.Changes
Azure ha-hot-hot README: Added "TLS termination" section explaining that the default Standard Load Balancer uses TCP passthrough on 443, causing browser warnings since the VM's self-signed certificate CN (per-VM hostname) doesn't match the LB public IP or DNS records. Documented two production options: enabling Application Gateway with a valid PFX certificate (recommended), or fronting with an upstream L7 LB/reverse proxy.
Azure unlimited-scale README: Added equivalent "TLS termination" section with similar guidance, noting the additional complexity that VMSS instances rotate on autoscale and rolling refresh, making certificate churn more visible to operators.
CHANGELOG.md: Added documentation entry under new "Documentation" section noting this clarification of existing behavior and the recommended production deployment patterns.
Implementation Details
hailbytes-asm/hailbytes-satchanges that now use per-VM IMDS hostnames for certificate CNswaf_policy_idfor WAF parity with AWS ALB deploymentshttps://claude.ai/code/session_018piCyGQ4rHxkdBdYXa5zGf