-
-
Notifications
You must be signed in to change notification settings - Fork 162
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
Support DNS verification via AWS Route53 #51
Comments
@PaulDMendoza - out of curiosity, have you looked into using https://aws.amazon.com/certificate-manager/ for your HTTPS certificate generation? If you are running your services on AWS, this may provide what you need without the overhead of Let's Encrypt. I haven't tried it myself with an ASP.NET Core app, but I happen to know the folks at AWS who work on .NET support and they may be able to help if you're running into issues. |
Actually, don't worry about this. I ended up just buying an SSL cert from
Namecheap for $7 for this backend server. Seems to work fine now.
I use certificate manager for my public facing stuff with API Gateway. But
private API Gateway endpoints are accessible with the Client VPN it seems
and I don't want to extra pay for the ELB. So I just opted to use an EC2
instance where I public my ASP.NET Core app to and run Kestrel web server.
…On Mon, Feb 17, 2020 at 8:51 PM Nate McMaster ***@***.***> wrote:
@PaulDMendoza <https://github.com/PaulDMendoza> - out of curiosity, have
you looked into using https://aws.amazon.com/certificate-manager/ for
your HTTPS certificate generation? If you are running your services on AWS,
this may provide what you need without the overhead of Let's Encrypt. I
haven't tried it myself with an ASP.NET Core app, but I happen to know
the folks at AWS who work on .NET support and they may be able to help if
you're running into issues.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#51>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAH53MZLDPS72B735BTKAQDRDNSN3ANCNFSM4KW47QYQ>
.
--
*Paul Mendoza*
*C: (760) 917-3753*
*mendoza.paul@gmail.com <mendoza.paul@gmail.com>*
|
Ok, thanks for the additional info. |
Is your feature request related to a problem? Please describe.
Opening on behalf of @PaulDMendoza. In #29 (comment) he said
This library currently only supports HTTP verification which requires the server endpoint be exposed to Let's Encrypt CA servers.
Additional context
This is also a pre-requisite for #1
The text was updated successfully, but these errors were encountered: