The release of the Technostress post couldn’t have been timed better if I had tried. (I swear I didn’t take downAmazon)
If you don’t know what’s going on check out TechCrunch first: https://techcrunch.com/2017/02/28/amazon-aws-s3-outage-is-breaking-things-for-a-lot-of-websites-and-apps/
Although the exact cause has not been released the error is clearly coming out of one of Amazon’s server farms taking down the East Coast. I tell my customers Hardware before Software. Crazy idea, I know, in the era of apps and everything you could ever know at your fingertips, the software will not fix a hardware issue. The software can assist in load balances to a point, but servers are strained every day depending on what you are running.
For years the technology industry has gone crazy over “cloud”. The cloud isn’t a cloud and a horrible term but highly marketable. Your information is just hosted somewhere else and the host gets to bill you per license. Hooray for overcharging! Honestly, it isn’t that bad of a system for small companies getting off the ground but these have been marketed as a long-term solution. If you depend on your own server(s) you could still go down, but Amazon currently has most of the East Coast down; overpromising and under delivering. Most server farms have a failover plan. If a server goes down it will disconnect and go to the backup server. This brings me back to my point. This is the reason why server farms exist. Load balancing and backup failover precautions cost money upfront. Take whatever technology quote you have and immediately multiply it by two. $$$$$
Amazon is one of the biggest customers for cloud as a service. When something like this happens to the largest supplier it will most likely disrupt the market. I’ll be watching this intently to see what the cause was and what marketing spin comes out of this.
As for any of you using AWS, take some vitamin D, mediate, and hope your cortisol levels don’t get too bad. (See the previous post)