• Resolved jocelyn72s

    (@jocelyn72s)


    Hi all,

    I tried several time to configure the plugin properly but it never accepts my access key. I tried to generate a new one but it did not work too.
    How can I solve it?

Viewing 4 replies - 1 through 4 (of 4 total)
  • I am getting the same error, tried a couple new api ID/keys to no avail. The documentation is dated when trying to setup.

    Hello

    Folow the link below:

    https://console.aws.amazon.com/iam/home#/users/yourusernameher?section=security_credentials

    there you can see your keys make them inactive and then

    1-Create New access key
    2 – Upload your public key & Secret
    3- Use Them in The Application

    I hope this can help everyone

    • This reply was modified 7 years, 11 months ago by ebayastore1413. Reason: mistake
    Thread Starter jocelyn72s

    (@jocelyn72s)

    The issue was solved: I filled the first field with an invalid parameter.
    Now it works fine.

    • This reply was modified 7 years, 11 months ago by jocelyn72s.
    • This reply was modified 7 years, 11 months ago by jocelyn72s.
    Plugin Author Amazon Associates Link Builder

    (@amazonlinkbuilder)

    To retrieve your security credentials:

    1. Sign in your AWS account at AWS Security Credentials Console. Use the same email address and password as you used for signing up for the Amazon Product Advertising API.
    2. A pop-up message appears. Click Continue to Security Credentials.
      Click Access Keys (Access Key ID and Secret Key).
    3. Click Create New Access Key, and then click Show Access Key or Download Key File to retrieve the credentials.
    4. Save the access key information in a safe location. You will use these credentials to make calls to the Product Advertising API.

    Important

    1. You can access the secret access key only when you first create an access key pair. For security reasons, it cannot be retrieved at any later time. Ensure that you save both the access key ID and its matching secret key. If you lose them, you must create a new access key pair.
    2. IAM roles are not currently supported. You must use the root account credentials.
Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘No Secret Key is accepted’ is closed to new replies.