AWS greengrass documentation change
Summary
Removed details about request signing using IAM credentials and AWS STS temporary security credentials
Security assessment
The removal of authentication mechanism documentation reduces clarity on securing API access but lacks explicit evidence of addressing a security vulnerability. While authentication is security-related, the change itself does not reference a specific security issue or fix.
Diff
diff --git a/greengrass/v1/developerguide/infrastructure-security.md b/greengrass/v1/developerguide/infrastructure-security.md index 7af1de1d7..27d4b84c5 100644 --- a//greengrass/v1/developerguide/infrastructure-security.md +++ b//greengrass/v1/developerguide/infrastructure-security.md @@ -20,2 +19,0 @@ You use AWS published API calls to access AWS IoT Greengrass 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. -