Wasabi Storage Storage is one of the costliest options in the cloud and probably the biggest deterrent to migration. Fortunately, a handful of contenders are changing the game and breaking into affordable options for personal budgets. One of these companies is Wasabi. I have embraced the AWS platform, so on the surface this appears to be in opposition to that. Maybe it is, but Wasabi utilizes AWS S3 on the backend with a pricing strategy fit for personal as well as business use.
As I’ve stated in previous posts, I currently use CloudFlare as my CDN. There are several reasons for this that I won’t go into now. One of the “ToDo’s” on my list has been to clear CloudFlare’s cache when I upload new content to my blog. I was finally able to spend some time and get that done. CloudFlare API To start things off I reviewed the doc for the CloudFlare API.
It’s important to know your limits. In this case study we find a situation stemming from SMTP being throttled. This is part of the packet capture I received: The top lines show the previous conversation ending. SMTP successfully sent 3 messages. After the 3rd message the mail server stopped responding and retransmits began. This pattern was repeatable. More than that it was repeatable from other EC2 instances. The only thing between the EC2 instances and the mail server was a router and a firewall.
If you refer to this post, you’ll see that one of my objectives for this year was to develop an Alexa app for my kids. Well, I am happy to report this objective as completed. The cover art and the image below show the high level architecture. The app idea actually started based on something I was doing for my kids that they really took a liking to. Unfortunately, for this post it might be an idea that I could actually publish and potentially monetize.
Being that I recently took the plunge to a static site hosted on AWS S3 I thought I would create a post outlining the high-level process for future reference. There are quite a few blogs in the interwebs outining this process, but if this helps someone else too then it’s a win-win. If you are curious as to WHY I migrated, you can find a short bit about that in this post.
This is old news, but I recently found out that Jeff Bezos considered “Relentless” as a possible name for his company instead of Amazon. If this is news to you as well, you can read a short article about it from Business Insider here. Webster Dictionary defines “relentless” this way: showing or promising no abatement of severity, intensity, strength, or pace For some reason this word has stuck with me the past couple of weeks.
Moving to S3 I’m currently in the process of moving my blog to Amazon S3. I’m not the first to do this and I won’t be the last. My reasons for this are similar to everyone else. Wordpress is an excellent blogging and site platform. I have really enjoyed working with it and getting to know its innards. As I continuously evaluate the purpose of my site though, I have to keep the technology behind it in sync.
Yesterday I sat for the AWS Solutions Architect Associate exam and passed! Thanks to the teams at A Cloud Guru and WhizLabs for the training.
So, all credit goes to Colm MacCárthaigh for this one. I think his recent post on Shuffle Sharding is so go it deserves a share and a place on my blog to serve as a reminder for me from time-to-time. This is one way AWS achieves the level of reliability and stability it has for its customers. Some of the methodology can easily be applied to traditional and on-prem infrastructure though as well.
Symptoms Website randomly goes down a few times a week Server stopped responding Network and CPU logs show a small spike, but not enough to lock up a server Stopping and starting the server resolves the problem Details This pattern repeated several weeks until the customer grew tired of rebooting the server. The evidence did not seem to lead to a system issue or network or security security problem such as a denial of service.
- OLDER POSTS
- page 1 of 2