AWS sagemaker-unified-studio documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for terminology consistency
Security assessment
The changes are purely terminological adjustments (removing redundant 'AWS' prefix). No security vulnerabilities or security feature enhancements are mentioned. The emphasis remains on user responsibility for auditing exported files.
Diff
diff --git a/sagemaker-unified-studio/latest/userguide/app-export.md b/sagemaker-unified-studio/latest/userguide/app-export.md index 7ff040de6..0ada337ff 100644 --- a//sagemaker-unified-studio/latest/userguide/app-export.md +++ b//sagemaker-unified-studio/latest/userguide/app-export.md @@ -11 +11 @@ With Amazon Bedrock in SageMaker Unified Studio, you can export the files for an -When you export an app, Amazon Bedrock in SageMaker Unified Studio exports a zip file with the AWS CloudFormation templates and other files required by your app. To use your app, you need to deploy the AWS CloudFormation templates to an AWS account. The actual contents of the zip file vary on the Amazon Bedrock in SageMaker Unified Studio components that your app uses. After uncompressing the zip file, you deploy the contents of the zip file into your AWS account (or another AWS account, if you prefer). +When you export an app, Amazon Bedrock in SageMaker Unified Studio exports a zip file with the AWS CloudFormation templates and other files required by your app. To use your app, you need to deploy the CloudFormation templates to an AWS account. The actual contents of the zip file vary on the Amazon Bedrock in SageMaker Unified Studio components that your app uses. After uncompressing the zip file, you deploy the contents of the zip file into your AWS account (or another AWS account, if you prefer). @@ -15 +15 @@ When you export an app, Amazon Bedrock in SageMaker Unified Studio exports a zip -Once you export your app, it's your responsibility to audit the app files and make sure they are correct. You can use the AWS CloudFormation templates as you wish. +Once you export your app, it's your responsibility to audit the app files and make sure they are correct. You can use the CloudFormation templates as you wish. @@ -25 +25 @@ Depending on the composition of your app, the zip package contains some or all o - * **function-stack-*.json** — AWS CloudFormation template that creates your function component, if any. This includes: + * **function-stack-*.json** — CloudFormation template that creates your function component, if any. This includes: @@ -33 +33 @@ Depending on the composition of your app, the zip package contains some or all o - * **flow-stack.json** — AWS CloudFormation template that creates an Amazon Bedrock flows resource. + * **flow-stack.json** — CloudFormation template that creates an Amazon Bedrock flows resource. @@ -35 +35 @@ Depending on the composition of your app, the zip package contains some or all o - * **guardrails-stack-*.json** — AWS CloudFormation template that creates a [guardrail](https://docs.aws.amazon.com/bedrock/latest/studio-ug/guardrails.html) for Amazon Bedrock, if any. + * **guardrails-stack-*.json** — CloudFormation template that creates a [guardrail](https://docs.aws.amazon.com/bedrock/latest/studio-ug/guardrails.html) for Amazon Bedrock, if any. @@ -37 +37 @@ Depending on the composition of your app, the zip package contains some or all o - * **agent-stack.json** — AWS CloudFormation template that creates an Amazon Bedrock Agent, if any. + * **agent-stack.json** — CloudFormation template that creates an Amazon Bedrock Agent, if any. @@ -39 +39 @@ Depending on the composition of your app, the zip package contains some or all o - * **invocation-policy-*.json** — AWS CloudFormation template that creates an IAM policy with the runtime permissions that you need to talk to your deployed chat agent app. + * **invocation-policy-*.json** — CloudFormation template that creates an IAM policy with the runtime permissions that you need to talk to your deployed chat agent app.