Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    ACME Provider and Route 53 - doesn't ask for Zone ID

    Scheduled Pinned Locked Moved ACME
    2 Posts 2 Posters 824 Views
    Loading More Posts
    • 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.
    • R
      rain
      last edited by

      Hi There,

      In the ACME package when you select Route53, it prompts for the API ID (which is the AWS Access Key ID) and the API Key (which is the AWS secret key), but it does not ask for the Zone ID.

      In the Dynamic DNS it asks for all three and works well.

      Initially when I asked for the certificate it actually created the cert, but it did not create the DNS entry. I'm guessing this is expected/acceptable behavior? I still need to use Dynamic DNS to create the DNS entry?

      Would be grateful for an explanation.

      With regards,

      Tim

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        ACME only updates TXT records, it has nothing to do with dynamic DNS for regular A/AAAA records. The package does not share any code or functionality with dynamic DNS in the base system.

        The ACME package only asks for what the acme.sh dnsapi script for Route53 wants (dns_aws.sh) and that is only the AWS Access Key ID and secret.

        Remember: Upvote with the πŸ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.