We just got back from the Google Next conference and it was quite the event. Some major updates have been announced that our team is very excited about. I wanted to make a quick post to summarize some of the major updates to GCP.
This is what the .NET community needed to fully embrace GCP
Yesterday at Google Next, they announced something I've been wanting for a long time. As a google partner, sometimes I get to hear about things when they're in alpha and this was one of them. Serverless containers is the ultimate awesome in my mind, especially for webapps and APIs, because everyone knows the biggest headache for containers is orchestration. Well this announcement kinda abrogates the need for orchestration at all. If these things auto-scale then I don't have to manage a K8s cluster at all. I mean, yeah for internal services there is some significant networking work to do, but DUDE. Auto-scaling CONTAINERS that are SERVERLESS. Can life better? I submit that it CANNOT!
When creating an AWS EC2 instance, there is a User Data section where you can include scripts that will be run immediately upon instance creation. I was attempting to use AWS CloudFormation to define the infrastructure of my current project and ran into the issue of how to include the User Data section in the CloudFormation JSON definition.
DevOps is harder than it sounds
If you're like me, when you learned about containers, you got SUPER excited. There is something about wrapping up your code in a nice little package where it has everything it needs to run in a happy little space where it's nice and warm. BUT; how'm I supposed to get my happy warm little container out into the real world where it can actually do some good? This is harder question to answer.
A CloudFormation script to get a docker instance of pi-hole running in your AWS account
What is pi-hole?
Infrastructure as code is amazing. The fact that we can build entire environments using CODE is nothing short of miraculous. But tell me if this has ever happened to you:
This is the first in a series of posts team Observian will be publishing on AWS Cloudformation. As the name suggests, this is a basic introductory article on Cloudformation. A paint brush is what I would compare Cloudformation to, AWS platform is my canvas and offerings like EC2, S3, VPC, ELB etc. are my colors to paint those elegant paintings called stacks of resources. Now, what are the building blocks of Cloudformation? Well, there are 3, namely, template, stack & change set. Template is considered the user's playground and the heart of Cloudformation.