AWS m2 documentation change
Summary
Updated documentation to remove 'AWS' prefix from CloudFormation references (branding standardization)
Security assessment
Changes only modify branding terminology from 'AWS CloudFormation' to 'CloudFormation' without altering security configurations, access controls, or security-related procedures. No evidence of addressing vulnerabilities or security incidents.
Diff
diff --git a/m2/latest/userguide/set-up-appstream-mf.md b/m2/latest/userguide/set-up-appstream-mf.md index 90b0ff029..6f7865a55 100644 --- a//m2/latest/userguide/set-up-appstream-mf.md +++ b//m2/latest/userguide/set-up-appstream-mf.md @@ -5 +5 @@ -PrerequisitesStep 1: Get the WorkSpaces Applications imagesStep 2: Create the stack using the AWS CloudFormation templateStep 3: Create a user in WorkSpaces ApplicationsStep 4: Log in to WorkSpaces ApplicationsStep 5: Verify buckets in Amazon S3 (optional)Next stepsClean up resources +PrerequisitesStep 1: Get the WorkSpaces Applications imagesStep 2: Create the stack using the CloudFormation templateStep 3: Create a user in WorkSpaces ApplicationsStep 4: Log in to WorkSpaces ApplicationsStep 5: Verify buckets in Amazon S3 (optional)Next stepsClean up resources @@ -19 +19 @@ This document is intended for members of the customer operations team. It descri -The steps in this tutorial are based on the downloadable AWS CloudFormation template [cfn-m2-appstream-fleet-ea-ed.yml](https://drm0z31ua8gi7.cloudfront.net/tutorials/mf/appstream/cfn-m2-appstream-fleet-ea-ed.yml). +The steps in this tutorial are based on the downloadable CloudFormation template [cfn-m2-appstream-fleet-ea-ed.yml](https://drm0z31ua8gi7.cloudfront.net/tutorials/mf/appstream/cfn-m2-appstream-fleet-ea-ed.yml). @@ -27 +27 @@ The steps in this tutorial are based on the downloadable AWS CloudFormation temp - * Step 2: Create the stack using the AWS CloudFormation template + * Step 2: Create the stack using the CloudFormation template @@ -52 +52 @@ The steps in this tutorial are based on the downloadable AWS CloudFormation temp - * create stacks in AWS CloudFormation using a template. + * create stacks in CloudFormation using a template. @@ -74 +74 @@ In this step, you share the WorkSpaces Applications images for Enterprise Analyz -## Step 2: Create the stack using the AWS CloudFormation template +## Step 2: Create the stack using the CloudFormation template @@ -76 +76 @@ In this step, you share the WorkSpaces Applications images for Enterprise Analyz -In this step, you use the downloaded AWS CloudFormation template to create an WorkSpaces Applications stack and fleet for running Rocket Enterprise Analyzer. You can repeat this step later to create another WorkSpaces Applications stack and fleet for running Rocket Enterprise Developer, since each tool requires its own fleet and stack in WorkSpaces Applications. For more information on AWS CloudFormation stacks, see [Working with stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacks.html) in the _AWS CloudFormation User Guide_. +In this step, you use the downloaded CloudFormation template to create an WorkSpaces Applications stack and fleet for running Rocket Enterprise Analyzer. You can repeat this step later to create another WorkSpaces Applications stack and fleet for running Rocket Enterprise Developer, since each tool requires its own fleet and stack in WorkSpaces Applications. For more information on CloudFormation stacks, see [Working with stacks](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/stacks.html) in the _AWS CloudFormation User Guide_. @@ -84 +84 @@ AWS Mainframe Modernization adds an additional fee to the standard WorkSpaces Ap - 2. Open the AWS CloudFormation console and choose **Create Stack** and **with new resources (standard)**. + 2. Open the CloudFormation console and choose **Create Stack** and **with new resources (standard)**. @@ -94 +94 @@ AWS Mainframe Modernization adds an additional fee to the standard WorkSpaces Ap - + @@ -110 +110 @@ AWS Mainframe Modernization adds an additional fee to the standard WorkSpaces Ap - + @@ -121 +121 @@ AWS Mainframe Modernization adds an additional fee to the standard WorkSpaces Ap -It takes between 20 and 30 minutes for the stack and fleet to be created. You can choose **Refresh** to see the AWS CloudFormation events as they occur. +It takes between 20 and 30 minutes for the stack and fleet to be created. You can choose **Refresh** to see the CloudFormation events as they occur. @@ -125 +125 @@ It takes between 20 and 30 minutes for the stack and fleet to be created. You ca -While you are waiting for AWS CloudFormation to finish creating the stack, you can create one or more users in WorkSpaces Applications. These users are those who will be using Enterprise Analyzer in WorkSpaces Applications. You will need to specify an email address for each user, and ensure that each user has sufficient permissions to create buckets in Amazon S3, upload files to a bucket, and link to a bucket to map its contents. +While you are waiting for CloudFormation to finish creating the stack, you can create one or more users in WorkSpaces Applications. These users are those who will be using Enterprise Analyzer in WorkSpaces Applications. You will need to specify an email address for each user, and ensure that each user has sufficient permissions to create buckets in Amazon S3, upload files to a bucket, and link to a bucket to map its contents. @@ -142 +142 @@ For more information on creating WorkSpaces Applications users, see [WorkSpaces -When AWS CloudFormation finishes creating the stack, you can assign the user you created to the stack, as follows: +When CloudFormation finishes creating the stack, you can assign the user you created to the stack, as follows: @@ -203 +203 @@ This process can take around 10 minutes. -One of the tasks completed by the AWS CloudFormation template you used to create the stack was to create two buckets in Amazon S3, which are necessary to save and restore user data and application settings across work sessions. These buckets are as follows: +One of the tasks completed by the CloudFormation template you used to create the stack was to create two buckets in Amazon S3, which are necessary to save and restore user data and application settings across work sessions. These buckets are as follows: @@ -227 +227 @@ To verify that the buckets were created, follow these steps: -If you see the buckets, no further action is necessary. Just be aware that the buckets exist. If you do not see the buckets, then either the AWS CloudFormation template is not finished running, or an error occurred. Go to the AWS CloudFormation console and review the stack creation messages. +If you see the buckets, no further action is necessary. Just be aware that the buckets exist. If you do not see the buckets, then either the CloudFormation template is not finished running, or an error occurred. Go to the CloudFormation console and review the stack creation messages.