AWSSimplified# Chapter 04 # AWS API Gateway workshop

*********************** Use case ****************************
Setting up Application Services for AppWays to consumed by internal/external users and partners
*************************************************************
Problem statement P1N1F1: Setting up AWS Network Firewall to ensure that only legitimate request traffic is allowed into the ecosystem and all other traffic is rejected.
Problem statement P1N1F2: Setting up AWS Web application firewall to ensure that inbound http requests are valid and there is no OWASP-mentioned suspicious traffic, Requests Body, Parameters, and Header are clean and request can be accepted based on the defined rules.

* We have already solved this problem in our
- Chapter 01 - AWS Network Firewall meetup.
- Chapter 02 - AWS Web application Firewall meetup.
- Chapter 03 - AWS API Gateway meetup.

Problem statement P1N1F4: AppWays has one cloud-hosted Web service Named "CustomerEligibility", which takes CustomerID, PostCode as input in the request and responds accordingly. We have multiple way to implement this using :
- URL query string
- Header
- Payload Request (JSON/Text) - Hypermedia
The above service is for B2B and B2C customers. However Retail customers should not be able to call this service more than once within a specified time window, whereas B2B doesn't have any restrictions.

- Lets configure this and test this on the go. Along with this let's explore more scenarios/use case.

Do Join us for the learning takeaways. There will be Three sections of this session:

Section: 1
- Explore possible scenarios and design possibilities for the mentioned use case.
Section: 2
- Configure AWS API Gateway using AWS Console
Section: 3
- Test API gateway

Mode: Online.
AWSSimplified# Chapter 04 # AWS API Gateway workshop
Wednesday, March 06 · 6:00pm – 6:45pm
Time zone: Asia/Singapore
Google Meet joining info
**call link: https://meet.google.com/vsb-rcxc-abn**