AWS neptune documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' throughout the documentation for consistency. No functional changes to security configurations or procedures.
Security assessment
The changes are purely terminological (removing 'AWS' prefix from CloudFormation references) and do not alter security configurations, permissions, or address vulnerabilities. Security group configuration instructions remain unchanged except for terminology alignment.
Diff
diff --git a/neptune/latest/userguide/export-service.md b/neptune/latest/userguide/export-service.md index f792d4130..c033abcd3 100644 --- a//neptune/latest/userguide/export-service.md +++ b//neptune/latest/userguide/export-service.md @@ -17 +17 @@ Use an AWS CloudFormation template to create the stack: - 1. Launch the AWS CloudFormation stack on the AWS CloudFormation console by choosing one of the **Launch Stack** buttons in the following table: + 1. Launch the CloudFormation stack on the CloudFormation console by choosing one of the **Launch Stack** buttons in the following table: @@ -79 +79 @@ When a VPC endpoint is created with this flag enabled, all API Gateway traffic i - 6. On the **Review** page, select the first check box to acknowledge that AWS CloudFormation will create IAM resources. Select the second check box to acknowledge `CAPABILITY_AUTO_EXPAND` for the new stack. + 6. On the **Review** page, select the first check box to acknowledge that CloudFormation will create IAM resources. Select the second check box to acknowledge `CAPABILITY_AUTO_EXPAND` for the new stack. @@ -83 +83 @@ When a VPC endpoint is created with this flag enabled, all API Gateway traffic i -`CAPABILITY_AUTO_EXPAND` explicitly acknowledges that macros will be expanded when creating the stack, without prior review. Users often create a change set from a processed template so that the changes made by macros can be reviewed before actually creating the stack. For more information, see the AWS CloudFormation [CreateStack](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html) API. +`CAPABILITY_AUTO_EXPAND` explicitly acknowledges that macros will be expanded when creating the stack, without prior review. Users often create a change set from a processed template so that the changes made by macros can be reviewed before actually creating the stack. For more information, see the CloudFormation [CreateStack](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html) API. @@ -92 +92 @@ Then choose **Create**. -After the Neptune-Export installation has completed, update your [Neptune VPC security group](./get-started-vpc.html#security-vpc-security-group) to allow access from Neptune-Export. When the Neptune-Export AWS CloudFormation stack has been created, the **Outputs** tab includes a `NeptuneExportSecurityGroup` ID. Update your Neptune VPC security group to allow access from this Neptune-Export security group. +After the Neptune-Export installation has completed, update your [Neptune VPC security group](./get-started-vpc.html#security-vpc-security-group) to allow access from Neptune-Export. When the Neptune-Export CloudFormation stack has been created, the **Outputs** tab includes a `NeptuneExportSecurityGroup` ID. Update your Neptune VPC security group to allow access from this Neptune-Export security group. @@ -96 +96 @@ After the Neptune-Export installation has completed, update your [Neptune VPC se -If you make your Neptune-Export endpoint VPC-only, you can only access it from within the VPC in which the Neptune-Export service is installed. To allow connectivity from an Amazon EC2 instance in the VPC from which you can make Neptune-Export API calls, attach the `NeptuneExportSecurityGroup` created by the AWS CloudFormation stack to that Amazon EC2 instance. +If you make your Neptune-Export endpoint VPC-only, you can only access it from within the VPC in which the Neptune-Export service is installed. To allow connectivity from an Amazon EC2 instance in the VPC from which you can make Neptune-Export API calls, attach the `NeptuneExportSecurityGroup` created by the CloudFormation stack to that Amazon EC2 instance.