AWS singlesignon documentation change
Summary
Updated documentation links by adding double slashes after domain in multiple URLs
Security assessment
The changes only modify URL formatting (adding double slashes after domain) without altering security-related content. No evidence of addressing vulnerabilities or security incidents. Existing security references (e.g., 'fine-grained access controls') remain unchanged.
Diff
diff --git a/singlesignon/latest/userguide/tip-tutorial-lf.md b/singlesignon/latest/userguide/tip-tutorial-lf.md index dd53cc5ce..9f4ede103 100644 --- a//singlesignon/latest/userguide/tip-tutorial-lf.md +++ b//singlesignon/latest/userguide/tip-tutorial-lf.md @@ -9 +9 @@ PrerequisitesSteps to set up trusted identity propagationTrusted identity propag -[AWS Lake Formation](https://docs.aws.amazon.com/lake-formation/latest/dg/what-is-lake-formation.html) is a managed service that simplifies the creation and management of data lakes on AWS. It automates data collection, cataloging, and security, providing a centralized repository for storing and analyzing diverse data types. Lake Formation offers fine-grained access controls and integrates with various AWS analytics services, enabling organizations to efficiently set up, secure, and derive insights from their data lakes. +[AWS Lake Formation](https://docs.aws.amazon.com//lake-formation/latest/dg/what-is-lake-formation.html) is a managed service that simplifies the creation and management of data lakes on AWS. It automates data collection, cataloging, and security, providing a centralized repository for storing and analyzing diverse data types. Lake Formation offers fine-grained access controls and integrates with various AWS analytics services, enabling organizations to efficiently set up, secure, and derive insights from their data lakes. @@ -24 +24 @@ Before you can get started with this tutorial, you'll need to set up the followi - 1. **Integrate IAM Identity Center with AWS Lake Formation** following the guidance in [Connecting Lake Formation with IAM Identity Center](https://docs.aws.amazon.com/lake-formation/latest/dg/connect-lf-identity-center.html). + 1. **Integrate IAM Identity Center with AWS Lake Formation** following the guidance in [Connecting Lake Formation with IAM Identity Center](https://docs.aws.amazon.com//lake-formation/latest/dg/connect-lf-identity-center.html). @@ -28 +28 @@ Before you can get started with this tutorial, you'll need to set up the followi -**If you do not have AWS Glue Data Catalog tables** , you must create them in order to use AWS Lake Formation to grant access to IAM Identity Center users and groups. See [Creating objects in AWS Glue Data Catalog](https://docs.aws.amazon.com/lake-formation/latest/dg/populating-catalog.html) for more information. +**If you do not have AWS Glue Data Catalog tables** , you must create them in order to use AWS Lake Formation to grant access to IAM Identity Center users and groups. See [Creating objects in AWS Glue Data Catalog](https://docs.aws.amazon.com//lake-formation/latest/dg/populating-catalog.html) for more information. @@ -32 +32 @@ Before you can get started with this tutorial, you'll need to set up the followi -[Register the S3 locations](https://docs.aws.amazon.com/lake-formation/latest/dg/register-location.html) where the data of the Glue tables are stored. By doing this, Lake Formation will provision temporary access to the required S3 locations when the tables are queried, removing the need to include S3 permissions in the service role (e.g. the Athena service role configured on the WorkGroup). +[Register the S3 locations](https://docs.aws.amazon.com//lake-formation/latest/dg/register-location.html) where the data of the Glue tables are stored. By doing this, Lake Formation will provision temporary access to the required S3 locations when the tables are queried, removing the need to include S3 permissions in the service role (e.g. the Athena service role configured on the WorkGroup). @@ -44 +44 @@ This will allow Lake Formation to provision temporary IAM credentials with the n -To use these policies, replace the `italicized placeholder text` in the example policy with your own information. For additional directions, see [Create a policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_create.html) or [Edit a policy](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_manage-edit.html). The permission policy should grant access to the S3 location specified in the path: +To use these policies, replace the `italicized placeholder text` in the example policy with your own information. For additional directions, see [Create a policy](https://docs.aws.amazon.com//IAM/latest/UserGuide/access_policies_create.html) or [Edit a policy](https://docs.aws.amazon.com//IAM/latest/UserGuide/access_policies_manage-edit.html). The permission policy should grant access to the S3 location specified in the path: @@ -130 +130 @@ The IAM role created by the wizard is a service-linked role and does not include -AWS Lake Formation supports using [AWS Resource Access Manager (RAM)](https://docs.aws.amazon.com/ram/latest/userguide/what-is.html) to share tables across AWS accounts and it works with trusted identity propagation when the grantor account and grantee account are in the same AWS Region, in the same AWS Organizations, and share the same organization instance of IAM Identity Center. See [Cross-account data sharing in Lake Formation](https://docs.aws.amazon.com/lake-formation/latest/dg/cross-data-sharing-lf.html) for more information. +AWS Lake Formation supports using [AWS Resource Access Manager (RAM)](https://docs.aws.amazon.com//ram/latest/userguide/what-is.html) to share tables across AWS accounts and it works with trusted identity propagation when the grantor account and grantee account are in the same AWS Region, in the same AWS Organizations, and share the same organization instance of IAM Identity Center. See [Cross-account data sharing in Lake Formation](https://docs.aws.amazon.com//lake-formation/latest/dg/cross-data-sharing-lf.html) for more information.