AWS solutions documentation change
Summary
Condensed parameter descriptions, merged notes into parameter text, and updated formatting for deployment instructions
Security assessment
Changes include formatting updates to existing GDPR compliance notes and parameter descriptions, but no new security features or vulnerability mitigations are introduced. The GDPR-related note about manual data deletion was already present in prior documentation.
Diff
diff --git a/solutions/latest/unified-profiles-for-travelers-and-guests-on-aws/step-1-launch-the-stack.md b/solutions/latest/unified-profiles-for-travelers-and-guests-on-aws/step-1-launch-the-stack.md index d69ef052c..c93c97be9 100644 --- a/solutions/latest/unified-profiles-for-travelers-and-guests-on-aws/step-1-launch-the-stack.md +++ b/solutions/latest/unified-profiles-for-travelers-and-guests-on-aws/step-1-launch-the-stack.md @@ -11,3 +11 @@ Follow the step-by-step instructions in this section to configure and deploy the - 1. Sign in to the [AWS Management Console](https://console.aws.amazon.com/console/) and select the button to launch the `ucp.template` AWS CloudFormation template. - -[  ](https://console.aws.amazon.com/cloudformation/home#/stacks/new?templateURL=https://solutions-reference.s3.amazonaws.com/unified-profiles-for-travelers-and-guests-on-aws/latest/ucp.template&redirectId=ImplementationGuide) + 1. Sign into [AWS Management Console](https://aws.amazon.com/console) and select the button to launch `ucp.template` CloudFormation template. [  ](https://console.aws.amazon.com/cloudformation/home#/stacks/new?templateURL=https://solutions-reference.s3.amazonaws.com/unified-profiles-for-travelers-and-guests-on-aws/latest/ucp.template&redirectId=ImplementationGuide) @@ -25,4 +23 @@ Parameter | Default | Description -**FrontendDeploymentOption** | `CloudFront` | This parameter allows you to choose the frontend deployment option: - * Deploys frontend on Amazon CloudFront - * Deploys in a web service with Amazon ECS - * No frontend deployed (headless) +**FrontendDeploymentOption** | `CloudFront` | This parameter allows you to choose the frontend deployment option: **Deploys frontend on Amazon CloudFront** Deploys in a web service with Amazon ECS ** No frontend deployed (headless) @@ -30,15 +25,3 @@ Parameter | Default | Description -**customerProfileStorageMode** | `true` | Enable profile replication in Amazon Connect Customer profiles. - -###### Note - -At least one of the two parameters **customerProfileStorageMode** and **dynamoStorageMode** must be set to `true`. -**dynamoStorageMode** | `true` | Enable profile replication in DynamoDB. - -###### Note - -At least one of the two parameters **customerProfileStorageMode** and **dynamoStorageMode** must be set to `true`. -**enableRealtimeBackup** | `false` | Enable or disable (default) the real-time backup. If enabled, all messages sent to the solution’s Kinesis stream will be automatically backed up in Amazon S3. - -###### Note - -Enabling this option requires user to manually locate and delete profiles to comply with privacy laws like GDPR. The privacy search and delete does not include the backup bucket. +**customerProfileStorageMode** | `true` | Enable profile replication in Amazon Connect Customer profiles. NOTE: At least one of the two parameters **customerProfileStorageMode** and **dynamoStorageMode** must be set to `true`. +**dynamoStorageMode** | `true` | Enable profile replication in DynamoDB.NOTE: At least one of the two parameters **customerProfileStorageMode** and **dynamoStorageMode** must be set to `true`. +**enableRealtimeBackup** | `false` | Enable or disable (default) the real-time backup. If enabled, all messages sent to the solution’s Kinesis stream will be automatically backed up in Amazon S3. NOTE: Enabling this option requires user to manually locate and delete profiles to comply with privacy laws like GDPR. The privacy search and delete does not include the backup bucket. @@ -49 +32 @@ Enabling this option requires user to manually locate and delete profiles to co -**skipjobrun** | `true` | If set to `false`, the jobs will run incrementally every two hours, Job-based ingestion is recommended primarily for historical data ingestion. By default, the details flag issetto true. User can start these jobs from the solution' s frontend screen. +**skipjobrun** | `true` | If set to `false`, the jobs will run incrementally every two hours, Job-based ingestion is recommended primarily for historical data ingestion. By default, the details flag issetto true. User can start these jobs from the solution’s frontend screen. @@ -55,5 +38 @@ Enabling this option requires user to manually locate and delete profiles to co -**logLevel** | `INFO` | Sets logging verbosity from most (DEBUG) to least (ERROR) verbose. - -###### Note - -Debug mode can amount to significant CloudWatch log cost at scale. +**logLevel** | `INFO` | Sets logging verbosity from most (DEBUG) to least (ERROR) verbose.NOTE: Debug mode can amount to significant CloudWatch log cost at scale.