AWS AWSEC2: Documentation updates for Secondary Networks terminology
Summary
Standardized capitalization of 'Region' and 'Availability Zone' and minor wording clarifications.
Security assessment
Changes involve terminology standardization (e.g., 'availability zone' to 'Availability Zone') and minor wording tweaks without altering security implications. The IAM permission note remains unchanged in substance.
Evidence
+ * Verify IAM permissions for ec2:CreateSecondaryNetwork, ec2:CreateSecondarySubnet.
Diff
diff --git a/AWSEC2/latest/UserGuide/secondary-networks.md b/AWSEC2/latest/UserGuide/secondary-networks.md index 290db1626..495766fe8 100644 --- a//AWSEC2/latest/UserGuide/secondary-networks.md +++ b//AWSEC2/latest/UserGuide/secondary-networks.md @@ -83 +83 @@ EC2 instances that support Secondary Networks are multi-homed, meaning they can - * Secondary interfaces cannot be attached/detached once the instance is launched. + * Secondary interfaces cannot be attached/detached after the instance is launched. @@ -96 +96 @@ EC2 instances that support Secondary Networks are multi-homed, meaning they can -Before launching instances with Secondary Networks, ensure you have also configured your VPC in the targeted region and a Subnet in the targeted availability zone of your EC2 capacity. +Before launching instances with Secondary Networks, ensure you have also configured your VPC in the targeted Region and a Subnet in the targeted Availability Zone of your EC2 capacity. @@ -125 +125 @@ Create a Secondary Network in the same region as your VPC. This is a regional re -Create a Secondary Subnet in the same availability zone as your VPC subnet. This is an AZ-specific resource. +Create a Secondary Subnet in the same Availability Zone as your VPC subnet. This is an AZ-specific resource. @@ -240 +240 @@ Amazon reserves 5 IP addresses per subnet. -**Use Multiple Subnets** : Within a Secondary Network, use multiple Secondary Subnets to segment traffic by GPU index, availability zone, or workload type. As an example, a common architecture pattern is to deploy a single secondary network with 4 or 8 secondary subnets, where each secondary subnet is aligned to a group of GPUs of common indices. +**Use Multiple Subnets** : Within a Secondary Network, use multiple Secondary Subnets to segment traffic by GPU index, Availability Zone, or workload type. As an example, a common architecture pattern is to deploy a single secondary network with 4 or 8 secondary subnets, where each secondary subnet is aligned to a group of GPUs of common indices. @@ -256 +256 @@ Amazon reserves 5 IP addresses per subnet. - * Check that your Secondary Subnet is in the same availability zone as your VPC subnet + * Check that your Secondary Subnet is in the same Availability Zone as your VPC subnet @@ -273 +273 @@ Amazon reserves 5 IP addresses per subnet. - * Instances within the same secondary subnet are reachable via direct routes. Cross subnet communication is available via a static route vended via DHCP. + * Instances within the same secondary subnet are reachable through direct routes. Cross subnet communication is available via a static route vended via DHCP. @@ -284 +284 @@ Amazon reserves 5 IP addresses per subnet. - * Verify IAM permissions for ec2:CreateSecondaryNetwork, ec2:CreateSecondarySubnet, etc. + * Verify IAM permissions for ec2:CreateSecondaryNetwork, ec2:CreateSecondarySubnet. @@ -288 +288 @@ Amazon reserves 5 IP addresses per subnet. - * Verify that you're using the correct region and availability zone + * Verify that you're using the correct Region and Availability Zone