Skip to main content

Retrieving EC2 instance information with PowerShell - Part 2

If you did not read part 1 of this, there may be some differences in configurations. As long as you have access to the AWS CLI with a specified user (or yourself), you should be good to go!

We left off with running some PowerShell cmdlets to pull some information. Let's say that's not enough. Let's say we want to have the ability to make a tool out of this script to run at our leisure. Say daily, weekly, monthly. We'll have to turn this into a dedicated script for our use case.

The first thing we'll do is get our code editor. I prefer VSCode, but you can choose whichever you prefer. Within VSCode, please download the PowerShell extension.


Let's go ahead and go to File > New File. Save wherever you would like (in production, a Git repo would be ideal. For testing, we can save to our desktop). I named mine Get-EC2VMinfo.ps1, but you can name it whatever you'd like, as long as it has a .ps1 file extension.

Now that we have our text editor and file ready, let's start with our function block and parameters.


I specified two parameters here, instanceID and Region. The instanceID param is for if you want to specify a specific instance. If you don't specify, they all get returned.


The above is the core code that will be run in our process block. Let's break it down;
1. The first try block contains a call to the $PSCmdlet class that essentially says "run this part of the code if instance ID is specified"
2. The else statement is for if instanceID is NOT specified and it will return all instances
3. The [pscustomobject] blocks are to create objects out of our output and specify what we want to see.
4. The try/catch error handing is very simple. If there are any errors, they get thrown to the screen.

Now that we wrote out code, let's go ahead and run it.


I ran the code without specifying an instanceID, but I only have one running, which is why there isn't more output. Above we can see;
1. InstanceName
2. InstanceID
3. AMI
4. InstanceType
5. PrivateIP
6. PublicIP

These are the custom objects that we created within our code.

There you have it folks! We now have a tool that can pull EC2 info for us on any occasion we would like.

For code resources, please visit: https://github.com/AdminTurnedDevOps/TheLifeOfAnEngineerBlog/blob/master/RetrievingEC2instanceinformationwithPowerShellPart%202/Get-EC2VMinfo.ps1

Want to tell me how I'm doing or ask questions? Please feel free to contact me!
Gmail: mikelevantech@gmail.com
Twitter: @JerseySysadmin

Comments

Popular posts from this blog

Run PowerShell code with Ansible on a Windows Host

Ansible is one of the Configuration Manager kings in the game. With it's easy-to-understand syntax and even easier to use modules, Ansible is certainly a go-to when you're picking what Configuration Management you want to use for your organization. Your question may be "but Ansible is typically on Linux and what happens when I'm in a Windows environment?". Luckily I'm here to tell you that Ansible will still work! I was pleasantly surprised with how easy it is to use Ansible on Windows with a little WinRM magic. Let's get started.

Pre-requisites for this post:
1) WinRM set up to connect to your Windows host from Ansible
2) Ansible set up for Windows Remote Management
3) SSH access to the Ansible host
4) Proper firewall rules to allow WinRM (port 5985) access from your Ansible host to your Windows host
5) Hosts file set up in Ansible that has your IP or hostname of your Windows Server.
6) At least one Linux host running Ansible and one Windows Server host …

Running PowerShell commands in a Dockerfile

As Docker continues to grow we are starting to see the containerization engine more and more on Windows. With the need for containers on Windows, we also need the same automation we get in Linux with Dockerfiles. Today we're going to create a Dockerfile that runs PowerShell cmdlets.
Prerequisites; 1. Docker for Windows
2. A code editor (VSCode preferred)

Let's go ahead and get our Dockerfile set up. Below is the Dockerfile I used for this post.

from mcr.microsoft.com/windows/servercore:1903 MAINTAINER Michael Levan RUN powershell -Command Install-WindowsFeature -Name Web-Server RUN powershell -Command New-Item -Type File -Path C:\ -Name config
As you can see from the above, this is a tiny Dockerfile. What this will do is install the IIS Windows 

Feature and create a new file in C:\ called "config".
You should see something very similar to the below screenshot;

Next let's create a running container out of our image. First we'll need to run docker container ls to

 get o…

DevOps tooling in the Microsoft realm

When I really started to dive into automation and practicing DevOps with specific tooling, there were a few key players. At the time Microsoft was not one of them. They were just starting to embrace the open source world, including the art and practice of DevOps. Since then Microsoft has went all in and the tech giant has made some incredible tooling. Recently I switched to a Microsoft-heavy environment and I love it. I went from AWS/Python/Ansible/Jenkins to Azure/PowerShell/ARM/Azure DevOps. My first programming language was PowerShell so being back in the saddle allowed me to do a full circle between all of the different types of tooling in both worlds. Today I want to share some of that tooling with you.

The first thing I want to talk about is ARM. What is ARM? ARM is a configuration management tool that allows you to perform software-defined-infrastructure. Much like Ansible and Terraform, ARM allows you to define what you want your environment to look like at scale. With ARM, yo…