AWS lookout-for-vision high security documentation change
Summary
Removed details about requiring signed requests using IAM access keys or AWS STS temporary credentials.
Security assessment
The removal of explicit guidance on signing requests with IAM credentials or temporary security tokens could impact authentication practices. This change might lead to confusion about secure API access requirements, though it's unclear if the service's actual security controls were altered. The original text emphasized critical security mechanisms (access keys, STS), so its deletion raises concerns about documentation accuracy.
Diff
diff --git a/lookout-for-vision/latest/developer-guide/infrastructure-security.md b/lookout-for-vision/latest/developer-guide/infrastructure-security.md index 1aac0c631..285a7b509 100644 --- a//lookout-for-vision/latest/developer-guide/infrastructure-security.md +++ b//lookout-for-vision/latest/developer-guide/infrastructure-security.md @@ -20,2 +19,0 @@ You use AWS published API calls to access Lookout for Vision through the network -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. -