Prerequisite – Creating an Amazon VPC endpoint

To create a VPC endpoint

1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.

2. In the navigation pane, under Virtual private cloud, choose Endpoints.

3. Choose Create Endpoint.

4. On the Create endpoint page, for Service category, choose Other endpoint services.

5. For Service name, enter com.amazonaws.us-east-1.guardduty-data.

   Make sure to replace us-east-1 with the correct Region. This must be the same Region as the EKS cluster that belongs to your AWS account ID.

6. Choose Verify service.

7. After the service name is successfully verified, choose the VPC where your cluster resides. Add the following policy to restrict VPC endpoint usage to specified account only. With the organization Condition provided below this policy, you can update the following policy to restrict access to your endpoint. To provide VPC endpoint support to specific account IDs in your organization, see Organization condition to restrict access to your endpoint.

   {
   	"Version": "2012-10-17",
   	"Statement": [
   		{
   			"Action": "*",
   			"Resource": "*",
   			"Effect": "Allow",
   			"Principal": "*"
   		},
   		{
   			"Condition": {
   				"StringNotEquals": {
   					"aws:PrincipalAccount": "111122223333" 
   				}
   			},
   			"Action": "*",
   			"Resource": "*",
   			"Effect": "Deny",
   			"Principal": "*"
   		}
   	]
   }

   The aws:PrincipalAccount account ID must match the account containing the VPC and VPC endpoint. The following list shows how to share the VPC endpoint with other AWS account IDs:

   Organization condition to restrict access to your endpoint

   • To specify multiple accounts to access the VPC endpoint, replace "aws:PrincipalAccount": "111122223333" with the following:

     "aws:PrincipalAccount": [
               "666666666666",
               "555555555555"
         ]

   • To allow all the members from an organization to access the VPC endpoint, replace "aws:PrincipalAccount": "111122223333" with the following:

     "aws:PrincipalOrgID": "o-abcdef0123"

   • To restrict accessing a resource to an organization ID, add your ResourceOrgID to the policy.

     For more information, see ResourceOrgID.

     "aws:ResourceOrgID": "o-abcdef0123"

8. Under Additional settings, choose Enable DNS name.

9. Under Subnets, choose the subnets in which your cluster resides.

10. Under Security groups, choose a security group that has the in-bound port 443 enabled from your VPC (or your EKS cluster). If you don't already have a security group that has an in-bound port 443 enabled, Create a security group.

    If there is an issue while restricting the in-bound permissions to your VPC (or instance), you can the in-bound 443 port from any IP address (0.0.0.0/0). However, GuardDuty recommends using IP addresses that matches the CIDR block for your VPC. For more information, see VPC CIDR blocks in the Amazon VPC User Guide.