Using AWS Systems Manager and Patch Groups

This is a way to manage your cloud setup and use patch your AWS infrastructure in a way that meets certain parameters.

There are multiple operating systems you can choose from; It's the equivalent of saying "Hey, I have a Linux machine here; So search though all of the Linux options only and see if my particular Instance needs a patch." Or "Here's a group of Windows Servers; Check for patches once a week and let me know."

If you have multiple instances with multiple instances, you can put those into Patch Groups and designate a OS to each, however, an instance can only be in one AWS Patch Group (PG) at a time.

The most challenging part was simply setting things up. I did this in two accounts:

In my root account, with the help of this video on YouTube, I simply put in instances, applied patches easily.
In an IAM account, I had to have multiple permissions, and even then it took about 2 days for the instances to be acknowledged and for me to have patches attached.

How did I solve the problem in the IAM instance in the account with IAM access?

Truthfully, I have no idea.

I walked away for 2 days and came back to see the problem was solved, and it wasn't continually kicking me to the Quick Start screen (a screen that would be telling me to add instances to monitor...which I already had) or the AWS Parameters Store. The person I was working with also had no idea. But hey, we got there in the end (somehow).

I know hiring managers don't want to hear this, but fellow tech heads know, sometimes, it just works and we don't know how!

Actually into the service, I can put instances into certain PGs to update them on a schedule. Update windows only run 24 times (a use case example: If I wanted a PG to check for updates once a day, it would only run 24 times). It's a way to keep an eye on things, but I see how someone would be annoyed by it.

There are preset baselines for many of the Instances AWS supports, including Linux, Mac OS, and Windows.

Comments

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

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

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.

RUN TCP/IP | Morgan Lucas' Tech Portfolio

Search This Blog