AWS transform documentation change
Summary
Modified no_proxy domain pattern from '.transform-custom.<region>.api.aws' to 'transform-custom.<region>.api.aws' (removed leading dot)
Security assessment
The change corrects proxy configuration syntax but doesn't reference any security implications. Incorrect proxy settings could cause connectivity issues but aren't presented as a security vulnerability.
Diff
diff --git a/transform/latest/userguide/custom-troubleshooting.md b/transform/latest/userguide/custom-troubleshooting.md index 433ce60fd..85430e484 100644 --- a//transform/latest/userguide/custom-troubleshooting.md +++ b//transform/latest/userguide/custom-troubleshooting.md @@ -156 +156 @@ If you are using a VPN/Proxy server that leverages the `https_proxy` and `no_pro -`export no_proxy=.s3.amazonaws.com,.transform-custom.<region>.api.aws` +`export no_proxy=.s3.amazonaws.com,transform-custom.<region>.api.aws`