You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Utility should work for instance endpoints and cluster endpoint the same way. Looks like utility only produces output with cluster endpoint. Customer may want to just use reader endpoint dedicated to graphql in production environments.
The text was updated successfully, but these errors were encountered:
Thanks for opening up the issue, I agree that the ability to restrict the AppSync API to a single reader would be a useful addition.
This can currently be achieved manually by opening the data sources in AppSync, finding the data source lambda function, opening the lambda functions configuration tab, and editing the NEPTUNE_HOST environment variable.
triggan
changed the title
Instance endpoint support
Instance, Reader, and Custom endpoint support
Mar 26, 2024
Changing the request to be a broader. We also need to investigate splitting mutation/query APIs across both cluster and reader endpoints respectively. This would allow reads to scale beyond a single instance.
We also do not currently have the ability to support custom endpoints beyond a user manually modifying the NEPTUNE_HOST environment variable in the associated lambda function.
Utility should work for instance endpoints and cluster endpoint the same way. Looks like utility only produces output with cluster endpoint. Customer may want to just use reader endpoint dedicated to graphql in production environments.
The text was updated successfully, but these errors were encountered: