A tool for customers to evaluate their AWS service configurations based on AWS and community best practices and receive recommendations on potential improvements.
Describe the bug
A clear and concise description of what the bug is.
EC2Active checks whether EC2 has not been running for more than 7 days. However, it checks if its CPU utilization is lower than 5%, which does not mean EC2 is not running. If EC2 is not running, we usually call it as Stopped status. Some customers who check this EC2Active got confused as their EC2 was still running with a low CPU utilization.
[code]
if not results['Datapoints']:
results['Datapoints'] = [{'Average': 0.0}]
if results['Datapoints'][0]['Average'] < 5.0:
self.results['EC2Active'] = [-1, 'Inactive']
There is another check called EC2LowUtilization to identify low utilization. Let's clarify these two checks and update the description of EC2Active accordingly.
To Reproduce
Steps to reproduce the behavior:
Clone Repo
Setup Alias
Run command
Full commands used to reproduce this bug
e.g: screener --regions ALL --services rds,iam,ec2
Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
AWS CloudShell (please complete the following information):
Region: [e.g. us-east-1]
Python version [e.g. 7.2]
AWS SDK version (boto3) [e.g. 3.0]
Browser (to display output) [e.g. chrome, safari]
Execution Environment (PLEASE FILL THIS UP IF YOU ARE NOT RUNNING THIS IN AWS CLOUDSHELL):
Instance type: [e.g. t2.small]
OS: [e.g. Linux]
EBS volume size [e.g. 20GiB]
Region: [e.g. us-east-1]
Python version [e.g. 3.8]
AWS SDK version (boto3) [e.g. 1.29.3]
Browser (to display output) [e.g. chrome, safari]
Additional context
Add any other context about the problem here.
Describe the bug A clear and concise description of what the bug is.
EC2Active checks whether EC2 has not been running for more than 7 days. However, it checks if its CPU utilization is lower than 5%, which does not mean EC2 is not running. If EC2 is not running, we usually call it as Stopped status. Some customers who check this EC2Active got confused as their EC2 was still running with a low CPU utilization.
[code] if not results['Datapoints']: results['Datapoints'] = [{'Average': 0.0}] if results['Datapoints'][0]['Average'] < 5.0: self.results['EC2Active'] = [-1, 'Inactive']
There is another check called EC2LowUtilization to identify low utilization. Let's clarify these two checks and update the description of EC2Active accordingly.
To Reproduce Steps to reproduce the behavior:
Full commands used to reproduce this bug e.g: screener --regions ALL --services rds,iam,ec2
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
AWS CloudShell (please complete the following information):
Execution Environment (PLEASE FILL THIS UP IF YOU ARE NOT RUNNING THIS IN AWS CLOUDSHELL):
Additional context Add any other context about the problem here.