Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update README.md - Use allowlisted instead of whitelisted. Use blocklist instead of blacklist. #843

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Update README.md - Use allowlisted instead of whitelisted. Use blocklist instead of blacklist. #843

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
4 changes: 2 additions & 2 deletions solutions/system_design/scaling_aws/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:*
Expand Down Expand Up @@ -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:*
Expand Down