Installing GuardDuty security agent manually on Amazon EKS resources - Amazon GuardDuty

Installing GuardDuty security agent manually on Amazon EKS resources

This section describes how you can deploy the GuardDuty security agent for the first time for specific EKS clusters. Before you proceed with this section, make sure you have already set up the prerequisites and enabled Runtime Monitoring for your accounts. The GuardDuty security agent (EKS add-on) will not work if you do not enable Runtime Monitoring.

Choose your preferred access method to deploy the GuardDuty security agent for the first time.

Console

  1. Open the Amazon EKS console at https://console.aws.amazon.com/eks/home#/clusters.

  2. Choose your Cluster name.

  3. Choose the Add-ons tab.

  4. Choose Get more add-ons.

  5. On the Select add-ons page, choose Amazon GuardDuty Runtime Monitoring.

  6. Choose the agent that shows up as the latest and default version.

  7. On the Configure selected add-on settings page, use the default settings. If the Status of your EKS add-on is Requires activation, choose Activate GuardDuty. This action will open the GuardDuty console to configure Runtime Monitoring for your accounts.

  8. After you've configured Runtime Monitoring for your accounts, switch back to the Amazon EKS console. The Status of your EKS add-on should have changed to Ready to install.

  9. (Optional) Providing EKS add-on configuration schema

    For the add-on Version, if you choose v1.5.0 or above, Runtime Monitoring supports configuring specific parameters of the GuardDuty agent. For information about parameter ranges, see Configure EKS add-on parameters.

    1. Expand Optional configuration settings to view the configurable parameters and their expected value and format.

    2. Set the parameters. The values must be in the range provided in Configure EKS add-on parameters.

    3. Choose Save changes to create the add-on based on the advanced configuration.

    4. For Conflict resolution method, the option that you choose will be used to resolve a conflict when you update the value of a parameter to a non-default value. For more information about the listed options, see resolveConflicts in the Amazon EKS API Reference.

  10. Choose Next.

  11. On the Review and create page, verify all the details, and choose Create.

  12. Navigate back to the cluster details and choose the Resources tab.

  13. You can view the new pods with the prefix aws-guardduty-agent.

API/CLI

You can configure the Amazon EKS add-on agent (aws-guardduty-agent) using either of the following options:

  • Run CreateAddon for your account.

  • Note

    For the add-on version, if you choose v1.5.0 or above, Runtime Monitoring supports configuring specific parameters of the GuardDuty agent. For more information, see Configure EKS add-on parameters.

    Use the following values for the request parameters:

    • For addonName, enter aws-guardduty-agent.

      You can use the following AWS CLI example when using configurable values supported for addon versions v1.5.0 or above. Make sure to replace the placeholder values highlighted in red and the associated Example.json with the configured values.

      aws eks create-addon --region us-east-1 --cluster-name myClusterName --addon-name aws-guardduty-agent --addon-version v1.5.0-eksbuild.1 --configuration-values 'file://example.json'
      Example.json
      {
	"priorityClassName": "aws-guardduty-agent.priorityclass-high",
	"dnsPolicy": "Default",
	"resources": {
		"requests": {
			"cpu": "237m",
			"memory": "512Mi"
		},
		"limits": {
			"cpu": "2000m",
			"memory": "2048Mi"
		}
	}	
}

    • For information about supported addonVersion, see Kubernetes versions supported by GuardDuty security agent.

  • Alternatively, you can use AWS CLI. For more information, see create-addon.

Private DNS names for VPC endpoint

By default, the security agent resolves and connects to the private DNS name of the VPC endpoint. The following list provides the private DNS names for your endpoints:

  • Non-FIPS endpoint – guardduty-data.us-east-1.amazonaws.com

  • FIPS endpoint – guardduty-data-fips.us-east-1.amazonaws.com

The AWS Region, us-east-1, will change based on your Region.