Mastering Laravel & AWS S3 🚀

AWS can seem confusing and intimidating, but it doesn't have to be. Let's take a shallow dive, a wade through the Amazon and hook up our Laravel application to AWS S3.

----------------------------------------------------
⏱️ HIRE ME ⏱️
Whether you just need someone to consult you on a project or a full stack developer, drop me a message and let's start that conversation!

----------------------------------------------------

👋 SOCIAL MEDIA 👋

----------------------------------------------------

🔗 Links 🔗

----------------------------------------------------

⏱️ CHAPTERS ⏱️
0:00 - Intro
0:58 - Quick question
2:44 - IAM/User groups and users
8:15 - Create and configure an S3 bucket
15:20 - Configure the ACL on the bucket
19:51 - Configure your Laravel application
20:55 - Custom storage disks
23:20 - Testing it all out
25:22 - Replicating bucket settings
26:30 - So you wanna be a rock super star, live large, big house five cars you're in charge?

[LaravelOnline]

Stick around till the end for a special treat 🎉

[rahim-uddin-jsr]

Thank you so much for this incredibly helpful video! AWS can indeed be daunting, but you broke it down into such simple and understandable steps. Connecting my Laravel application to S3 felt seamless thanks to your guidance. Your clear explanations and practical examples made a world of difference. Keep up the fantastic work—your content is making a real impact!

[MrJeffrey]

Great watching this area of coding get a fresh perspective. Nice job!

[kristian]

As well as a great programmer you are also a wonderful narrator!

[DailyTechShot]

I'm using AWS for storing images.. however there is a small intended fuck up in AWS.

If you use the storage facade, and check if a given image exists on AWS using the exists() method, you will get a 403 response by default instead of a 404, which will result in an exception.

[EdmundCiegoBelize]

so if we have an existing appliation with files stored locally, how do we get them to s3 so that they can be served from s3? i already changed my storage filesystem already.

[Svenson]

Great tutorial, managed to set everything up! Would you say this approach is fine for a public Laravel website that gets accessed a couple hundred times a day, or do you reckon it is not safe to store it this publicly or costs may get out of hand? Just wondering, first time using anything AWS :) Edit: it will host many images and several audio files, since there will be quite a lot of articles

[ericmp]

u got any video to know explaining how much is going to cost me to use the aws s3? couldnt find it. anyways, in this case is a small project which i guess will store like between 5-10BG of imgs & mp3 files and will receive less than 1000 requests per day to retrieve those s3 objects 🤔 what do u think?

[Glory_Alphonsus]

I’m using aws s3 bucket to upload files, but when I try to download the uploaded files it downloads an empty file with the wrong doctype .

[ericmp]

thanks for the video! just one question, why dont u use warp!!!? (:

[dflshgc]

yo wait I actually do need to learn AWS…

[mori]

This is why i dont use aws. Its to much. I use the storageboxes from hetzer. Or you can use Storage Volumes on Hetzner, too. On your server you can mount the /storage/app folder, in the storagebox. Only 1line: "ln -s /mnt/storagebox /laravel/storage/app". Now you will 1TB, 5TB or 25TB full mountet with your laravel application. Soo easy. I watched your video, because i dont understand aws. Yes your video show all things, but this not for a human. And here is a other important thing: In laravel you can use private files or public files, you can use policies or gates. Why i must seeting up the S3 for the permissions... I dont understand why people use this. But thanks for your video. You show me that i will never use aws :)