Support » Plugin: Amazon Associates Link Builder » Access key is not recognized

  • Resolved hobbystash


    I have deleted and had new access key issued to no avail….several times. No matter what I do it will not recognize me as an Amazon Associate, which I have been for years. The old generate link, copy and paste…irritating as it is, is not as bad as trying to get this darn plug in to recognize me!! Beyond frustrated at this point.

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author Amazon Associates Link Builder


    Hi hobbystash,

    I’m sorry for the difficulty you’re having with the plugin. In order to troubleshoot the issue, can you please check the following:

    1. You are using root account credentials in the setting console. IAM credentials are not supported for Product Advertising API. If you would like to generate a new set of credentials, please follow the instructions listed in Manage Your Account.
    2. The email address used for Product Advertising API must be linked as a primary or secondary email address in your Amazon Associates account. If it is not, please follow these guidelines to add the Product Advertising API email address as a secondary user in your Amazon Associates account You will be able to successfully access Product Advertising API once the secondary user is successfully added.

    Hope that helps.
    Link Builder team

    I have same problem and have followed all the instructions at
    Manage Your Account.

    I must say your AWS / IAM, Product Advertising API documentation is confusing and seems circular. Why two registrations? Or is it three?

    AALB complains I have not registered my AWS Access key as an Amazon Associate. Both accounts are using the same email. There is only one email.

    I generated the access keys and entered the keys, and the Amazon Associates tracking ID.

    So where or how do I tie these together?

    Please provide step by step instructions – the docs are not good.

    @isaaa As opposed to the advice in the IAM console you must not create a new user for the plugin but create the access key id with the root user (your associate account user).

    With those credentials I got the plugin to connect to the AWS.

    But then I ran into the next problem. There’s another thread for this here in the forum.


Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Access key is not recognized’ is closed to new replies.