Skip to content
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

Figure out how to use an ACM certificate #1

Open
waldoj opened this issue Nov 27, 2017 · 4 comments
Open

Figure out how to use an ACM certificate #1

waldoj opened this issue Nov 27, 2017 · 4 comments

Comments

@waldoj
Copy link
Member

waldoj commented Nov 27, 2017

AWS Certificate Manager can issue the certificate, as long as the site is behind Cloudfront. (Or other services, but that's the viable one here.) You can't load it onto an EC2 instance. Figure out how to do that, to make the site portable, off its current server.

@waldoj
Copy link
Member Author

waldoj commented Nov 27, 2017

I set up a new CloudFront distribution for the site. I think that's going to be enough to do the trick? (I can't say for sure, because the new distribution is "In Progress.")

@waldoj
Copy link
Member Author

waldoj commented Nov 27, 2017

All that remains is to disable the certificate on the EC2 instance and see how that goes.

@waldoj
Copy link
Member Author

waldoj commented Nov 28, 2017

Huh. I broke it. Having seen that the CloudFront distribution process was complete, I pointed Route 53 at the distribution, and then modified the CloudFront distribution to specify api.richmondsunlight.com as a CNAME. That resulted in every API query returning this:

ERROR

The request could not be satisfied.

Bad request.
I've removed that CNAME from the distribution, and monitored the DNS record in Route 53 to just use an A record pointing to the server's IP address, and all's well again.

I'm going to open a new issue to sort out the matter of CloudFront.

@waldoj
Copy link
Member Author

waldoj commented Nov 28, 2017

Re: the topic of this issue, I think I need to revert the API to HTTP, route all traffic via CloudFront, and direct CloudFront to interface with EC2 via HTTP, and that'll do it. Of course, traffic is unencrypted within AWS' environment, but since this is all public data, that shouldn't be a problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant