AWS neptune: Neptune bulk loader requires Gateway VPC endpoint for Amazon S3
Summary
Clarifies that the S3 bucket for bulk loading must be in the same AWS Region as the Neptune DB instance, and that the loader requires a Gateway (not Interface) VPC endpoint for Amazon S3, adding a note that S3 offers both endpoint types under the same service name.
Security assessment
The change documents network-path requirements for the loader: a Gateway VPC endpoint keeps S3 traffic on the AWS private network instead of traversing the public internet, and the note prevents users from selecting the wrong (Interface) endpoint type. This is hardening/connectivity guidance rather than a fix for a specific vulnerability, so it is security-adjacent documentation of medium impact.
Evidence
+The Neptune loader requires a Gateway VPC endpoint for Amazon S3.
Diff
diff --git a/neptune/latest/userguide/bulk-load-data.md b/neptune/latest/userguide/bulk-load-data.md index b1ddf3c..c156bf5 100644 --- a//neptune/latest/userguide/bulk-load-data.md +++ b//neptune/latest/userguide/bulk-load-data.md @@ -21 +21 @@ For information about launching a Neptune DB instance, see [Creating an Amazon N - * An Amazon Simple Storage Service (Amazon S3) bucket to put the data files in. + * An Amazon Simple Storage Service (Amazon S3) bucket to put the data files in. The bucket must be in the same AWS Region as your Neptune DB instance. @@ -48 +48 @@ The Neptune `Load` API needs read access to the data files only. The IAM policy -The Neptune loader requires a VPC endpoint for Amazon S3. +The Neptune loader requires a Gateway VPC endpoint for Amazon S3. @@ -58 +58,5 @@ The Neptune loader requires a VPC endpoint for Amazon S3. - 4. Choose the **Service Name** `com.amazonaws.`region`.s3`. + 4. For **Type** , choose **Gateway** , and then choose the **Service Name** `com.amazonaws.`region`.s3`. + +###### Note + +Amazon S3 offers both **Gateway** and **Interface** endpoints under this service name. The Neptune loader requires the **Gateway** type.