Trusted Advisor findings for cost savings.

[MichaelDoria-NOAA]

Review provided trusted advisor findings.
Fernando has requested that we put the HV sub-component name next to each item and send to appropriate team members to address the findings.

[MichaelDoria-NOAA]

ELB Trust advisor findings significantly reduced through the use of Lifecycle policies and proper tagging.

[MichaelDoria-NOAA]

Getting a targeted full report from the shared services account for current resources. Writing python script to go through listed resources and get tags to associate with sub applications.

[MichaelDoria-NOAA]

Low_Utilization_EC2_dev.csv
Low_Utilization_EC2_prod.csv
Low_Utilization_EC2_uat.csv
Underutilized_EBS_dev.csv
Underutilized_EBS_prod.csv
Underutilized_EBS_uat.csv

[RobHanna-NOAA]

Interesting. I checked all of my fim-dev AWS resource for both of the "dev".csv's above.

I only had one entry which was in the Low_Utilization_EC2_dev.csv which was for just one of my developers, Heidi's, EC2 workstations. All of our team have their own EC2 workstation for FIM-Dev work and have a tool that auto-shuts them down at night. But.. a developer can override the flag to let their image run overnight if they need to once in a while.

Not sure why the other 25 didn't give the same warning. She must not being working on her EC2 much for the time period scanned.

Reminder: All of our "fim-dev" or "ras2fim" AWS objects / components through the entire system (more than just EC2's), have a tag saying "owp_group": either "fim-dev" or "ras2fim".

['True', 'fim-dev', 'fim-dev-workstation-base-6-Heidi', 'patch-policy-default-scan', 'arn:aws:resource-groups:us-east-1:526904826677:group/fim-dev-Robh-myApps/01qncctdtvr5chzhyp6k9vcybj', 'us-east-1', 'hydrovis-vpp', 'dev', 'noaa8501', 'nws', '', 'nws-dis', 'noaa8501', 'hydrovis-vpp-fim-dev', '-', '-', '', 'fim-dev']

[MichaelDoria-NOAA]

@RobHanna-NOAA This is the most current report from Quicksight in the shared services account. I did find that it isn't completely accurate, I think this is because anything within the monthly window gets added to it. I had a bunch of EBS volumes listed for UAT which no longer existed but probably had low utilization within the (previous?) month. I excluded these from the cleaned up reports, but the EC2 still exists.