AWS amplify documentation change
Summary
Consistently replaced 'AWS CloudFormation' with 'CloudFormation' across multiple sections
Security assessment
The changes are purely editorial, standardizing service names. While the documentation discusses GitHub App authentication (a security feature), these updates do not introduce new security information or address vulnerabilities. The security implications of using personal access tokens and GitHub Apps were already documented.
Diff
diff --git a/amplify/latest/userguide/setting-up-GitHub-access.md b/amplify/latest/userguide/setting-up-GitHub-access.md index 44ea58f20..a8f6c8714 100644 --- a//amplify/latest/userguide/setting-up-GitHub-access.md +++ b//amplify/latest/userguide/setting-up-GitHub-access.md @@ -5 +5 @@ -Installing and authorizing the Amplify GitHub App for a new deploymentMigrating an existing OAuth app to the Amplify GitHub AppSetting up the Amplify GitHub App for AWS CloudFormation, CLI, and SDK deploymentsSetting up web previews with the Amplify GitHub App +Installing and authorizing the Amplify GitHub App for a new deploymentMigrating an existing OAuth app to the Amplify GitHub AppSetting up the Amplify GitHub App for CloudFormation, CLI, and SDK deploymentsSetting up web previews with the Amplify GitHub App @@ -21 +21 @@ When you deploy a new app or migrate an existing app using the Amplify console, - * Setting up the Amplify GitHub App for AWS CloudFormation, CLI, and SDK deployments + * Setting up the Amplify GitHub App for CloudFormation, CLI, and SDK deployments @@ -104 +104 @@ Use the following instructions to migrate an app and delete its corresponding OA -## Setting up the Amplify GitHub App for AWS CloudFormation, CLI, and SDK deployments +## Setting up the Amplify GitHub App for CloudFormation, CLI, and SDK deployments @@ -106 +106 @@ Use the following instructions to migrate an app and delete its corresponding OA -Existing Amplify apps that you previously connected from GitHub repositories use OAuth for repo access. This can include apps that you deployed using the Amplify Command Line Interface (CLI), AWS CloudFormation, or the SDKs. We strongly recommend that you migrate these apps to use the new Amplify GitHub App. Migration must be performed in the Amplify console in the AWS Management Console. For instructions, see Migrating an existing OAuth app to the Amplify GitHub App. +Existing Amplify apps that you previously connected from GitHub repositories use OAuth for repo access. This can include apps that you deployed using the Amplify Command Line Interface (CLI), CloudFormation, or the SDKs. We strongly recommend that you migrate these apps to use the new Amplify GitHub App. Migration must be performed in the Amplify console in the AWS Management Console. For instructions, see Migrating an existing OAuth app to the Amplify GitHub App. @@ -108 +108 @@ Existing Amplify apps that you previously connected from GitHub repositories use -You can use AWS CloudFormation, the Amplify CLI, and the SDKs to deploy a new Amplify app that uses the GitHub App for repo access. This process requires that you first install the Amplify GitHub App in your GitHub account. Next, you will need to generate a personal access token in your GitHub account. Lastly, deploy the app and specify the personal access token. +You can use CloudFormation, the Amplify CLI, and the SDKs to deploy a new Amplify app that uses the GitHub App for repo access. This process requires that you first install the Amplify GitHub App in your GitHub account. Next, you will need to generate a personal access token in your GitHub account. Lastly, deploy the app and specify the personal access token. @@ -147 +147 @@ Use the format `https://github.com/apps/aws-amplify-`REGION`/installations/new`, - 9. Copy and save the personal access token. You will need to provide it when you deploy an Amplify app with the CLI, AWS CloudFormation, or the SDKs. + 9. Copy and save the personal access token. You will need to provide it when you deploy an Amplify app with the CLI, CloudFormation, or the SDKs. @@ -152 +152 @@ Use the format `https://github.com/apps/aws-amplify-`REGION`/installations/new`, -After the Amplify GitHub app is installed in your GitHub account and you have generated a personal access token, you can deploy a new app with the Amplify CLI, AWS CloudFormation, or the SDKs. Use the `accessToken` field to specify the personal access token that you created in the previous procedure. For more information, see [CreateApp](https://docs.aws.amazon.com/amplify/latest/APIReference/API_CreateApp.html#API_CreateApp_RequestSyntax) in the _Amplify API reference_ and [AWS::Amplify::App](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-amplify-app.html) in the _AWS CloudFormation User Guide_. +After the Amplify GitHub app is installed in your GitHub account and you have generated a personal access token, you can deploy a new app with the Amplify CLI, CloudFormation, or the SDKs. Use the `accessToken` field to specify the personal access token that you created in the previous procedure. For more information, see [CreateApp](https://docs.aws.amazon.com/amplify/latest/APIReference/API_CreateApp.html#API_CreateApp_RequestSyntax) in the _Amplify API reference_ and [AWS::Amplify::App](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-amplify-app.html) in the _AWS CloudFormation User Guide_.