AWS solutions documentation change
Summary
Formatting changes including URL encoding fixes, parameter syntax corrections, and consolidation of note sections into parameter descriptions. Updates to VPC configuration parameters and Bedrock agent references.
Security assessment
Changes primarily involve documentation formatting and parameter syntax. While some parameters relate to security components (Cognito, IAM, VPC configurations), there's no evidence these changes address specific vulnerabilities or security incidents. The modifications restructure existing security-related documentation rather than adding new security features.
Diff
diff --git a/solutions/latest/generative-ai-application-builder-on-aws/deploying-a-standalone-agent-use-case.md index 12f0ea3f7..480780af4 100644 --- a/solutions/latest/generative-ai-application-builder-on-aws/deploying-a-standalone-agent-use-case.md +++ b/solutions/latest/generative-ai-application-builder-on-aws/deploying-a-standalone-agent-use-case.md @@ -13 +13 @@ Follow the step-by-step instructions in this section to configure and deploy th -**BedrockAgent.template** | [  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/quickcreate?&templateURL=https://solutions-reference.s3.amazonaws.com/generative-ai-application-builder-on-aws/latest/BedrockAgent.template&redirectId=ImplementationGuide) +**BedrockAgent.template** | [  ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/quickcreate?&templateURL=https://solutions-reference.s3.amazonaws.com/generative-ai-application-builder-on-aws/latest/BedrockAgent.template&redirectId=ImplementationGuide) @@ -24 +24 @@ This solution uses Amazon Bedrock, which is not currently available in all AWS R - 4. On the **Specify stack details** page, assign a name to your solution stack. For information about naming character limitations, see [IAM and AWS STS quotas](https://docs.aws.amazon.com/https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-limits.html) in the _AWS Identity and Access Management User Guide_. + 4. On the **Specify stack details** page, assign a name to your solution stack. For information about naming character limitations, see {https---docs-aws-amazon-com-https---docs-aws-amazon-com-IAM-latest-UserGuide-reference-iam-limits-html}[IAM and AWS STS quotas] in the _AWS Identity and Access Management User Guide_. @@ -30,2 +30,2 @@ Parameter | Default entry | Description -**UseCaseConfigRecordKey** | ``<Requires input>`` | Key corresponding to the record that contains configurations required by the chat provider Lambda function at runtime. The record in the table must have a **key** attribute matching this value, and a **config** attribute containing the desired configuration. This record will be populated by the deployment platform if it’s in use. For standalone deployments of this use case, a manually created entry in the table defined in **UseCaseConfigTableName** is required. -**UseCaseConfigTableName** | ``<Requires input>`` | The stack will read the use case configuration from the table provided here and using the record key defined in **UseCaseConfigRecordKey**. +**UseCaseConfigRecordKey** | `<Requires input>` | Key corresponding to the record that contains configurations required by the chat provider Lambda function at runtime. The record in the table must have a **key** attribute matching this value, and a **config** attribute containing the desired configuration. This record will be populated by the deployment platform if it’s in use. For standalone deployments of this use case, a manually created entry in the table defined in **UseCaseConfigTableName** is required. +**UseCaseConfigTableName** | `<Requires input>`` | The stack will read the use case configuration from the table provided here and using the record key defined in **UseCaseConfigRecordKey**. @@ -34,5 +34 @@ Parameter | Default entry | Description -**ExistingCognitoUserPoolId** | _(Optional input)_ | **UserPoolId** of an existing Amazon Cognito user pool that you want to authenticate this use case with. - -###### Note - -You typically provide this ID when deploying from the Deployment dashboard, but you can omit it when deploying this use case stack standalone. +**ExistingCognitoUserPoolId** | _(Optional input)_ | **UserPoolId** of an existing Amazon Cognito user pool that you want to authenticate this use case with. NOTE: You typically provide this ID when deploying from the Deployment dashboard, but you can omit it when deploying this use case stack standalone. @@ -40,5 +36 @@ You typically provide this ID when deploying from the Deployment dashboard, but -**ExistingCognitoGroupPolicyTableName** | _(Optional input)_ | Name of the DynamoDB table containing user group policies. This is used by the custom authorizer on the use case’s API. - -###### Note - -You typically provide this name when deploying from the Deployment dashboard, but you can omit it when deploying this use case stack standalone. +**ExistingCognitoGroupPolicyTableName** | _(Optional input)_ | Name of the DynamoDB table containing user group policies. This is used by the custom authorizer on the use case’s API. NOTE: You typically provide this name when deploying from the Deployment dashboard, but you can omit it when deploying this use case stack standalone. @@ -46,27 +38,7 @@ You typically provide this name when deploying from the Deployment dashboard, bu -**CreateNewVpc** | ` No ` | Select `Yes` if you want the solution to create a new VPC for you and to use it for this use case. - -###### Note - -This parameter is only relevant if **VpcEnabled** is `Yes`. -**IPAMPoolId** | _(Optional input)_ | If you want to assign the CIDR range using IPAM, provide the IPAM pool ID to use. - -###### Note - -This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. -**ExistingVpcId** | _(Optional input)_ | VPC ID of an existing VPC to be used for the use case. - -###### Note - -This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. -**ExistingPrivateSubnetIds** | _(Optional input)_ | Comma separated list of subnet IDs of existing private subnets to be used to deploy the Lambda function. - -###### Note - -This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. -**ExistingSecurityGroupIds** | _(Optional input)_ | Comma-separated list of security groups of the existing VPC to be used for configuring Lambda functions. - -###### Note - -This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. -**BedrockAgentId** | ``<Requires input>`` | The ID of the Amazon Bedrock Agent to be used. -**BedrockAgentAliasId** | ``<Requires input>`` | The alias ID of the Amazon Bedrock Agent to be used. +**CreateNewVpc** | `No` | Select `Yes` if you want the solution to create a new VPC for you and to use it for this use case. NOTE: This parameter is only relevant if **VpcEnabled** is `Yes`. +**IPAMPoolId** | _(Optional input)_ | If you want to assign the CIDR range using IPAM, provide the IPAM pool ID to use. NOTE: This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. +**ExistingVpcId** | _(Optional input)_ | VPC ID of an existing VPC to be used for the use case. NOTE: This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. +**ExistingPrivateSubnetIds** | _(Optional input)_ | Comma separated list of subnet IDs of existing private subnets to be used to deploy the Lambda function. NOTE: This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. +**ExistingSecurityGroupIds** | _(Optional input)_ | Comma-separated list of security groups of the existing VPC to be used for configuring Lambda functions. NOTE: This parameter is only relevant if **VpcEnabled** is `Yes` and **CreateNewVpc** is `No`. +**BedrockAgentId** | `<Requires input>` | The ID of the Amazon Bedrock Agent to be used. +**BedrockAgentAliasId** | `<Requires input>` | The alias ID of the Amazon Bedrock Agent to be used.