AWS billingconductor documentation change
Summary
Removed two sentences about request signing requirements using IAM credentials or AWS STS temporary security credentials
Security assessment
While the removed content relates to security practices (credential usage), there is no explicit evidence this change addresses a specific security vulnerability. The removal appears to be a documentation simplification rather than a security fix.
Diff
diff --git a/billingconductor/latest/userguide/infrastructure-security.md b/billingconductor/latest/userguide/infrastructure-security.md index e1edce614..15b8a2218 100644 --- a//billingconductor/latest/userguide/infrastructure-security.md +++ b//billingconductor/latest/userguide/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access Billing Conductor 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. -