-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add custom DNS to API Gateway Endpoint #18
Comments
@chand1012 you should have access to the domain on namecheap now |
@chand1012 can we use |
I figured that we'd want |
As far as I'm aware we can use api.deephire.com for all of our services [image:
image.png]
https://aws.amazon.com/blogs/compute/architecting-multiple-microservices-behind-a-single-domain-with-amazon-api-gateway/
…On Thu, May 13, 2021 at 9:51 AM Chandler Lofland ***@***.***> wrote:
@chand1012 <https://github.com/chand1012> can we use api.pillar.gg as the
domain name?
I figured that we'd want api.pillar.gg for another service, but we do
need that DNS on AWS anyway. Once its verified it should be a matter of
switching the DNS on CDK.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#18 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADSXBSTDQMSYG6A3A3GSKFDTNPRPJANCNFSM44DH4JHQ>
.
|
Is this done? |
Any progress on this? @chand1012 @RusseII Want to either close this out or move it to Triage/ToDo |
I haven't made any progress, the url is static as long as we don't change the names. I think we can add this to the backlog. |
Because of the nature of how AWS CDK Pipelines work (being added in #17 ), the DNS that our API is accessible at is subject to change. By giving it a custom domain name, this issue is mitigated. It seems that there is little documentation on how to add a custom domain with CDK, but here is what I found.
@RusseII and/or @gatesyp will need to help out as they have access to the DNS settings for
pillar.gg
. We may want to do this either with the addition of #17 or before we add it in.The text was updated successfully, but these errors were encountered: