New private API Gateway endpoints causing edge endpoints to not be accessible from VPC

aws

#1

I was excited to hear about Serverless Framework supporting AWS API Gateway private endpoints and decided to play around with them. After reading the blog post and the AWS docs, I got everything running successfully.

However, adding the VPC endpoint with DNS resolution results in all of my “Edge Optimized” API domain names (ex. *.execute-api.us-east-1.amazonaws.com) resolving to VPC IP addresses. Edge Optimized APIs still work fine from outside the VPC, but inside the VPC they return a 403 error with {“message”:“Forbidden”}.

Is there a way to authorize requests from the VPC for Edge Optimized APIs?