Skip to main content

Retrieving EC2 instance information with PowerShell - Part 1

We're in a constant state of movement in the tech field. To ensure we can get everything done in a timely fashion, we must automate. Automation is huge in Cloud Engineering, and should be throughout all of IT. Today I'll show you a quick way to get some EC2 instance information with PowerShell. This will allow you to retrieve information right from the shell vs having to log into the UI.

First thing we want to do is ensure we have;
1. An AWS user that has programmatic access to your AWS console 
2. AWS configured within PowerShell

Let's go ahead and create a new user. You will need admin rights to your AWS console.

First, sign in and go to IAM users. Click "Create new user".


I decided to name mine "powershell". The next thing we want to do is give that user specific permissions. Head over to groups and look for the "AmazonEC2FullAccess". Because we want to have the ability to not only read, but to create resources, I will choose full access.



After you click "Create user", you'll get your access key and secret key. You cannot re-generate the secret key, so please store it in a secure location that only you have access to. (you will see an access id token. Mine is white due to crossing it out for security purposes).

Next, open up a PowerShell terminal as Administrator and run aws configure so you can type in your access key and secret key.

Now we can run cmdlets based on the AWS API for PowerShell.


There you have it! In part 2 of this series, we will start writing a PowerShell tool that will retrieve information for us. This tool is have the ability to be turned into a module so you can pass it along.

Comments

Popular posts from this blog

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…

Monitoring your containers in an AKS cluster with Prometheus

Monitoring and alerting is arguably one of the most important thing in Cloud Engineering and DevOps. It's the difference between your clients stack being up and a client being down. Most of us have SLA's to abide by (for good reason). Today we're going to learn how to spin up Prometheus in an AKS cluster to monitor our applications.

Pre-reqs;
1. Intermediate knowledge of Kubernetes
2. An AKS cluster spun up in Azure

Recently AKS supports Prometheus via Helm, so we'll use that for an automated solution to spin this up. This installs kube-prometheus, which is a containerized version of the application. With raw Prometheus, there are a few things that are needed for the operator;

1. Prometheus: Defines a desired deployment.
2. ServiceMonitor: Specifies how groups of services should be monitored
3. Alertmanager: Defines the operator to ensure services and deployments are running by matching the resource

With kube-prometheus, it is all packaged for you. This means configuri…

So, you want to be a Cloud Engineer?

In 2019 one of the biggest pieces of tech is the cloud. Whether it be public cloud or private cloud, cloud technologies are here to stay (for now). I predict that Cloud Engineering will be a very big part of IT (and development) for another 5-10 years. Today I want to share with you my journey in becoming a Cloud Engineer and some helpful tips. A career timeline to be a Cloud Engineer can go like so;

Desktop Support > Junior Sysadmin > Sysadmin > Sysadmin/Technical Lead > Engineer >  Cloud Engineer.

Although our career paths may not align, I believe that this progression is very import. Let me tell you why.



Helpdesk/Desktop Support Helpdesk and desktop support get your feet wet. It allows you to understand technology and how it's used in the workplace from a business perspective. It shows you what technologies may be best in the current environment your in and how to support those technologies. It also teaches you soft skills and how to support people from a technic…