AWS chime documentation change
Summary
Removed documentation about API request signing requirements (access keys, secret keys, and AWS STS temporary credentials).
Security assessment
While authentication mechanisms are security-related, the removal of this documentation does not indicate a resolved security issue. The change reduces clarity about security practices but lacks evidence of addressing a specific vulnerability. This could negatively impact security awareness for users.
Diff
diff --git a/chime/latest/ag/infrastructure-security.md b/chime/latest/ag/infrastructure-security.md index 1efaff7c9..8e376c9eb 100644 --- a//chime/latest/ag/infrastructure-security.md +++ b//chime/latest/ag/infrastructure-security.md @@ -20,2 +19,0 @@ You use AWS published API calls to access Amazon Chime through the network. Clie -Additionally, requests must be signed by using an access key ID and a secret access key that is associated with an IAM principal. Or you can use the [AWS Security Token Service](https://docs.aws.amazon.com/STS/latest/APIReference/welcome.html) (AWS STS) to generate temporary security credentials to sign requests. -