Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse

Cloudron Forum

Apps | Demo | Docs | Install

aws route 53 domain set up

Scheduled Pinned Locked Moved Solved Support
domainsroute53
3 Posts 2 Posters 20 Views
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • ShaiS Offline
    ShaiS Offline
    Shai
    wrote on last edited by girish
    #1

    I haven't done this in awhile. I did remember to add AWS domain id to the "policy" which gives permissions to API calls to Route53.

    But I don't remember where to get the Access Key ID or the Secret access key. I clicked on "Users" at IAM and nothing looks right there. I have several domains whose DNS is at AWS so I've done this before. I can see the access_id used on those other domains but I can't find a secret associated with that access_Id. Uggh, it's a problem when you don't do this stuff very often.

    Thanks for the help.

    1 Reply Last reply
    1
  • nebulonN Offline
    nebulonN Offline
    nebulon Staff
    wrote on last edited by nebulon
    #2

    There are some links from our docs for Route53, maybe those help depending on if you use IAM or root accounts https://docs.cloudron.io/domains/#route53-dns

    The AWS UI is so hard to understand, that I also have to start fresh each time I log in.

    1 Reply Last reply
    2
  • ShaiS Offline
    ShaiS Offline
    Shai
    wrote on last edited by
    #3

    @nebulon Thanks. Ohh, I was so close last night. Your post gave me the courage to plunge back in. The username I gave to the user who owns the policy was a really wierd choice several years ago. So when I went to the aws users page, I didn't think of exploring there. Also the ID and secret were in a file on my local machine, filed well with a good file name. Last night I just wasn't careful in looking for it. So I'm all good now.

    1 Reply Last reply
    0
  • girishG girish marked this topic as a question on
  • girishG girish has marked this topic as solved on

  • Login

  • Don't have an account? Register

  • Login or register to search.
  • First post
    Last post
0
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Login

  • Don't have an account? Register

  • Login or register to search.