-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
route53-targets: Add support for GraphqlApiDomainTarget #26109
Comments
It makes sense to me. We welcome and appreciate your PR if it's ready. Thank you for your contribution. |
It also makes sense for multi-region deployment, in the context of a disaster recovery implementation. |
I also had to use the workaround provided by @thesnups. |
Comments on closed issues and PRs are hard for our team to see. |
1 similar comment
Comments on closed issues and PRs are hard for our team to see. |
Describe the feature
Implement
GraphqlApiDomainTarget
inaws-cdk-lib/aws-route53-targets
to facilitate easily configuring A records for AppSync APIs with custom domains.Use Case
https://github.com/aws/aws-cdk/tree/main/packages/aws-cdk-lib/aws-route53-targets is missing an
IAliasRecordTarget
implementation for AWS AppSync GraphQL APIs. The AppSync docs suggest the use of a CNAME for custom domains, but that is not an option for me because I cannot create a CNAME at the apex of the hosted zone. Also, the Route 53 console UI supports AppSync domains as an alias target, and that should be reflected in CDK.Proposed Solution
I am currently using the following workaround in my project:
I based this implementation on the
UserPoolDomainTarget
, and it seems to work. Unsure if there is a different, preferable approach. Here it is in use:Other Information
No response
Acknowledgements
CDK version used
2.85.0
Environment details (OS name and version, etc.)
Mac OS
The text was updated successfully, but these errors were encountered: