AWS CLI security error

Earlier I was getting a security error using a clean install of the Amazon Web Services CLI on a new EC2 instance. After triple checking my keys in the IAM Management console I figured out there was something else going on. Hopefully this helps anyone who is running into the same problem & searching for solution.

The initial installation of the AWS CLI tools is pretty straight forward. On a Debian machine the following should work.
sudo apt-get install -y python-pip
sudo pip install awscli

I’ve found the best way to configure your security settings is using aws configure which is covered here here

Once you’ve configured AWS CLI it’s recommended you run a simple test such as:
aws ec2 describe-regionsThe security error I kept getting when running the command looked like this:
A client error (AuthFailure) occurred: AWS was not able to validate the provided access credentialsIf you are seeing a similar error double check that your system clock is in sync with a time server. If it’s just a minute ahead your credentials will fail silently.

Five Links

How I Learned to Stop Giving Advice – spot on post about helping early stage start-ups by telling them stories about your own experiences starting a company.  Stories about where things went wrong are just as important as where things succeeded.  From the author. “It is that founder’s job to take what I can relate about my experiences and determine if it applies to what they are doing. They know their product, vision, and domain more than I ever will.”

AWS Tips I Wish I’d Known Before I started – a solid collection of tips for all pieces of the AWS stack. Love this line – “If you have to SSH into your servers, then your automation has failed.”

Why the Most Important Part of Your App has the Messiest Code – truth. 

Do Not End the Week With Nothing – This is a must read for developers. It’s lengthy but very much worth the time.  

Fake Your Backend – A simple way to create a dummy endpoints for your front-end or app developers. With it you can quickly mock up JSON endpoints. I can see this being very handy.

Nexus 5 Screen Replacement

File this one under “things I couldn’t solve with a simple Google search”.

I recently dropped & shattered the screen on my Nexus 5. Bummer. It was actually pretty surprising, I’ve had plenty of other phones with Gorilla Glass that were dropped and survived. This time the phone hit the ground face down and completely shattered.

If you are looking for a way to replace it yourself I’d recommend you save yourself the trouble. Replacement screens run $150+ on eBay and that’s just parts.

I ended up contacting LG support at 1-800-793-8896. It’s a pretty straight forward process, they’ll give you a return authorization number and an address to mail the phone. They won’t give you an estimate until they have had a chance to inspect the phone but I can tell you right now, it will cost you $146.

After they receive the phone you’ll get a call from a support rep. You can pay the repair fee right then over the phone, and a few days later your Nexus 5 will be returned, good as new. It’s not a refurb, they send your actual phone back. You’ll still need to factory reset before you send it in though.

Expensive lesson, but overall a pretty simple process. Hope this helps someone looking for a solution.


© 2009 - 2019 Ross Bates