API Gateway stage-to-backend integration has no client certificate
- Severity
- Low
- Service
- API Gateway
- Check ID
- APIGW_NO_CLIENT_CERT
What this check finds
This API Gateway stage does not use a client certificate for backend integration. Without mutual TLS, the backend cannot verify that requests originate from API Gateway.
Passing looks like: API Gateway backend integration uses a client certificate.
How to fix it
Generate a client certificate and associate it with the stage.
AWS CLI
aws apigateway generate-client-certificateThen attach it to the stage:
aws apigateway update-stage --rest-api-id API_ID --stage-name STAGE --patch-operations op=replace,path=/clientCertificateId,value=CERT_ID
Names in capitals are placeholders for your own resource. Review a command before you run it.
AWS console
API Gateway → Stage → Settings → Client Certificate.
Compliance controls it is evidence for
A failing result counts against these controls in KloudLytics; a passing one is evidence towards them. How compliance mapping works
| Framework | Controls |
|---|---|
| NIST SP 800-53 Rev5 (Moderate) |
|
| NIST Cybersecurity Framework 2.0 |
|
| ISO/IEC 27001:2022 Annex A |
|
Checked on every scan
KloudLytics runs this check each time it scans a connected AWS account, through a read-only role, and lists every affected resource with its region. On Pro and Business a fix is written for the specific resource rather than the general case above. The exact access it needs
More API Gateway checks
- HighAPI Gateway execute-api endpoint not disabled — CloudFront WAF bypassable
- HighAPI Gateway REST API method has no authorization
- HighHTTP API (v2) has no JWT authorizer configured
- HighPrivate API has no resource policy restricting access
- MediumAPI Gateway custom domain TLS minimum version below 1.2
- MediumAPI Gateway REST API has no request validators configured
- MediumAPI Gateway stage not associated with a WAF Web ACL
- LowAPI Gateway stage does not have access logging enabled