1 Answers
1
As per the doc (https://docs.aws.amazon.com/apigateway/latest/developerguide/rest-api-mutual-tls.html), private APIs don't support mutual TLS.
In order to do that, you would need something like: Client -> NLB -> Proxy (to handle mTLS) -> interface VPC endpoint for API Gateway -> private API
You can have a look at this blog post: https://aws.amazon.com/pt/blogs/aws-brasil/suportando-mutual-tls-mtls-utilizando-certificados-do-icp-brasil-para-o-open-banking-no-brasil-utilizando-o-amazon-api-gateway/, it's in Portuguese but you will see the architecture, and can probably translate.
answered 8 months ago
Relevant questions
Mutual TLS for AWS Lambda Function URL
asked 4 months agoMutual TLS with Commercial Client Certificates
asked 4 months agoHTTP API Gateway - HTTP URI Integration fails when query contains spaces
asked 2 months agoAPI Gateway Private Integration with multiple NLB listeners
Accepted Answerasked 3 years agoHttp API Gateway using stage variables on a private integration
asked 8 months agoSupporting mutual TLS on specific resource paths
asked 6 months agoBuild a REST API with API Gateway private integration: Tutorial
Accepted Answerasked 5 months agoAmazon API Gateway Proxy - VPC Endpoint - NLB - Private DNS - Self-signed SSL
Accepted Answerasked 2 years agoAWS API Gateway private integration with mutual TLS
asked 8 months agoHttp API Gateway with lambda integration for multiple routes
Accepted Answerasked 2 years ago
I'm aware that mutual TLS for private API gateways are not supported, but in my case I'm using public API gateway with VPC link. Shouldn't this configuration be supported, as only difference between functional and nonfunctional configurations is to swap lambda integration with VPC link integration?