Running a website on the AWS platform is one of the most common ways that I see organization employ when first getting started with Amazon Web Services.
It’s popular because it tends to be quite cost-effective (depending on your deployment methodology), and it’s easy to get started.
In this webinar, I discussed general best practices, three reference architectures, and their benefits.
I love BaseCRM! It’s been my go to CRM for some years now, and when I decided to start my own AWS consulting and managed services business, I knew exactly which CRM tool I was going to use.
One thing I needed was an easy way to capture lead data from my static website which I’m hosting via the Simple Storage Service (S3) and delivering content via CloudFront. If you’re a regular reader, you know that one of my goals for 2017 is to shut down as many OS’ as I can, so I decided the integration of my S3 website with BaseCRM would serve as an excellent example of what is possible.
In the previous two articles, I told you about how I used scheduled Lambda jobs and S3 event notifications to remove multiple Cron jobs running on an EC2 instance. In this article, I’ll talk about how I handle jobs in the SQS queues.
The Hockey Pool application uses a total of five SQS queues. Three are for processing stat files; the other two are for injuries and lifetime standings - ya, we’re stat geeks.
Send a paragraph about what you're trying to do on AWS. I'll come back with how I'd approach it, or a pointer to someone better suited.
