Was recently working on a project for a customer who was having performance issues. Noticed the customer was using t2.* for the problematic system. Also knew that I'd seen them using pre-Nitro instance-types on some other systems they'd previously complained about performance problems with. Wanted to put a quick list of "you might want to consider updating these guys" EC2s. Ended up executing:
$ aws ec2 describe-instances \ --query 'Reservations[].Instances[].{Name:Tags[?Key == `Name`].Value,InstanceType:InstanceType}' \ --output text | \ sed -e 'N;s/\nNAME//;P;D'
Because the describe-instances's command-output is multi-line – even with the applied --query filter – adding the sed filter was necessary to provide a nice, table-like output:
t3.medium ingress.dev-lab.local t2.medium etcd1.dev-lab.local m5.xlarge k8snode.dev-lab.local m6i.large runner.dev-lab.local t2.small dns1.dev-lab.local t3.medium k8smaster.dev-lab.local t2.medium bastion.dev-lab.local t3.medium ingress.dev-lab.local t2.medium etcd0.dev-lab.local m5.xlarge k8snode.dev-lab.local m6i.large runner.dev-lab.local m5.xlarge k8snode.dev-lab.local t2.xlarge workstation.dev-lab.local t2.medium proxy.dev-lab.local t2.small dns0.dev-lab.local t3.medium ingress.dev-lab.local t2.medium etcd2.dev-lab.local m5.xlarge k8snode.dev-lab.local t2.medium mail.dev-lab.local m6i.large runner.dev-lab.local t2.small dns2.dev-lab.local t3.medium k8smaster.dev-lab.local t2.medium bastion.dev-lab.local t2.medium proxy.dev-lab.local
No comments:
Post a Comment