AWS prescriptive-guidance documentation change
Summary
Updated references from 'Network Firewall' to 'AWS Network Firewall' for product naming consistency, modified section link formatting, and removed redundant architecture reference URL
Security assessment
Changes focus on branding consistency and formatting improvements rather than addressing security vulnerabilities. The content maintains existing security recommendations about firewall rules validation and network architecture without introducing new security features or addressing specific vulnerabilities.
Diff
diff --git a/prescriptive-guidance/latest/migration-perimeter-zone-apps-network-firewall/best-practices.md b/prescriptive-guidance/latest/migration-perimeter-zone-apps-network-firewall/best-practices.md index 7b1c24dd2..88a621124 100644 --- a//prescriptive-guidance/latest/migration-perimeter-zone-apps-network-firewall/best-practices.md +++ b//prescriptive-guidance/latest/migration-perimeter-zone-apps-network-firewall/best-practices.md @@ -5 +5 @@ -[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating perimeter zone applications to the AWS Cloud using Network Firewall](welcome.html) +[Documentation](/index.html)[AWS Prescriptive Guidance](https://aws.amazon.com/prescriptive-guidance/)[Migrating perimeter zone applications to the AWS Cloud using AWS Network Firewall](introduction.html) @@ -19 +19 @@ We recommend the following best practices for migrating your perimeter zone appl - * Validate the inbound and outbound rules required for each application and their availability in AWS Network Firewall during the design phase of the migration. + * Validate the inbound and outbound rules required for each application and their availability in Network Firewall during the design phase of the migration. @@ -27 +27 @@ We recommend the following best practices for migrating your perimeter zone appl - * Keep in mind that the Application Load Balancer is an internet-facing load balancer, even though the endpoint's subnet doesn't have direct internet access. There is no internet gateway on **Route table endpoint A** and **Route table endpoint B** in the diagram from the [Perimeter zone architecture based on Network Firewall](./architecture.html#perimeter-zone-applications-network-firewall) section of this guide. The subnet is protected by Network Firewall and has internet access through Network Firewall. + * Keep in mind that the Application Load Balancer is an internet-facing load balancer, even though the endpoint's subnet doesn't have direct internet access. There is no internet gateway on **Route table endpoint A** and **Route table endpoint B** in the diagram from the _Perimeter zone architecture based on Network Firewall_ section of this guide. The subnet is protected by Network Firewall and has internet access through Network Firewall.