VPC endpoint should restrict public access

Docs > Datadog Security > OOTB Rules > VPC endpoint should restrict public access

このページは日本語には対応しておりません。随時翻訳に取り組んでいます。翻訳に関してご質問やご意見ございましたら、お気軽にご連絡ください。

Description

Harden your VPC endpoint by restricting AWS actions that can be invoked through it.

Rationale

VPC endpoints can be hardened by setting a non-default VPC endpoint policy, limiting the AWS actions that can be taken when an AWS service is invoked through this VPC endpoint.

Remediation

From the console

Follow the Add or remove permissions for your endpoint service AWS console docs.

From the command line

Edit your existing Amazon VPC endpoint access policy and replace untrusted AWS identifiers. To create a new policy document, use the AWS policy generator.

{
  "Id": "insert-vpc-policy-id",
  "Version": "2012-10-17",
  "Statement": [
    {
      "Action": "*",
      "Effect": "Allow",
      "Resource": "*",
      "Principal": {
        "AWS": [
          "insert-allowed-arns"
        ]
      }
    }
  ]
}

Run the modify-vpc-endpoint command with your VPC endpoint ID and the updated or new policy document to replace the existing policy.

aws ec2 modify-vpc-endpoint \
--region insert-region-here
--vpc-endpoint-id insert-vpc-endpoint-id \
--policy-document file://insert-new-vpc-policy-filename.json

Repeat steps 1 & 2 for all non-compliant VPC Endpoints in the current region.
Repeat steps 1 & 2 for all non-compliant VPC Endpoints in other regions.