AWS apigateway documentation change
Summary
Added 'private integrations' to the list of integration types where contentHandling properties require CLI/CloudFormation/SDK usage
Security assessment
This clarifies tooling requirements for more integration types but does not address security features or vulnerabilities.
Diff
diff --git a/apigateway/latest/developerguide/api-gateway-payload-encodings.md b/apigateway/latest/developerguide/api-gateway-payload-encodings.md index 51fe572f7..adde73fda 100644 --- a//apigateway/latest/developerguide/api-gateway-payload-encodings.md +++ b//apigateway/latest/developerguide/api-gateway-payload-encodings.md @@ -25 +25 @@ To handle binary payloads for non-proxy integrations, you add the media types to -For `MOCK` integrations, setting the `contentHandling` properties isn't supported in the AWS Management Console. You must use the AWS CLI, AWS CloudFormation, or an SDK to set the `contentHandling` properties. +For `MOCK` or private integrations, setting the `contentHandling` properties isn't supported in the AWS Management Console. You must use the AWS CLI, AWS CloudFormation, or an SDK to set the `contentHandling` properties.