AWS Access Key Id is not registered as an Amazon Associate

@bazajaytee

I would not call it “user error” when three separate registrations are required and it takes this much effort to find them all. The process is not clearly documented, and their program should only require one registration.

Thank you for your post I spent hours looking for how to solve this problem,and your post solved it in 1 second.

Glad it worked for you too @isaaa

Their documentation definitely needs an overhaul and their error messaging in the app itself could use some work to show what was actually wrong.

same issue; and there isn’t any solve for me.

I’m trying to plug in but gives me same error;
Your AWS Access Key Id is not registered as an Amazon Associate. Please verify that you are registered as an Amazon Associate in respective locale and you added the email address registered for the Product Advertising API as a secondary email address in your Amazon Associates account.

I’ve done everything, root keys im using but nothing change. Please help

• This reply was modified 7 years, 7 months ago by ozyedi.

I was having the same problem as Bazajaytee and contacted Amazon twice to resolve. Neither support person asked about having an API account. Thank you for the link above because that fixed my problem and now the plugin works. Yay!

You were far more fortunate than I was, craftina2017.

I first heard from a gal who referred me to a link where she said I was to outline my problem; and if I had not heard back from anyone by something like the middle of the following month, I was to respond directly back to her.

Well, no one answered my query by her deadline; but when I E-mailed back the gal who had given me the link, she never got around to replying, either.

And then suddenly my Amazon.co.uk Associates account became inaccessible. Each time I tried to access it with either of the two E-mail addresses I had been using, the declaration came that neither address belonged an any known Associate.

So now I had to make a new enquiry ─ and that, too, was ignored. That had to have been at least three months ago.

I just gave up until about 10 days ago when I learned about Amazon’s new OneLink feature that will tie in Amazon.com, Amazon.ca, and Amazon.co.uk ─ provided that the Associate has an account with each of those Amazons.

I had to set up a new account at Amazon.co.uk and turn my back on the small balance I already had in my lost original Associate account; and I also had to apply for an Amazon.ca Associate account, for I never had one.

But oddly, once I had the new Amazon.co.uk Associate account, I discovered that the plugin now worked after I replaced my old Associate ID with the new one! Keep in mind that I had periodically tried out the Associates Link Builder plugin all along every couple or so weeks just to ensure that I was still out of the loop; and each time it had always claimed that my AWS Access Key ID was not registered as an Associate.

What is especially peculiar is that I never applied for a new Associates Access Key ID ─ the two showing up in my account include an original created back on December 5, 2009; and the most recent one created on December 18, 2016. This more recent one is the one I created in order to try to use the darned plugin!

So if I never had a previous Associates account, then why do I see these two old Access Key IDs when I have supposedly only set up an account within the past two weeks?

Something is really screwy at Amazon.co.uk