Troubleshooting ec2 Guardduty runtime agent not reporting

0

I am following the steps to enable the GuardDuty security agent on my ec2 instances which are used in a ecs cluster.

The ec2 instance is running and when I run sudo systemctl status amazon-guardduty-agent

it shows

amzn_guardduty_agent_ecs: GuardDuty agent started
amzn_guardduty_agent_ecs: Type Ctrl+C to terminate

I've crated a VPC endpoint with private subnet the ec2 instance is in, with dns enabled and a security group applied allowing 443 inbound from 0.0.0.0/0 but it's still reporting as agent no reporting in the AWS Guardduty dashboard.

What is the endpoint that is called / is there any further troubleshooting I can do from the ec2 instance?

已提問 6 個月前檢視次數 404 次
2 個答案
0

The IAM role assigned to the EC2 hosts must have the policy AWSServiceRoleForAmazonGuardDuty

Is this the case?

profile picture
專家
已回答 6 個月前
  • I didn't see that documented anywhere - but it turns out I missed a step on the guide. Under Additional settings, choose Enable DNS name.

0

Validate Prerequisites for Amazon EC2 instance support here - https://docs.aws.amazon.com/guardduty/latest/ug/prereq-runtime-monitoring-ec2-support.html

profile picture
已回答 6 個月前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南