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!
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.
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.
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
That depends on what you’re storing and what you’re serving those couple hundred visits. If they’re each downloading GBs of days that is different than just serving a few MB of images. AWS doesn’t charge for each download they charge based on the amount of data you are serving. Typically this is how I setup a site for a couple hundred daily visitors.
@@LaravelOnline It was a tricky one. While trying to create the bucket through s3 client (I was desperate...), I got 'cURL error 60: SSL certificate problem'. Wich finally told me where the error was. I downloaded the cacert.pem and change my php.ini file with it. Works like a charm now. I was pulling my hairs off. If that can help someone one day. Made a Stackoverflow post about it.
First of all, thank you for the video and for you response to the comment, good quality really. Error was tricky, it was a weir cURL / SSL certificate error... had to download cacert.pem and modify my php.ini file. Almost went crazy. Made a post on stackoverflow if needed. But I seem to be the only poor soul that faced the problem...
@@LaravelOnline Hey man, thank you for the video, its great. It was tricky. It was a ssl / cURL error, found out while trying to create the bucket through s3 client. Had to download a file (can't say more here, it deletes my comment) and change my php.ini file. Made a post on stack if needed. Nearly drove me mad.
I had the same error ,I lost my mind for an entire day, I'm not sure if the solution is downloading the cacert file and changing the php.ini file , for me I had to DEACTIVATE MY ANTIVIRUS (using avast) which is weird , the next day it wasn't working,lost my mind for half a day again, until deactivating my antivirus so apparently I have to keep it always deactivated
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 this is right. Can you view the file in AWS? You should be able to verify it’s doc type and even download/view the file from the console.
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 :)
Right but let’s say you have a 400mb video that you want people to be able to stream in California, but your server is in Australia. How will you ensure people in California have good streaming speeds, how much will it cost you? AWS allows you this type of granularity and predictability, this is a VERY small example.
What if your server is load balanced over 3 servers but you exceed 80% CPU for 2 minutes, how would handle that? Can it be automated? AWS can handle this situation, again, a small example.
@lOnline I know what you mean, and yes for your example, aws is the right way. But in 90% not. I know many people they switched to hetzner, because its so clean admin panel. The Storage Volumes and Storageboxes are very powerfull. The most power you will get, if you make full mounting, with EXT4, XFS, WebDav or SSHFS. And Hetzner also support Load Balancer with Forge :)
Stick around till the end for a special treat 🎉
Great tutorial. We need more on aws!
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!
🥰 thank you for such a beautiful compliment!
Great watching this area of coding get a fresh perspective. Nice job!
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.
Interesting, I’m going to look into this!
As well as a great programmer you are also a wonderful narrator!
Aww, thank you so much!
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.
Well you would have to move those files up and store the urls, every app is different it depends on your use.
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
That depends on what you’re storing and what you’re serving those couple hundred visits. If they’re each downloading GBs of days that is different than just serving a few MB of images. AWS doesn’t charge for each download they charge based on the amount of data you are serving. Typically this is how I setup a site for a couple hundred daily visitors.
Damn man, I followed everything to the letter, multiple times. All I get is "false". I don't know what to try anymore...
Where do you get this error?
@@LaravelOnline It was a tricky one.
While trying to create the bucket through s3 client (I was desperate...), I got 'cURL error 60: SSL certificate problem'. Wich finally told me where the error was. I
downloaded the cacert.pem and change my php.ini file with it.
Works like a charm now. I was pulling my hairs off. If that can help someone one day. Made a Stackoverflow post about it.
First of all, thank you for the video and for you response to the comment, good quality really.
Error was tricky, it was a weir cURL / SSL certificate error... had to download cacert.pem and modify my php.ini file. Almost went crazy.
Made a post on stackoverflow if needed. But I seem to be the only poor soul that faced the problem...
@@LaravelOnline Hey man, thank you for the video, its great.
It was tricky. It was a ssl / cURL error, found out while trying to create the bucket through s3 client. Had to download a file (can't say more here, it deletes my comment) and change my php.ini file. Made a post on stack if needed. Nearly drove me mad.
I had the same error ,I lost my mind for an entire day, I'm not sure if the solution is downloading the cacert file and changing the php.ini file , for me I had to DEACTIVATE MY ANTIVIRUS (using avast) which is weird , the next day it wasn't working,lost my mind for half a day again, until deactivating my antivirus so apparently I have to keep it always deactivated
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?
I don’t have a video on calculating costs for AWS, there are calculators if you Google it though
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 .
What do I do?
I’ve not seen this happen before. I’m assuming you’re using Laravel and using Storage::put()?
@@LaravelOnline I’m using this: Storage::disk('s3')->put().
@@Glory_Alphonsus this is right. Can you view the file in AWS? You should be able to verify it’s doc type and even download/view the file from the console.
@@LaravelOnline yes. I can view the file on the s3 bucket. However I can’t download the exact file type and size.
thanks for the video! just one question, why dont u use warp!!!? (:
😂 I do sometimes. I had it on another machine just haven’t installed it back here yet. I’ll do it though 😁
@@LaravelOnline its fine. im waiting for it to be released on linux & windows ^^
nice video
Thank you so much. They can take quite a bit of energy to get out to UA-cam, I appreciate the compliment!
yo wait I actually do need to learn AWS…
Tada!! Don’t forget to subscribe!
❤😊
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 :)
There’s a reason most of the largest companies on earth use AWS. If your app doesn’t need to scale keep doing what you’re doing.
@@LaravelOnline Yes, you can also scale up with storage volumes on hetzner. Laravel Forge support Hetzner,too :)
Right but let’s say you have a 400mb video that you want people to be able to stream in California, but your server is in Australia. How will you ensure people in California have good streaming speeds, how much will it cost you? AWS allows you this type of granularity and predictability, this is a VERY small example.
What if your server is load balanced over 3 servers but you exceed 80% CPU for 2 minutes, how would handle that? Can it be automated? AWS can handle this situation, again, a small example.
@lOnline I know what you mean, and yes for your example, aws is the right way. But in 90% not. I know many people they switched to hetzner, because its so clean admin panel. The Storage Volumes and Storageboxes are very powerfull. The most power you will get, if you make full mounting, with EXT4, XFS, WebDav or SSHFS. And Hetzner also support Load Balancer with Forge :)