AWS AWSEC2 documentation change
Summary
Minor editorial changes: renamed section header from 'Considerations' to 'Note' and removed redundant network explanation
Security assessment
Formatting changes without security implications. No security features or vulnerabilities discussed.
Diff
diff --git a/AWSEC2/latest/UserGuide/using-instance-addressing.md b/AWSEC2/latest/UserGuide/using-instance-addressing.md index c683b76ce..24aa501f4 100644 --- a/AWSEC2/latest/UserGuide/using-instance-addressing.md +++ b/AWSEC2/latest/UserGuide/using-instance-addressing.md @@ -11,2 +10,0 @@ Amazon EC2 and Amazon VPC support both the IPv4 and IPv6 addressing protocols. B -When you launch an EC2 instance, you specify a VPC and a subnet. The instance receives a private IPv4 address from the CIDR range of the subnet. You can optionally configure your instances with public IPv4 addresses and IPv6 addresses. If EC2 instances in different VPCs communicate using public IP addresses, the traffic stays in the AWS private global network and does not traverse the public internet. - @@ -99 +97 @@ If you are using Amazon VPC IP Address Manager (IPAM), you can get a contiguous -###### Considerations +###### Note