aws / aws/aws-appsync-community

Feature Request: Custom domain names for Private AppSync APIs

Open
#407 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
HTML
Stars
507
Forks
37
PR merge metrics
No merged PRs in 30d

Description

## Description

Custom domain names are currently supported for **public** AWS AppSync APIs (resolving [#5](https://github.com/aws/aws-appsync-community/issues/5)). However, **private** AppSync APIs (which can only be accessed from a VPC) do not support custom domain names.

## Proposed Solution

Allow associating a custom domain name with a private AWS AppSync API, as is possible for Private APIs in AWS Apigateway .

## Related

- #5 Original feature request for custom domains (for public APIs)

Contributor guide

Open the contributing guide

Research direction

Start by reading related issue #5 and the AWS AppSync private API behavior described here; no repository files or tests are named. Determine the requirements for associating a custom domain with a private API, with completion meaning private AppSync APIs support custom domains while remaining accessible only from a VPC.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, graphql
Domain
api, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.