AWS blockchain-templates documentation change
Summary
Replaced 'AWS CloudFormation' with 'CloudFormation' in multiple instances for naming consistency
Security assessment
These are stylistic/naming convention updates only. The VPC prerequisite requirements (NAT Gateway, Elastic IP) remain unchanged, and there is no indication of security vulnerability fixes or new security guidance being added.
Diff
diff --git a/blockchain-templates/latest/developerguide/blockchain-templates-hyperledger.md b/blockchain-templates/latest/developerguide/blockchain-templates-hyperledger.md index 9cfee4da1..efaa40afd 100644 --- a//blockchain-templates/latest/developerguide/blockchain-templates-hyperledger.md +++ b//blockchain-templates/latest/developerguide/blockchain-templates-hyperledger.md @@ -17 +17 @@ The AWS Blockchain Template for Hyperledger Fabric only supports a _docker-local -See [Getting Started with AWS Blockchain Templates](https://aws.amazon.com/blockchain/templates/getting-started/) for links to launch AWS CloudFormation in specific Regions using the Hyperledger Fabric templates. +See [Getting Started with AWS Blockchain Templates](https://aws.amazon.com/blockchain/templates/getting-started/) for links to launch CloudFormation in specific Regions using the Hyperledger Fabric templates. @@ -37 +37 @@ Before you launch a Hyperledger Fabric network using template, make sure that th - * You must have a Amazon VPC network with a public subnet, or a private subnet with a NAT Gateway and Elastic IP address so that Amazon S3, AWS CloudFormation, and Amazon ECR can be accessed. + * You must have a Amazon VPC network with a public subnet, or a private subnet with a NAT Gateway and Elastic IP address so that Amazon S3, CloudFormation, and Amazon ECR can be accessed.