Create an AWS Lambda and Connect to API Gateway. about 100daysofcloudideas HOT 4 CLOSED

@what-name in my opinion we should inculcate the idea of building anything with a security first approach, so included the API key as must ,but that could be anything else too with a security aspect is all.

As for complexity ,I thought we could see some of these below patterns implemented for further levels as it will add a dash of challenge to exploring serverless functions offerings with various triggers

https://www.jeremydaly.com/serverless-microservice-patterns-for-aws/

Just my $0.2

from 100daysofcloudideas.

I agree level 200 for any FaaS really, security first, always.

from 100daysofcloudideas.

#16
Lambda and APIGateway are not Level 100 but 200. Especially when securing the API with an access key. Creating this is somewhat easy after some experience, but saying this is Level100 is false hope. Participants will likely encounter some advanced problems such as choosing "Proxy" and integrating the two resources together, deploying the API Gateway after changes and using POSTMAN (which is not required without the API Access Key).

I think the API Access Key should be optional and this project bumped to 200.

from 100daysofcloudideas.

closing, please apply changes in PR #16 (comment)

from 100daysofcloudideas.