Hosting Elastic Beanstalk Docker Image, expose via Route 53 and secure with HTTPS












0















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.










share|improve this question

























  • Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.

    – Kunal Nagpal
    Nov 22 '18 at 22:17
















0















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.










share|improve this question

























  • Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.

    – Kunal Nagpal
    Nov 22 '18 at 22:17














0












0








0








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.










share|improve this question
















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






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Nov 28 '18 at 15:46









Flimzy

38.5k106597




38.5k106597










asked Nov 21 '18 at 21:23









jjuser19jjjjuser19jj

5221722




5221722













  • Could you also share details on the CloudFront distribution's origin settings? This could be where the issue is.

    – Kunal Nagpal
    Nov 22 '18 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 '18 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 '18 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 '18 at 22:17












0






active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















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

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







Popular posts from this blog

"Incorrect syntax near the keyword 'ON'. (on update cascade, on delete cascade,)

Alcedinidae

Origin of the phrase “under your belt”?