kube-or-fake VS aws-cloudformation-coverage-roadmap

Hi all! In this blog post, I’ll guide you through creating your own Kube or Fake? mini-game using ChatGPT. For those of you who joined late, Kube or Fake? is a Kubernetes/ChatGPT mini-game created by Raftt, where the player must distinguish between real Kubernetes terms and fake ChatGPT-generated ones (and it all happens live 💪). If you haven’t already tried it, kick back and enjoy. First, we will get familiar with the ChatGPT API and see how we can use it to generate text. We will then see how we can integrate it into a small funky app, wrap it nicely enough, and publish it for the whole world! (or a couple of friends).

CloudFormation is an IaC AWS-native service that helps you model and configure your resources declaratively. Using CloudFormation, you can manage and operate your AWS infrastructure efficiently, so you can spend less time managing infrastructure.

Basic knowledge of AWS and CloudFormation

AWS WAF Security Automations use AWS CloudFormation to quickly configure AWS WAF rules that help block these common types of attacks:

IaC stands for Infrastructure as code and for a while I struggled to understand this concept, and when it seemed like I was starting to get it, I started confusing it with some other thing. IaC allows you to build, change, and manage your infrastructure in a safe, consistent, and repeatable way by defining resource configurations that you can version, reuse, and share. Infrastructure as code is basically provisioning or creating your resources through code or configuration files, in other words, automating the process of creating them in one click, instead of creating them singly through GUI or CLI, and Terraform is a tool that helps us to do that. An AWS cloud native used to also achieve IaC is AWS CLoudFormation and you can learn more about it here

1.1 Using AWS CloudFormation If you already use AWS CloudFormation, you can simply bring your existing templates over to the new AWS account. AWS CloudFormation helps you manage and set up your resources easily. You create templates that allow you to quickly and reliably set up services or applications called “stacks.”

Similarly, on the infrastructure provisioning side, IaC tools - which are usually declarative - are a great fit for observing and managing drifts. Tools such as OpenTofu, Hashicorp Terraform, or AWS CloudFormation use declarative templates to define the environment's state. This provides the option to detect drift by comparing the current state of resources to the defined infrastructure in the code.

DevOps started with engineers clicking around the AWS console and writing scripts to automate tasks like creating EC2 instances and setting up VPCs, but as usage grew, Infrastructure as Code (IaC) tools such as terraformand CloudFormation emerged. Instead of writing shell scripts, infrastructure engineers can write declarative code to define how the cloud resources should be deployed. This is a great step up in terms of abstraction from the one-off automation scripts. On one hand, the declarative nature of the IaC tools makes it easy enough for most developers to write (you can think of it as configuration instead of code); on the other, it's not abstracted enough to give platform engineers the ability to write modularized code for developers to create infrastructure across the organization.

Container images (Dockerfiles), infrastructure as code with AWS CloudFormation, AWS Serverless Application Model (SAM), or HashiCorp Terraform can all be generated, updated, or optimized using AI-assisted tools.

AWS CloudFormation: Speed up cloud provisioning with infrastructure as code as code.

1. AWS CloudFormation