Skip to main content

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.


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

What Do You Need? [List of Offered Services]

2023 Version is here, at this handy Notion Page.

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl