Why isn't CloudFront serving my domain name over HTTPS?

Aug 16, 2023

Why isn't CloudFront serving my domain name over HTTPS?

For more details see the Knowledge Center article with this video: https://repost.aws/knowledge-center/c…
Rohit shows you why CloudFront isn’t serving your domain name over HTTPS.

Content

0 -> (upbeat music)

12.46 -> - Hello.

13.293 -> I'm Rohit, a cloud support engineer

14.855 -> here at AWS office in Bangalore, India.

18.29 -> Today I'm going to show you what you can do

20.971 -> if Amazon CloudFront is not serving a domain

24.75 -> even though you have already added the SSL certificate

27.89 -> for the domain in the CloudFront distribution.

30.13 -> Let's get started.

31.66 -> As you can see, I'm already logged

33.78 -> in into the AWS management console.

36.53 -> From here, navigate to the CloudFront console.

45.21 -> First, added the, already created distribution setting

49.38 -> and configure the domain name

50.686 -> into the alternate domain name filled.

54.33 -> For this example, I'm using my custom domain name

57.48 -> www.rohitcf.info

61.77 -> If you requesting an SSL certificate,

64.31 -> then be sure that SSL certificate has a domain name

68.06 -> that you want to add as an alternate domain name

71.63 -> in your CloudFront distribution setting.

74.17 -> When you add an alternate domain name to the distribution,

77.41 -> CloudFront check whether or not that alternate domain name

81.42 -> is covered by the certificate that you have attached.

91.13 -> I want to highlight www.rohitcf.info

98.48 -> Click to request or import an SSL certificate from from ACM.

103.71 -> Or you can also upload and import

106.75 -> an SSL certificate to the IM using AWS CLA .

111.03 -> I am using ACM in this video.

119.89 -> In the new tab, ACM that opens.

122.86 -> Add the alternate domain into the domain name section.

126.36 -> I have added the SSL certificate like

129.877 -> *.rohitcf.info

140.8 -> Choose next.

142.8 -> Then, choose a process to validate that you own

146.67 -> or control the domain that you

148.89 -> are requesting the certificate for.

151.7 -> You can validate ownership by using DNS

154.81 -> or by sending an email to the contact address

157.59 -> of the domain owner.

159.35 -> I choose DNS validation, then I click to review

163 -> and confirm the request.

171.99 -> In this example, I am using Route 53 as a DNS provider.

176.36 -> So, I click to create record in Route 53.

182.97 -> Click to continue.

187.81 -> Then the SSL certificate is validated and issue.

192.23 -> Then go back to the CloudFront console

194.92 -> and refresh the browser to see your certificate

197.78 -> in the custom SSL certificate section.

201.213 -> You should able to view the newly added certificate

204.9 -> into your custom SSL certificate section.

220.59 -> Add the alternate domain name into the CNAME section

224.03 -> and choose yes to add it.

229.55 -> Your custom domain name is configured on CloudFront.

233.05 -> Now, wind your domain name to the CloudFront.

236.29 -> I have the demonstrated this in the video using Route 53.

241.1 -> If you are not using Route 53 to manage your domain,

245.1 -> then reach out to your DNS provider if you need assistance

248.96 -> to create the CNAME record.

252.15 -> Move to the Route 53 console.

260.8 -> In the Route 53 console, choose the hosted zone,

264.55 -> then choose the custom domain name

267.14 -> from the list of hosted zone.

272.31 -> If the custom name is the apex domain,

275.74 -> then click record set with type A.

281.66 -> Choose alias yes and then choose the CloudFront distribution

286.44 -> from the alias target list.

289.19 -> In my example, I am making use of subdomain

292.7 -> that is www.rohitcf.info

296.7 -> is winding to the CloudFront.

298.65 -> Now, click to create.

302.73 -> To confirm that your domain is winding

305.38 -> to CloudFront, you can use the dig or nslookup command.

330.83 -> When your domain name winds to CloudFront successfully,

334.28 -> then open your browser and access

336.48 -> your domain name using HTTPS.

340.17 -> Now you can access the domain successfully.

345.35 -> Thanks for watching and happy cloud computing

347.34 -> from all of us here at AWS.

349.118 -> (upbeat music)

Source: https://www.youtube.com/watch?v=vBJ4KnDzbqg