Skip to main content

Get in CloudFormation; A Timeline learning IaC for AWS

 

Want to share this page easily? 


Here's a Notion Page.

 

A big shoutout to Pluralsight for their free weekend, and James Millar for a great introductory course. For the longest time, I couldn't see how people found this easy, but this helped.

(Why did we make up so many programming languages that only work based upon the correct formatting of spaces and tabs? Readability is important, but when you're just beginning, how I learn, I'm interested in 'it works' first and 'it's pretty' second).

 

The (paid) project:

Create an Instance that has basic security rules from a security group it's in. The most difficult part was learning the tool and the formatting. This was much easier in Terraform (Now OpenTofu) for AWS, but this time we wanted to use CloudFormation.

 

The Numbers:

Resources Created: At least 11

  • VPC
  • MacOSImageID*
  • MacOSInstanceKeyName*
  • InternetGateway
  • PublicInternetRoute
  • VPCGatewayAttachment
  • PublicInternetRouteTable
  • PublicSubnet01
  • PublicSubnet01RouteTableAssociation
  • SecurityGroup
  • NetworkInterfaceAttachment

The Mac Instances were placed within later.

 

 

 TLDR? Check out the code on GitHub.

You can use a nifty GUI getup to drag and drop elements to create a JSON file;

 

 


It's not as easy at it seems, as I had to ask myself important questions:

 

What's the difference between a host and an instance?

Minutia; One's more expensive per hour.

 

Why does this throw an error?

Because YAML is picky about spacing.

This required me to make a Mac Virtual Machine. Only available in the East Virginia region through EC2; I ended up using a regular EC2 instance in its place for testing, so the client could upload the file and switch in their own Mac Instance.

You use !Ref to tie things to other elements. If I have an EC2 Instance, I'd use !Ref in the space where it asks about Firewalls to reference the one I have without hardcoding it in, very much like Variables in Terraform For Azure and AWS.


Tasks:

Create a KeyPair (Easy)
Place in A Firewall with rules about access (Hm.)

The Firewall part had the clearest documentation in AWS' CloudFormation section.

Type: AWS::NetworkFirewall::Firewall
Properties: 
  DeleteProtection: Boolean
  Description: String
  FirewallName: String
  FirewallPolicyArn: String
  FirewallPolicyChangeProtection: Boolean
  SubnetChangeProtection: Boolean
  SubnetMappings: 
    - SubnetMapping
  Tags: 
    - Tag
  VpcId: String
I found no page for the header type for integrating Key Pairs. The Key Pair parameter doesn't go where I thought, it goes under Parameters for the EC2 Instance.

 

 Parameters:

 macOSImageId:
    Type: AWS::EC2::Image::Id
    Default: ami-074f143fc810219ae
 

macOSInstanceKeyName:
    Type: AWS::EC2::KeyPair::KeyName
    Default: macos

Turns out, lots of people haven't migrated to Firewalls in CF yet. Security Groups, at a basic level, get the job done for their purposes. At least I have a good start on using AWS Firewalls.

AWS can be touchy about putting certain resources in certain regions.

API: ec2:RunInstances Not authorized for images

showed up when I tried to push a sample stack - from AWS - and it didn't work in the Ohio region. Some are region limited - something I learned from a third-party video.

💡 Consider making Amazon-given samples accessible to all regions.

A lot of things became clear the more I learned -  ex. hitting Template and Edit in Designer when a stack failed to launch.

The fact that it doesn't check the fields of things that must be specified until the end is a real pain. To its credit, it will throw all of the errors at you if they relate to other network elements - If there are errors in the EC2 instance, those are separate from those in a Firewall. It's easy to read.

I didn't have a lot of the Properties under my AWS::EC2::Route section; Remember the documentation says a lot of them aren't required. And yet;



So is there another part of my template making it necessary? Such as 'Oh, you have part A, now you need part B so it all works'?

I was eventually lead down the path of circular dependencies; Shout out to the 2nd piece of useful documentation I've come across about AWS CloudFormation.

 

💡 I also got to use curl and AWS CLI. 

 

Once again, AWS Documentation was a little too high level for a beginner, so Cloud Academy came through with how to actually set it up after installation. 

At least 3 times on Twitter, I had to ask the general population if it was intended to be this unclear, and 3 times the AWS team apologized and told me to submit feedback.

I thought it was just me, but no, their documentation confuses many people.

To their credit, AWS did come through with the actual commands; Well done! I connected via the console and bungled setting up the credentials through 'aws configuration' line - Which turned out to be a very insecure method of securing an EC2 instance.

 Here's a better way that involves policies and IAMs.



Their course on Udemy is great, and thank you again to a LI connection for the gifted course!



There are quirks in the programming; Most of the time, I've found !Ref works. But when making a firewall, it preferred Fn::GetAtt [name,name].

After lots of trial, error, and help, I managed to push an instance and some buckets - I can even log into the instance!

The second part of the task was seeing about MDM systems being compatible with EC2 instances; The general consensus was yes.

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory