AWS prescriptive-guidance documentation change
Summary
Fixed URL formatting in AWS Lake Formation documentation links by adding an extra slash after domain
Security assessment
The changes are purely URL formatting corrections (adding double slashes in links). No security-related content was added or modified. The existing text about data security controls and sharing methods remains unchanged.
Diff
diff --git a/prescriptive-guidance/latest/data-lake-for-growth-scale/centralized-catalog.md b/prescriptive-guidance/latest/data-lake-for-growth-scale/centralized-catalog.md index 7f37988ac..164b5652a 100644 --- a//prescriptive-guidance/latest/data-lake-for-growth-scale/centralized-catalog.md +++ b//prescriptive-guidance/latest/data-lake-for-growth-scale/centralized-catalog.md @@ -23 +23 @@ The following sections describe how the centralized catalog uses AWS Lake Format -[AWS Lake Formation](https://docs.aws.amazon.com/lake-formation/latest/dg/what-is-lake-formation.html) helps create databases in an AWS Glue Data Catalog that point to the locations of multiple data producers in your data lake. An AWS Identity and Access Management (IAM) role is created for Lake Formation in the centralized catalog. By using Lake Formation, the centralized catalog can selectively share data resources (for example, database, tables, or columns) with data consumers. The Lake Formation managed resources are shared with data consumers by using one of the following two methods: +[AWS Lake Formation](https://docs.aws.amazon.com//lake-formation/latest/dg/what-is-lake-formation.html) helps create databases in an AWS Glue Data Catalog that point to the locations of multiple data producers in your data lake. An AWS Identity and Access Management (IAM) role is created for Lake Formation in the centralized catalog. By using Lake Formation, the centralized catalog can selectively share data resources (for example, database, tables, or columns) with data consumers. The Lake Formation managed resources are shared with data consumers by using one of the following two methods: @@ -25 +25 @@ The following sections describe how the centralized catalog uses AWS Lake Format - * [Named resource method](https://docs.aws.amazon.com/lake-formation/latest/dg/granting-cat-perms-named-resource.html) – This method shares managed resources across accounts. Databases, tables, or column names must be specified and a resource can be shared to an organization, organizational unit (OU), or AWS account. To reduce the sharing and management overhead, we recommend that you share resources at higher levels where possible (for example, in an organization or OU instead of an AWS account) . However, you must make sure that this approach meets your organization's data security control requirements. + * [Named resource method](https://docs.aws.amazon.com//lake-formation/latest/dg/granting-cat-perms-named-resource.html) – This method shares managed resources across accounts. Databases, tables, or column names must be specified and a resource can be shared to an organization, organizational unit (OU), or AWS account. To reduce the sharing and management overhead, we recommend that you share resources at higher levels where possible (for example, in an organization or OU instead of an AWS account) . However, you must make sure that this approach meets your organization's data security control requirements. @@ -29 +29 @@ The following sections describe how the centralized catalog uses AWS Lake Format - * [Lake Formation tag-based access control (LF-TBAC) method](https://docs.aws.amazon.com/lake-formation/latest/dg/granting-catalog-perms-TBAC.html) – LF-TBAC is particularly useful for data consumers with a data-serving type. However, Lake Formation tagged resources can currently only be shared at the AWS account level and not at the organization or OU level. + * [Lake Formation tag-based access control (LF-TBAC) method](https://docs.aws.amazon.com//lake-formation/latest/dg/granting-catalog-perms-TBAC.html) – LF-TBAC is particularly useful for data consumers with a data-serving type. However, Lake Formation tagged resources can currently only be shared at the AWS account level and not at the organization or OU level.