Hosting Elastic Beanstalk Docker Image, expose via Route 53 and secure with HTTPS
up vote
0
down vote
favorite
I am trying to archive the following:
- Hosting a static webpage via S3, Cloudfront and Route 53 and secure it with HTTPS, this works.
- Expose a docker image, running a golang server via elastic beanstalk and secure it via HTTPS.
The problem is, that I can not reach the server / docker image hosted via Elastic beanstalk over https, I get a connection timed out error, when using api.domain.com, wwww.api.domain.com as well as using the Elastic Beanstalk URL. I have no problem reaching domain.com or www.domain.com via HTTPS.
Current setup:
Registrar:
www.domain.com, nameserver entries pointing to amazon.com nameservers created by AWS Route 53.
Lets encrypt certficate for the following domains:
- domain.com
- *.domain.com
AWS Route 53:
- Hostedzone for domain.com, A and AAAA antries for www.domain.com, domain.com, www.api.domain.com, api.domain.com, with alias pointing to cloudfront for domain.com and www.domain.com, and alias pointing to elastic beanstalk for www.api.domain.com, api.domain.com.
S3:
- Bucket setup to host a static webpage.
Cloudfront:
- Setup to distribute S3 bucket, with SSL certificate from Lets encrypt.
Elastic beanstalk:
- Setup to expose a docker golang image with Load Balancer, setup with the same SSL certificate as cloudfront is.
I hope some of you can point my to the right direction.
docker amazon-s3 https amazon-elastic-beanstalk
edited Nov 28 at 15:46
Flimzy
36.6k96496
asked Nov 21 at 21:23
jjuser19jj
5171622
add a comment |
up vote
0
down vote
favorite
I am trying to archive the following:
- Hosting a static webpage via S3, Cloudfront and Route 53 and secure it with HTTPS, this works.
- Expose a docker image, running a golang server via elastic beanstalk and secure it via HTTPS.
The problem is, that I can not reach the server / docker image hosted via Elastic beanstalk over https, I get a connection timed out error, when using api.domain.com, wwww.api.domain.com as well as using the Elastic Beanstalk URL. I have no problem reaching domain.com or www.domain.com via HTTPS.
Current setup:
Registrar:
www.domain.com, nameserver entries pointing to amazon.com nameservers created by AWS Route 53.
Lets encrypt certficate for the following domains:
- domain.com
- *.domain.com
AWS Route 53:
- Hostedzone for domain.com, A and AAAA antries for www.domain.com, domain.com, www.api.domain.com, api.domain.com, with alias pointing to cloudfront for domain.com and www.domain.com, and alias pointing to elastic beanstalk for www.api.domain.com, api.domain.com.
S3:
- Bucket setup to host a static webpage.
Cloudfront:
- Setup to distribute S3 bucket, with SSL certificate from Lets encrypt.
Elastic beanstalk:
- Setup to expose a docker golang image with Load Balancer, setup with the same SSL certificate as cloudfront is.
I hope some of you can point my to the right direction.
docker amazon-s3 https amazon-elastic-beanstalk
edited Nov 28 at 15:46
Flimzy
36.6k96496
asked Nov 21 at 21:23
jjuser19jj
5171622
Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.
– Kunal Nagpal
Nov 22 at 22:17
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am trying to archive the following:
- Hosting a static webpage via S3, Cloudfront and Route 53 and secure it with HTTPS, this works.
- Expose a docker image, running a golang server via elastic beanstalk and secure it via HTTPS.
The problem is, that I can not reach the server / docker image hosted via Elastic beanstalk over https, I get a connection timed out error, when using api.domain.com, wwww.api.domain.com as well as using the Elastic Beanstalk URL. I have no problem reaching domain.com or www.domain.com via HTTPS.
Current setup:
Registrar:
www.domain.com, nameserver entries pointing to amazon.com nameservers created by AWS Route 53.
Lets encrypt certficate for the following domains:
- domain.com
- *.domain.com
AWS Route 53:
- Hostedzone for domain.com, A and AAAA antries for www.domain.com, domain.com, www.api.domain.com, api.domain.com, with alias pointing to cloudfront for domain.com and www.domain.com, and alias pointing to elastic beanstalk for www.api.domain.com, api.domain.com.
S3:
- Bucket setup to host a static webpage.
Cloudfront:
- Setup to distribute S3 bucket, with SSL certificate from Lets encrypt.
Elastic beanstalk:
- Setup to expose a docker golang image with Load Balancer, setup with the same SSL certificate as cloudfront is.
I hope some of you can point my to the right direction.
docker amazon-s3 https amazon-elastic-beanstalk
edited Nov 28 at 15:46
Flimzy
36.6k96496
asked Nov 21 at 21:23
jjuser19jj
5171622
I am trying to archive the following:
- Hosting a static webpage via S3, Cloudfront and Route 53 and secure it with HTTPS, this works.
- Expose a docker image, running a golang server via elastic beanstalk and secure it via HTTPS.
The problem is, that I can not reach the server / docker image hosted via Elastic beanstalk over https, I get a connection timed out error, when using api.domain.com, wwww.api.domain.com as well as using the Elastic Beanstalk URL. I have no problem reaching domain.com or www.domain.com via HTTPS.
Current setup:
Registrar:
www.domain.com, nameserver entries pointing to amazon.com nameservers created by AWS Route 53.
Lets encrypt certficate for the following domains:
- domain.com
- *.domain.com
AWS Route 53:
- Hostedzone for domain.com, A and AAAA antries for www.domain.com, domain.com, www.api.domain.com, api.domain.com, with alias pointing to cloudfront for domain.com and www.domain.com, and alias pointing to elastic beanstalk for www.api.domain.com, api.domain.com.
S3:
- Bucket setup to host a static webpage.
Cloudfront:
- Setup to distribute S3 bucket, with SSL certificate from Lets encrypt.
Elastic beanstalk:
- Setup to expose a docker golang image with Load Balancer, setup with the same SSL certificate as cloudfront is.
I hope some of you can point my to the right direction.
docker amazon-s3 https amazon-elastic-beanstalk
docker amazon-s3 https amazon-elastic-beanstalk
edited Nov 28 at 15:46
Flimzy
36.6k96496
asked Nov 21 at 21:23
jjuser19jj
5171622
edited Nov 28 at 15:46
Flimzy
36.6k96496
asked Nov 21 at 21:23
jjuser19jj
5171622
edited Nov 28 at 15:46
Flimzy
36.6k96496
edited Nov 28 at 15:46
Flimzy
36.6k96496
edited Nov 28 at 15:46
Flimzy
36.6k96496
36.6k96496
asked Nov 21 at 21:23
jjuser19jj
5171622
asked Nov 21 at 21:23
jjuser19jj
5171622
asked Nov 21 at 21:23
jjuser19jj
5171622
5171622
Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.
– Kunal Nagpal
Nov 22 at 22:17
add a comment |
Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.
– Kunal Nagpal
Nov 22 at 22:17
Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.
– Kunal Nagpal
Nov 22 at 22:17
Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.
– Kunal Nagpal
Nov 22 at 22:17
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53420653%2fhosting-elastic-beanstalk-docker-image-expose-via-route-53-and-secure-with-http%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.
– Kunal Nagpal
Nov 22 at 22:17