AWS quicksight documentation change
Summary
Updated terminology to use 'QuickSight' instead of 'Amazon QuickSight' in multiple definitions and explanations
Security assessment
Changes are branding/terminology updates rather than security-related modifications. Existing security concepts like row-level security with tag-based rules are mentioned but not altered in functionality.
Diff
diff --git a/quicksight/latest/developerguide/terminology-and-concepts.md b/quicksight/latest/developerguide/terminology-and-concepts.md index 28d1cac15..9dbd1a9b3 100644 --- a//quicksight/latest/developerguide/terminology-and-concepts.md +++ b//quicksight/latest/developerguide/terminology-and-concepts.md @@ -9 +9 @@ Following, you can find a list of terms and concepts used to describe Amazon Qui -**Anonymous QuickSight user** – A temporary Amazon QuickSight user identity that virtually belongs to a namespace and that you can use only with embedding. You can use tag-based rules to implement row-level security for such users. +**Anonymous QuickSight user** – A temporary QuickSight user identity that virtually belongs to a namespace and that you can use only with embedding. You can use tag-based rules to implement row-level security for such users. @@ -11 +11 @@ Following, you can find a list of terms and concepts used to describe Amazon Qui -**Caller identity** – The identity of the IAM user making an API request. The identity of the caller is determined by Amazon QuickSight using the signature attached to the request. Through the use of our provided SDK clients, no manual steps are necessary to generate the signature or attach it to the requests. However, you can do it manually if you want to. +**Caller identity** – The identity of the IAM user making an API request. The identity of the caller is determined by QuickSight using the signature attached to the request. Through the use of our provided SDK clients, no manual steps are necessary to generate the signature or attach it to the requests. However, you can do it manually if you want to. @@ -13 +13 @@ Following, you can find a list of terms and concepts used to describe Amazon Qui -**Invoker identity** – In addition to the caller identity, but not as a replacement for it, you can assume a caller's identity through the IAM `AssumeRole` API operation when making calls to Amazon QuickSight. AWS approves callers through their invoker’s identity. This approval means that you can avoid having to explicitly add multiple accounts belonging to the same Amazon QuickSight subscription. +**Invoker identity** – In addition to the caller identity, but not as a replacement for it, you can assume a caller's identity through the IAM `AssumeRole` API operation when making calls to QuickSight. AWS approves callers through their invoker’s identity. This approval means that you can avoid having to explicitly add multiple accounts belonging to the same QuickSight subscription. @@ -17 +17 @@ Following, you can find a list of terms and concepts used to describe Amazon Qui -**QuickSight ARN** – Amazon Resource Name (ARN). Amazon QuickSight resources are identified using their name or ARN. For example, the following are ARNs for a group named `MyGroup1`, a user named `User1`, and a dashboard with the ID `1a1ac2b2-3fc3-4b44-5e5d-c6db6778df89`. +**QuickSight ARN** – Amazon Resource Name (ARN). QuickSight resources are identified using their name or ARN. For example, the following are ARNs for a group named `MyGroup1`, a user named `User1`, and a dashboard with the ID `1a1ac2b2-3fc3-4b44-5e5d-c6db6778df89`. @@ -55 +55 @@ Depending on the scenario, you might need to provide an entity's name, ID, or AR -**QuickSight user** – This is an Amazon QuickSight user identity acted on by your API call. This user isn't identical to the caller identity but might be the one that maps to the user in Amazon QuickSight. +**QuickSight user** – This is an QuickSight user identity acted on by your API call. This user isn't identical to the caller identity but might be the one that maps to the user in QuickSight.