API Credentials for Amazon Route 53

Guide to obtaining tokens, keys, and connections.

Botize needs three pieces of information from your AWS account: the region (Availability Zone) where your Route 53 service runs, an Access Key ID, and a Secret Access Key. The recommended approach is to create a dedicated IAM user for Botize with only the Route 53 permissions it needs — never use your AWS root credentials.

Availability zone

  1. 1

    Sign in to your AWS Console at https://console.aws.amazon.com.

  2. 2

    Look at the top-right corner of the console. Next to your account name you will see the current region (for example, "N. Virginia"). Click it to see the region identifier (for example, "us-east-1").

  3. 3

    Note: Route 53 is a global service; for the region field you can use "us-east-1" by default, or the region closest to where you operate.

  4. 4

    Go to Botize and paste the region identifier (for example, "us-east-1") into the "Availability zone" field in the connection form.

Credential Key and Credential Secret

  1. 1

    In the AWS Console, open the IAM service: search for "IAM" in the top search bar and click the result.

  2. 2

    In the left sidebar, click "Users" and then "Create user".

  3. 3

    Give the user a name (for example, "botize-route53") and click "Next".

  4. 4

    On the permissions page, choose "Attach policies directly". Search for and select "AmazonRoute53FullAccess" (or a more restrictive Route 53 policy if you prefer). Click "Next" and then "Create user".

  5. 5

    Open the newly created user. Go to the "Security credentials" tab and click "Create access key".

  6. 6

    Choose the "Application running outside AWS" use case (or "Third-party service"), confirm, and click "Create access key".

  7. 7

    AWS shows the Access Key ID (starts with "AKIA") and the Secret Access Key only once. Copy both immediately — if you close this page without copying the secret, you will need to create a new key.

  8. 8

    Go to Botize. Paste the Access Key ID into the "Credential Key" field and the Secret Access Key into the "Credential Secret" field in the connection form.