Checking EKS Runtime Monitoring configuration status - Amazon GuardDuty
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Checking EKS Runtime Monitoring configuration status

Use the following APIs or Amazon CLI commands to check the existing configuration status of EKS Runtime Monitoring.

To check existing EKS Runtime Monitoring configuration status in your account

  • Run GetDetector to check the configuration status of your own account.

  • Alternatively, you can run the following command by using Amazon CLI:

    aws guardduty get-detector --detector-id 12abc34d567e8fa901bc2d34e56789f0 --region us-east-1

    Make sure to replace the detector ID of your Amazon Web Services account and the current Region. To find the detectorId for your account and current Region, see the Settings page in the https://console.amazonaws.cn/guardduty/ console, or run the ListDetectors API

To check existing EKS Runtime Monitoring configuration status for your organization (as a delegated GuardDuty administrator account only)

  • Run DescribeOrganizationConfiguration to check the configuration status of your organization.

    Alternatively, you can run the following command using Amazon CLI:

    aws guardduty describe-organization-configuration --detector-id 12abc34d567e8fa901bc2d34e56789f0 --region us-east-1

    Make sure to replace the detector ID with the detector ID of your delegated GuardDuty administrator account and the Region with your current Region. To find the detectorId for your account and current Region, see the Settings page in the https://console.amazonaws.cn/guardduty/ console, or run the ListDetectors API