It's been a week.
My intention was to post weekly on the progress i've made completing the Cloud Resume Challenge. This week is unfortunately more about obstacles than progress.
In retrospect, it hasn't been an entirely unproductive time. I completed the javascript for my visitor counter which successfully increments my DynamoDB table, and was (previously) thinking i was prepared to say, "here world! it's a good start!". As i'm progressing though, i realize that there are plenty of guides out there for the steps to complete the challenge, but not necessarily as securely as i'd prefer. I'm also discovering that the documentation is ...hit or miss. And it's not for a lack of looking.
While i had also originally said my intention was to stick to the specific challenge objectives, security is kinda my thing. I don't want people to be able to access my content directly from an S3 URL, i want them to go through CloudFront. I created an origin access identity on my bucket, an API gateway to forward the requests, and eventually built a Lamda@Edge after having read that was required to deliver the correct host value to the API...
Sadly, with public access disabled on my bucket, i continue to get the Missing Authentication Token error. Even sadder, the number of things i've found and attempted to resolve this (20 at least? no exaggeration) have all been unsuccessful.
So this week finds an old noob a little discouraged.
...and i'm still parsing settings and search results, trying to find that piece i'm missing.
Top comments (1)
I decided to stop trying to find the "magic tweak" and go back to the basics, rebuild (or in this case verify) from the ground up using the most updated documentation. I had a feeling it was something simple I was overlooking. I was right =]