AWS AWSEC2 documentation change
Summary
Simplified instructions for assigning secondary private IPv4 addresses by removing Elastic IP allocation step
Security assessment
The change streamlines documentation steps but does not explicitly address security concerns. Removal of Elastic IP allocation guidance does not indicate a security fix or vulnerability mitigation.
Diff
diff --git a/AWSEC2/latest/UserGuide/config-windows-multiple-ip.md b/AWSEC2/latest/UserGuide/config-windows-multiple-ip.md index 25bf90e87..44690fa5b 100644 --- a//AWSEC2/latest/UserGuide/config-windows-multiple-ip.md +++ b//AWSEC2/latest/UserGuide/config-windows-multiple-ip.md @@ -30,3 +30 @@ These instructions are based on Windows Server 2022. The implementation of these - 1. Assign the secondary private IPv4 address to the network interface for the instance. You can assign the secondary private IPv4 address when you launch the instance, or after the instance is running. For more information, see [Assign secondary IP addresses to an instance](./instance-secondary-ip-addresses.html#assign-secondary-ip-address). - - 2. Allocate an Elastic IP address and associate it with the secondary private IPv4 address. For more information, see [Allocate an Elastic IP address](./working-with-eips.html#using-instance-addressing-eips-allocating). + * Assign the secondary private IPv4 address to the network interface for the instance. You can assign the secondary private IPv4 address when you launch the instance, or after the instance is running. For more information, see [Assign secondary IP addresses to an instance](./instance-secondary-ip-addresses.html#assign-secondary-ip-address).