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.
In part one of this series, I talked about the differences between Infrastructure as Config, and Infrastructure as Code. In this article, we’ll dive into the creation of a simple Virtual Private Cloud (VPC) on AWS using a Fugue composition.
Here’s what we’re going to create. It’s a basic example of a Virtual Private Cloud (VPC) which spans two availability zones (AZ) in a single region. We’re going to create four subnets (two in each AZ, and deploy a NAT Gateway in each AZ for redundancy.
Your first month in AWS can be a bit overwhelming. With over ninety services it can be difficult to make sure you’ve set up your AWS account following best practices. In this webinar, I’ll provide you with an actionable list of tasks when first getting started with AWS.
This article is part one of a multipart series exploring the idea of building a true Infrastructure as Code solution on the Amazon Web Services (AWS) platform.
What is Infrastructure as Code? I’ve talked about this subject a few times and mentioned how important (and popular) the topic was at the various AWS boot camps I’ve had the pleasure of leading. I describe Infrastructure as Code as the process of decomposing the components of your solution into individual pieces, storing these pieces in a centralized code repository and managing them like we would manage our application code.
I had numerous conversations this past week about the future of Infrastructure-as-a-Service (IaaS) and how it is increasingly becoming the third option when building solutions on Amazon Web Services (AWS).
Granted, IaaS isn’t going anywhere soon, but based on the conversations I have been having recently, both Serverless and Managed Services seem to be gaining traction when you are building something new and not shifting existing technology to AWS.
When I first started using Amazon Web Services (AWS) back in 2007, the majority of people I talked to who were interested in leveraging AWS wanted to talk about how they could use AWS to help reduce their IT costs. In the vast majority of cases, those customers were interested in shifting IT related expenses from capital to operating expenditures.
As time went on, a change in how people thought about Public Cloud occurred - rather than using AWS to help them save money organizations now wanted to talk about how they could use AWS to deliver IT projects faster.
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.
A few weeks back now I attended my first hackathon. For those of you who aren’t exactly sure what a hackathon is here’s my definition. A hackathon is where a group of individuals get together for a day (or more), come up with a few ideas of things they would like to build, pick one idea, and then get down to the business of creating something.
At the hackathon I attended, we decided to create what we ended up calling the ‘Nerd Party Alert’ application.
What a week. I’ve been hearing from all sorts of people (customers, students, co-workers) about the S3 outage - some even referred to it as the #S3apocalypse.
I’ll let you all in on something. It’s all FUD (Fear, Uncertainty, and Doubt). Every single person who is writing articles, or tweeting about the effects of the outage is using the S3 outage to try and sell you something - myself included.
When I talk to folks about serverless computing on AWS they usually say, “oh ya, you mean Lambda right?”
Sure, Lambda is the grand-daddy of serverless computing, but the AWS platform has many other serverless technologies that you can leverage to build applications on AWS.
Before jumping into a few of the serverless options that are available to us, it’s important that we define what I mean when I say “serverless” computing.