Glad you enjoyed it

Glad you think so!

Glad you liked it and thanks for the support!

Yes, if you're transferring large files then yes, you'd need to use signed urls or another approach.

You can configure your S3 bucket so all files are encrypted automatically at upload. Makes this super simple for storing encrypted files. No real coding required. You could encrypt it before you upload it (in the web app) and then the user can decrypt it again when they download it. that would all be frontend work ( encrypting and decrypting in react ) Another option is to encrypt it manually in the Lambda before storing it in S3. I don't really see the point in this vs option 1. If you did go for option 2 or 3 then you'd just use a library to do the encryption. This isn't something I've ever done so can't really recommend any packages.

Thank you!

I hope that you enjoy it

Yes, writing and reading csv files should work just the same. You'll have to convert it from cvs to JSON to be able to process it in the front end

Yes definitely. I'm planning to do some videos where I build simple from end websites that interact with the APIs built in this course.

Do you mean allowing the user to upload a file which you save in S3 and then add a field in dynamo which is the url of the uploaded object? If you do then you can definitely do that. You could modify the update player endpoint to also take an optional 'file' in the body of the request (similar to this video). If that parameter is present then you write the file to S3 as you do in this video. When you get back the details and calculate the URL you would add that as a parameter in the dynamo write data. This way when you next get that player score, there will be a URL in the data, pointing to that S3 file.

@@CompleteCoding Thanks for the comments. Could I upload a .zip file using this same Bucket?

I have a video on image upload already The API part kzfaq.info/get/bejne/faieaN2axK7MoZ8.html The react app: kzfaq.info/get/bejne/bK2glLGAvty-c3k.html Once the image is in S3, if you've made it public then you can just show that in the app. If it is private then you would have to use a signed url

You have two main options. You could either call your S3 get API from your server. If you've already followed this video then you should have an API which you can hit from your server. The other option is to add the logic for getting from S3 to your server directly. You will also need to give your EC2 permission to read from S3 but it saves the extra work of building and deploying your API. Hope that helps

@@CompleteCoding Thank you very much it is quite helpful, the file is deposited in the S3 on user request as I do it automatically an event of the S3 can invoke a rest service or implement the api

That's a good point. I'll put that option into the text version of this video

I've never seen that error before. There seem to be some answers if you google the error message

Yes, if you wanted to you could add both functionality into a single endpoint. One example I could think where you might is if you were creating a API to "find similar something". If it was for movies, you would post up the data for the movie, do some logic to find similar movies and then get those movies to return to the user.

@@CompleteCoding Thank you:)

Webpack takes all of the code required for the function and puts it into a single file. If you don't then ask code in the repo ends up in every lambda. With lots of endpoints the lambda can become too big to deploy

@@CompleteCoding Thank you for clearing that!

You can store files like those in S3 but you would use another technique called "Signed Urls". That way you can use whatever file type you like - even images or videos

Nice spot. I'm sure there are loads of little fumbles hidden in my videos