Amazon GuardDuty EKS Runtime Monitoring, status is always "Requires activation"?

Question

Hi,

I just noticed that Amazon GuardDuty EKS Runtime Monitoring has status "Requires activation". I have EKS runtime enabled as per this screen:

![Enter image description here](/media/postImages/original/IMHk9pxXZsTg6rnRZ0xpE1LA)

Also, coverage is fine:

![Enter image description here](/media/postImages/original/IMfbpy8HA3TRi4vqWJHBPySA)

But when I go to EKS addons I have this error:

![Enter image description here](/media/postImages/original/IMQkiy9wFTRWCAJmEQA9BTsw)

![Enter image description here](/media/postImages/original/IMsmO5YIPOSV2sHeUagKS3iQ)

SSM fleet manager shows that SSM agent is installed on all instances. I tried to remove addon and EKS from GuardDuty and install it again, but I have the same error.

Thanks, M

myronix88 · Accepted Answer

AWS reply - According to the internal team, the status "Requires activation" is a known EKS addon bug. Actually, this addon works but in a console, we see this bug.

jpcurtin · Answer

Hi,
You mentioned "The main GuardDuty service is enabled on a vast majority of our Organization accounts already" - why only "vast majority"?  When I looked into the documentation [https://docs.aws.amazon.com/guardduty/latest/ug/guardduty_organizations.html]() I'm wondering if all the accounts are in the same region?  GuardDuty is a regional service so any accounts in another region will require the GuardDuty administrator account of that region to be created / connected to the accounts.   Best of luck!

Amazon GuardDuty EKS Runtime Monitoring, status is always "Requires activation"?

Relevant content