AWS S3 – Simple Storage Service – is a great service for hosting content for your portfolio. But, the service is not without some challenges. 🙂
I am developing a portfolio to showcase my eLearning work. So, I need somewhere to store my files and link to them from my blog. I previously used Dropbox and Google Drive for something similar, but that is no longer an option. Besides, what geek wouldn’t use this as an opportunity to try out AWS!
At first, I tried the “read the documentation’ approach. OMG – the documentation is…verbose. And, I’m pretty sure they’re targeting corporate users more than individuals who probably won’t spend a lot. Speaking of which – the pricing structure is…cryptic. They provide tools to help you figure out what you might pay, but I found those tools perplexing.
I’d still be parsing text if I continued down that path. So, I just jumped in, started the service, created a bucket, uploaded some content, and… messed up the permissions settings. LOL. Honestly, you’d think I hadn’t been a server admin before.
At first I thought I just hadn’t made sure that every file/folder in the project was set properly. I started looking through the documentation for managing permissions and got lost somewhere along the ACL v. Bucket / User Policies.
E v e n t u a l l y, several hours later, and a wrong turn with the JSON-based bucket policy, I think I have managed to get it. I think I was missing giving read permissions to the ACL for all users. I haven’t tested that yet. I am leaving that as a mystery to be discussed in my next post. 🙂
One last thing – experimentation is grand. I love it – most geeks do… Yet, when you’re on a ‘free tier’ option, make sure to attend to your usage:
After several attempts, I’ve used almost 40% of my allotted monthly free tier for S3-Puts. I have no clue (yet). I wonder when the billing cycle ends. I guess I’ll have to check that out, too.