AWS lake-formation documentation change
Summary
Updated references from 'AWS CloudFormation' to 'CloudFormation' for consistency in terminology
Security assessment
The changes are purely editorial, standardizing product name references without altering security-related content. No security vulnerabilities, mitigations, or security features are mentioned or modified in these changes.
Diff
diff --git a/lake-formation/latest/dg/managing-dl-tutorial.md b/lake-formation/latest/dg/managing-dl-tutorial.md index 4c00f1a8b..3aa5c786e 100644 --- a//lake-formation/latest/dg/managing-dl-tutorial.md +++ b//lake-formation/latest/dg/managing-dl-tutorial.md @@ -132 +132 @@ The stack creation can take up to five minutes. -After you complete the tutorial, you might want to delete the stack in AWS CloudFormation to avoid continuing to incur charges. Verify that the resources are successfully deleted in the event status for the stack. +After you complete the tutorial, you might want to delete the stack in CloudFormation to avoid continuing to incur charges. Verify that the resources are successfully deleted in the event status for the stack. @@ -142 +142 @@ In this step, the data steward user defines the tag ontology with two LF-Tags: ` - 1. Sign in to the Lake Formation console at [https://console.aws.amazon.com/lakeformation/](https://console.aws.amazon.com/lakeformation/) as `lf-data-steward` with the password used while deploying the AWS CloudFormation stack. + 1. Sign in to the Lake Formation console at [https://console.aws.amazon.com/lakeformation/](https://console.aws.amazon.com/lakeformation/) as `lf-data-steward` with the password used while deploying the CloudFormation stack. @@ -237 +237 @@ You have created all the necessary LF-Tags for this exercise. - 5. For **Storage locations** , enter the Amazon S3 bucket created by the AWS CloudFormation template `(s3://lf-tagbased-demo-`Account-ID`)`. + 5. For **Storage locations** , enter the Amazon S3 bucket created by the CloudFormation template `(s3://lf-tagbased-demo-`Account-ID`)`. @@ -328 +328 @@ In this step, you create two databases and attach LF-Tags to the databases and s - 4. For **Location** , enter the Amazon S3 location created by the AWS CloudFormation template `(s3://lf-tagbased-demo-`Account-ID`/tag_database/)`. + 4. For **Location** , enter the Amazon S3 location created by the CloudFormation template `(s3://lf-tagbased-demo-`Account-ID`/tag_database/)`. @@ -348 +348 @@ In this step, you create two databases and attach LF-Tags to the databases and s - 7. For Include path, enter the path to `tag_database` created by the AWS CloudFormation template `(s3://lf-tagbased-demo`Account-ID`/tag_database/)`. + 7. For Include path, enter the path to `tag_database` created by the CloudFormation template `(s3://lf-tagbased-demo`Account-ID`/tag_database/)`. @@ -477 +477 @@ Repeat the following steps to create the database `col_tag_database` and table ` - 3. For **Location** , enter the Amazon S3 location created by the AWS CloudFormation template `(s3://lf-tagbased-demo-`Account-ID`/col_tag_database/)`. + 3. For **Location** , enter the Amazon S3 location created by the CloudFormation template `(s3://lf-tagbased-demo-`Account-ID`/col_tag_database/)`. @@ -773 +773 @@ To prevent unwanted charges to your AWS account, you can delete the AWS resource - 3. Sign into the Amazon S3 console as the account owner using the IAM credentials you used to deploy the AWS CloudFormation stack. + 3. Sign into the Amazon S3 console as the account owner using the IAM credentials you used to deploy the CloudFormation stack. @@ -781 +781 @@ To prevent unwanted charges to your AWS account, you can delete the AWS resource - 5. Sign into AWS CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/), and delete the stack you created. Wait for the stack status to change to `DELETE_COMPLETE`. + 5. Sign into CloudFormation console at [https://console.aws.amazon.com/cloudformation](https://console.aws.amazon.com/cloudformation/), and delete the stack you created. Wait for the stack status to change to `DELETE_COMPLETE`.