AWS solutions documentation change
Summary
Updated references from 'solution' to 'guidance' and clarified VPC endpoint requirements
Security assessment
Terminology updates and clarification of existing network security requirements (VPC endpoints) that were already part of the documentation. No new security controls added.
Diff
diff --git a/solutions/latest/clickstream-analytics-on-aws/pipeline-management.md b/solutions/latest/clickstream-analytics-on-aws/pipeline-management.md index 405b2d488..84deea665 100644 --- a//solutions/latest/clickstream-analytics-on-aws/pipeline-management.md +++ b//solutions/latest/clickstream-analytics-on-aws/pipeline-management.md @@ -3 +3 @@ -[Documentation](/index.html)[Clickstream Analytics on AWS](https://aws.amazon.com/solutions/implementations/clickstream-analytics-on-aws)[Implementation Guide](solution-overview.html) +[Documentation](/index.html)[Guidance for Clickstream Analytics on AWS](https://aws.amazon.com/solutions/guidance/clickstream-analytics-on-aws/)[Implementation Guide](solution-overview.html) @@ -9 +9 @@ Prerequisites -Data pipeline is the core functionality of this solution. In the Clickstream Analytics on AWS solution, we define a data pipeline as a sequence of integrated AWS services that ingest, process, and model the clickstream data into a destination data warehouse for analytics and visualization. It is also designed to efficiently and reliably collect data from your websites and apps to a S3-based data lake, where it can be further processed, analyzed, and utilized for additional use cases (such as real-time monitoring, and recommendation). +Data pipeline is the core functionality of this guidance. In the Clickstream Analytics on AWS guidance, we define a data pipeline as a sequence of integrated AWS services that ingest, process, and model the clickstream data into a destination data warehouse for analytics and visualization. It is also designed to efficiently and reliably collect data from your websites and apps to a S3-based data lake, where it can be further processed, analyzed, and utilized for additional use cases (such as real-time monitoring, and recommendation). @@ -23 +23 @@ Before you start to configure the pipeline in a specific region, make sure you h - * At least two private (with NAT gateways or instances) subnets across two AZs, or at least two isolated subnets across two AZs in the VPC. If you want to deploy the solution resources in the isolated subnets, you have to create [VPC endpoints](https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/what-are-vpc-endpoints.html) for below AWS services, + * At least two private (with NAT gateways or instances) subnets across two AZs, or at least two isolated subnets across two AZs in the VPC. If you want to deploy the guidance resources in the isolated subnets, you have to create [VPC endpoints](https://docs.aws.amazon.com/whitepapers/latest/aws-privatelink/what-are-vpc-endpoints.html) for below AWS services,