AWS wickr documentation change
Summary
Simplified Forward Access Sessions (FAS) explanation by removing implementation details
Security assessment
Condenses FAS description without changing security posture. Maintains reference to official documentation without introducing new security content.
Diff
diff --git a/wickr/latest/adminguide/security_iam_service-with-iam-principal-permissions.md b/wickr/latest/adminguide/security_iam_service-with-iam-principal-permissions.md index 1ef22d56a..da3f50b9a 100644 --- a//wickr/latest/adminguide/security_iam_service-with-iam-principal-permissions.md +++ b//wickr/latest/adminguide/security_iam_service-with-iam-principal-permissions.md @@ -11 +11 @@ This guide documents the new AWS Wickr administration console, released on March -When you use an IAM user or role to perform actions in AWS, you are considered a principal. When you use some services, you might perform an action that then initiates another action in a different service. FAS uses the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. FAS requests are only made when a service receives a request that requires interactions with other AWS services or resources to complete. In this case, you must have permissions to perform both actions. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html). +Forward access sessions (FAS) use the permissions of the principal calling an AWS service, combined with the requesting AWS service to make requests to downstream services. For policy details when making FAS requests, see [Forward access sessions](https://docs.aws.amazon.com/IAM/latest/UserGuide/access_forward_access_sessions.html).