AWS API Gateway Custom Domain Tutorial (2020)

AWS API Gateway Custom Domain Tutorial (2020)

In this video I show you how to connect a custom domain name using AWS Route 53 and AWS API Gateway.

🎓 Book a 1-on-1 Tutoring Call with me:

📚 FREE Software Development Audio Books:

📱 Discord server:

📺 Creating an API using AWS API Gateway:

💡 Have a video request?
Suggest it in our Discord server or leave it in the comments! I’ll do my best to make a video on it when I can.

📷 Check our Instagram for daily coding challenges:

🏆 Did this video help you? Consider supporting us on Patreon to receive perks:

💰 Consider donating:

⚙️ Keep switching between this video and your code editor? Use Google’s “Picture-in-Picture” Chrome Extension to view this video in a floating window:

🕐 Timestamps:
00:00 Introduction
01:03 Creating a custom subdomain
03:09 Connecting our subdomain to API Gateway
04:03 Outro

#aws #amazonwebservices #nodejs #wornoffkeys

12 thoughts on “AWS API Gateway Custom Domain Tutorial (2020)

  1. 📺 Want more content? AWS Series Playlist:
    📱 Discord Community:
    🏆 Unlock Patreon Perks:
    📺 Subscribe for More:

  2. Great video! I was confused at first as to what steps were needed to do exactly this, and after watching your video, I accomplished the task in just about 15 minutes. Thank you!

  3. Thanks for the video, great! I have my Route 53 + certificates in one account and making the API (the API Gateway) in another account. How can I get these certificates from the first account to the other, to be used in API Gateway?

  4. Thanks so much for the video! By any chance have you tried doing this with the new UI in ApiGateway? The new UI unfortunately hides the methods and resources panel, and I was unable to get it to work even when following this tutorial (maybe because they hid some configuration options that in this video you show yourself changing).

  5. Hi, nice video, thanks a lot for your explanation. It is the same process if the domain is registered in Ionos instead of Route 53? Thanks again.

Leave a Reply

Your email address will not be published. Required fields are marked *