From 07733f76c2a854f77442f75eb52cea5e32f68e7b Mon Sep 17 00:00:00 2001 From: JSon Date: Mon, 26 Feb 2024 13:16:36 +0800 Subject: [PATCH] Use allowlisted instead of whitelisted. Use blocklist instead of blacklist. --- README.md | 2 +- solutions/system_design/scaling_aws/README.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 7f41e7b..287dbaa 100644 --- a/README.md +++ b/README.md @@ -740,7 +740,7 @@ A reverse proxy is a web server that centralizes internal services and provides Additional benefits include: -* **Increased security** - Hide information about backend servers, blacklist IPs, limit number of connections per client +* **Increased security** - Hide information about backend servers, blocklist IPs, limit number of connections per client * **Increased scalability and flexibility** - Clients only see the reverse proxy's IP, allowing you to scale servers or change their configuration * **SSL termination** - Decrypt incoming requests and encrypt server responses so backend servers do not have to perform these potentially expensive operations * Removes the need to install [X.509 certificates](https://en.wikipedia.org/wiki/X.509) on each server diff --git a/solutions/system_design/scaling_aws/README.md b/solutions/system_design/scaling_aws/README.md index 99af0cf..9ffcdc4 100644 --- a/solutions/system_design/scaling_aws/README.md +++ b/solutions/system_design/scaling_aws/README.md @@ -126,7 +126,7 @@ Add a **DNS** such as Route 53 to map the domain to the instance's public IP. * Allow the web server to respond to incoming requests from: * 80 for HTTP * 443 for HTTPS - * 22 for SSH to only whitelisted IPs + * 22 for SSH to only allowlisted IPs * Prevent the web server from initiating outbound connections *Trade-offs, alternatives, and additional details:* @@ -182,7 +182,7 @@ We've been able to address these issues with **Vertical Scaling** so far. Unfor * Use a Virtual Private Cloud * Create a public subnet for the single **Web Server** so it can send and receive traffic from the internet * Create a private subnet for everything else, preventing outside access - * Only open ports from whitelisted IPs for each component + * Only open ports from allowlisted IPs for each component * These same patterns should be implemented for new components in the remainder of the exercise *Trade-offs, alternatives, and additional details:*