OpenParable
Skip to content
← Back to skills

Cis AWS Compute 2.6

DevOps & Security
cis-aws-compute-2.6

Cis AWS Compute 2.6 is an Agent Skill for devops & security published in the CyberStrikeus/CyberStrike repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Ensure detailed monitoring is enabled for production EC2 Instances

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/CyberStrikeus/CyberStrike/blob/HEAD/.cyberstrike/skill/CIS_benchmarks/Cloud_Providers/AWS/CIS_AWS_Compute_Services_Benchmark_v1.1.0/cis-aws-compute-2.6/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/cis-aws-compute-2-6, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Ensure detailed monitoring is enabled for production EC2 Instances

Description

Ensure that detailed monitoring is enabled for your Amazon EC2 instances.

Rationale

Monitoring is an important part of maintaining the reliability, availability, and performance of your Amazon EC2 instances.

Impact

Data is available in 1-minute periods. For the instances where you've enabled detailed monitoring, you can also get aggregated data across groups of similar instances. You are charged per metric that is sent to CloudWatch. You are not charged for data storage. Due to this added cost it is recommended that you only enable this on critical instances.

Audit Procedure

Using AWS CLI

  1. Run the describe-instances command:
aws ec2 describe-instances --region us-east-1 --output json --filters "Name=monitoring-state,Values=disabled" --query "Reservations[*].Instances[*].{Instance:InstanceId}"
  1. The output should be a list of running instances that have enhanced monitoring disabled.
  2. Based on this list of instance ids refer to the remediation below.

Using AWS Console

  1. Login to EC2 using https://console.aws.amazon.com/ec2/
  2. On the left Click INSTANCES, click Instances.
  3. Select the EC2 instance you want to review.
  4. Select the Description tab.
  5. Check the Launch time.
  6. Determine the level of monitoring by reviewing the 'Monitoring attribute'.
  7. If the value is set to basic refer to the remediation below.
  8. Repeat steps no. 3 - 7 to verify the monitoring level for all instances.
  9. Go through the other AWS regions and repeat the audit process.

Expected Result

The CLI command should return an empty list, indicating all production instances have detailed monitoring enabled. In the console, the Monitoring attribute should not show basic for production instances.

Remediation

Using AWS CLI

  1. Run the monitor-instances command using the list of instances collected in the audit:
aws ec2 monitor-instances --instance-ids <i-instancename>
  1. The output will show 'state: pending'.
  2. Wait a few minutes and run the same command again for that instance and it will show enabled.

Using AWS Console

  1. Login to EC2 using https://console.aws.amazon.com/ec2/
  2. On the left Click INSTANCES, click Instances.
  3. Select the EC2 instance you want to review.
  4. Select the Monitoring tab.
  5. Click on 'Enable Detailed Monitoring'.
  6. Click on Yes, Enable.
  7. Repeat steps no. 3 - 6 for any other instances that require detailed monitoring to be enabled.

Default Value

By default, EC2 instances use basic monitoring (5-minute intervals). Detailed monitoring (1-minute intervals) must be explicitly enabled.

References

No specific references provided in the benchmark for this control.

CIS Controls

Controls VersionControlIG 1IG 2IG 3
v88.2 Collect Audit Logsxxx
v76.2 Activate audit loggingxxx

Profile

Level 2 | Manual