I have been following strictly to the tutorial https://docs.aws.amazon.com/lambda/latest/dg/with-s3-tutorial.html#with-s3-tutorial-create-policy

I have been following strictly to the tutorial https://docs.aws.amazon.com/lambda/latest/dg/with-s3-tutorial.html#with-s3-tutorial-create-policy

I have been following strictly to the tutorial https://docs.aws.amazon.com/lambda/latest/dg/with-s3-tutorial.html#with-s3-tutorial-create-policy

If I change a lambda function and revert it back to the same code, the sha256 is exactly the same. why is that?

AWS offers code signing in AWS lambda and the documentation states, that this makes sure, that you are preventing lambda code from being deployed from people who got access to your function. So if the intruder alters the function, he could as well just sign the function again.

I have just finished building the react note app from aws.
https://aws.amazon.com/getting-started/hands-on/build-react-app-amplify-graphql/module-one/?nc1=h_ls
For practice purpose, I want to replace those functions:fecthNotes, createNotes and deleteNotes in App.js using lambda function. However, I am totally new to javascript and all the things I wrote are generated by chatGPT. I successfully replaced fecthNotes, but I meet some problems in createNotes.

If you have and AWS API Gateway with a Lambda Reverse Proxy in Javascript calling Fetch and returning the response headers to the API-Gateway it does not work.

ChatGPT tells me this:

A lambda function is invoked with the following test event json

My code as of now just moves the entire folder from my source bucket to my target bucket. It’s a lambda that has a trigger which copies the folder once a new object is created: