Versatile software engineer with a background in .NET consulting and CMS development. Working on regaining my embedded development skills to get more involved with IoT opportunities.
As a cautionary note, there is one more charge with S3: data outwards from the AWS network. If you make a bucket public, anyone from the Internet can download your file and you will be responsible from all the charges for those downloads!
As a best practice, never make a bucket or file public, unless you are running a static website from S3. Instead, make your files available from CloudFront if you expect lots of downloads, or use signed URLs to give your applications control over which files a user can download. Many companies have made the mistake of public buckets and accidentally exposed protected information, be careful!
As a cautionary note, there is one more charge with S3: data outwards from the AWS network. If you make a bucket public, anyone from the Internet can download your file and you will be responsible from all the charges for those downloads!
As a best practice, never make a bucket or file public, unless you are running a static website from S3. Instead, make your files available from CloudFront if you expect lots of downloads, or use signed URLs to give your applications control over which files a user can download. Many companies have made the mistake of public buckets and accidentally exposed protected information, be careful!
Thanks for checking out the article Scott! I appreciate the emphasis on what I mentioned in the post 🙂