cloud:aws
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
cloud:aws [2023/12/13 20:09] – skipidar | cloud:aws [2024/01/30 14:52] (current) – skipidar | ||
---|---|---|---|
Line 479: | Line 479: | ||
===== Shield ===== | ===== Shield ===== | ||
- | * protects | + | |
+ | AWS Shield | ||
+ | |||
+ | AWS **Shield is a managed Distributed Denial of Service (DDoS) protection service**, | ||
+ | whereas AWS WAF is an application-layer firewall that controls access via Web ACL’s. | ||
+ | |||
+ | See https:// | ||
+ | |||
+ | {{https:// | ||
Shield **" | Shield **" | ||
Line 494: | Line 502: | ||
===== WAF Web Application Firewall ===== | ===== WAF Web Application Firewall ===== | ||
- | Concentrates | + | See https:// |
+ | |||
+ | |||
+ | Network firewalls operate at Layer 3 (Network) and only understand the | ||
+ | * source IP Address, | ||
+ | * port, and | ||
+ | * protocol. | ||
+ | |||
+ | AWS **Security Group**s are a great example of this. | ||
+ | {{https:// | ||
+ | |||
+ | |||
+ | WAF works on **OSI layer 7** (Application) | ||
+ | |||
+ | means it understands higher-level protocols such as an | ||
+ | * HTTP(S) request, including its | ||
+ | * headers, | ||
+ | * body, | ||
+ | * method, and | ||
+ | * URL | ||
* WAF interacts with | * WAF interacts with | ||
- | | + | |
- | * application load balancers, | + | * application load balancers, |
- | * AppSync GraphQL, | + | * AppSync GraphQL, |
- | * APIs and | + | * APIs and |
- | * API Gateway REST APIs. | + | * API Gateway REST APIs. |
A WAF can be configured to detect traffic from the following: | A WAF can be configured to detect traffic from the following: | ||
Line 513: | Line 541: | ||
When incoming traffic matches any of the configured rules, WAF can reject requests, return custom responses or simply create metrics to monitor applicable requests. | When incoming traffic matches any of the configured rules, WAF can reject requests, return custom responses or simply create metrics to monitor applicable requests. | ||
+ | |||
+ | |||
+ | |||
===== AWS API Gateway ===== | ===== AWS API Gateway ===== | ||
Line 865: | Line 896: | ||
{{https:// | {{https:// | ||
+ | |||
+ | |||
+ | |||
+ | ===== Migration ===== | ||
+ | |||
+ | Prescriptive guideline describes pretty well how to organize it: | ||
+ | |||
+ | https:// | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ===== Domains ===== | ||
+ | |||
+ | ==== Finance and credit card ==== | ||
+ | |||
+ | Real time credit card fraud evaluation: | ||
+ | |||
+ | https:// | ||
+ | |||
+ | {{https:// | ||
+ | |||
+ | |||
+ | ==== Goldman Sachs ==== | ||
+ | |||
+ | Achieving cross-regional availibility | ||
+ | |||
+ | https:// | ||
+ | |||
cloud/aws.1702498144.txt.gz · Last modified: by skipidar