AWS mediaconvert high security documentation change
Summary
Removed a critical paragraph explaining that API requests must be signed with IAM credentials or AWS STS temporary security credentials.
Security assessment
The deleted content described a fundamental security requirement (request signing) for API access. Omitting this could mislead users into insecure configurations, creating a potential authentication bypass risk. This is concrete evidence of a security documentation gap.
Diff
diff --git a/mediaconvert/latest/ug/infrastructure-security.md b/mediaconvert/latest/ug/infrastructure-security.md index 4cb19c462..bfd083cb3 100644 --- a//mediaconvert/latest/ug/infrastructure-security.md +++ b//mediaconvert/latest/ug/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access MediaConvert 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. -