Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

Private appsync by private dns name is not accessible

0

We have created private appsync and vpc endpoint with private dns name option enabled.

These 2 options are also enable in VPC

  1. DNS hostnames:- Enabled
  2. DNS resolution:- Enabled

Still only zone specific vpce urls are accessible but graphql endpoint is not accessible. I'm trying to call it from EKS and this error is coming

Could not resolve host:

I can't use zone specific url. How to call it directly using graphql endpoint as mentioned here

Topics
ServerlessApplication IntegrationFront-End Web & MobileNetworking & Content DeliveryContainers
Tags
AWS AppSyncAmazon VPCAmazon Elastic Kubernetes Service
Language
English
asked 2 years ago936 views
1 Answer
0

Have you considered using a Lambda function as a resolver, running inside the same VPC as the resources you want to access?

EXPERT
answered 2 years ago
  • Tanul
    2 years ago

    I'm not referring to resolver. The url is not accessible at all from any source within the vpc. No matter if it is lambda, EC2 or EKS

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content