AWS solutions documentation change
Summary
Added instructions to remove 'custom:' prefix from Cognito User Pool attribute in hub and spoke templates, and added note about manual deletion of pre-v3.0.0 peering attachments
Security assessment
The changes involve configuration updates for Cognito attributes and procedural notes about attachment management. No security vulnerabilities, exploits, or security features are mentioned. Cognito attribute changes are routine configuration adjustments without security implications.
Diff
diff --git a/solutions/latest/network-orchestration-aws-transit-gateway/Migrate-the-Hub-stack-optional.md b/solutions/latest/network-orchestration-aws-transit-gateway/Migrate-the-Hub-stack-optional.md index 65ed027bd..85064177c 100644 --- a//solutions/latest/network-orchestration-aws-transit-gateway/Migrate-the-Hub-stack-optional.md +++ b//solutions/latest/network-orchestration-aws-transit-gateway/Migrate-the-Hub-stack-optional.md @@ -22,0 +23,8 @@ You cannot directly update solution v1 to latest due to breaking changes in late +Edit the template to remove the `custom:` prefix from the Cognito User Pool attribute: + + # Change from: + Name: custom:CognitoUserGr + + # To: + Name: CognitoUserGr + @@ -43,0 +52,8 @@ For spoke template, follow the steps provided in [Spoke stack](./update-the-spok +Edit the template to remove the `custom:` prefix from the Cognito User Pool attribute: + + # Change from: + Name: custom:CognitoUserGr + + # To: + Name: CognitoUserGr + @@ -54,0 +71,4 @@ For spoke template, follow the steps provided in [Spoke stack](./update-the-spok +###### Note + +If you created peering attachments using solution versions before v3.0.0 and then upgraded to v3.0.0 or later, those attachments cannot be deleted by updating the tag value on the transit gateway. You will need to delete them manually. +