AWS elasticloadbalancing documentation change
Summary
Updated terminology from 'ELB' to 'Elastic Load Balancing' when describing cookie generation for CORS requests
Security assessment
Change only updates service name terminology without modifying security-related content about SameSite cookies. No vulnerability or security enhancement is addressed.
Diff
diff --git a/elasticloadbalancing/latest/application/rule-action-types.md b/elasticloadbalancing/latest/application/rule-action-types.md index 0ebc08ef6..265816801 100644 --- a//elasticloadbalancing/latest/application/rule-action-types.md +++ b//elasticloadbalancing/latest/application/rule-action-types.md @@ -94 +94 @@ Application Load Balancers do not support cookie values that are URL encoded. -With CORS (cross-origin resource sharing) requests, some browsers require `SameSite=None; Secure` to enable stickiness. In this case, ELB generates a second cookie, AWSALBTGCORS, which includes the same information as the original stickiness cookie plus this `SameSite` attribute. Clients receive both cookies. +With CORS (cross-origin resource sharing) requests, some browsers require `SameSite=None; Secure` to enable stickiness. In this case, Elastic Load Balancing generates a second cookie, AWSALBTGCORS, which includes the same information as the original stickiness cookie plus this `SameSite` attribute. Clients receive both cookies.