AWS mediaconnect high security documentation change
Summary
Removed guidance about requiring signed requests using IAM access keys or AWS STS temporary credentials
Security assessment
The removed content specified security requirements for authenticating API calls. Deleting this could mislead users about proper credential usage, potentially enabling insecure configurations where unsigned requests might be accepted. This directly impacts authentication security controls.
Diff
diff --git a/mediaconnect/latest/ug/infrastructure-security.md b/mediaconnect/latest/ug/infrastructure-security.md index 3a1f7d3d0..589e76c30 100644 --- a//mediaconnect/latest/ug/infrastructure-security.md +++ b//mediaconnect/latest/ug/infrastructure-security.md @@ -18,2 +17,0 @@ You use AWS published API calls to access MediaConnect 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. -