Title: binki's Replies | WordPress.org

---

# binki

  [  ](https://wordpress.org/support/users/binki/)

 *   [Profile](https://wordpress.org/support/users/binki/)
 *   [Topics Started](https://wordpress.org/support/users/binki/topics/)
 *   [Replies Created](https://wordpress.org/support/users/binki/replies/)
 *   [Reviews Written](https://wordpress.org/support/users/binki/reviews/)
 *   [Topics Replied To](https://wordpress.org/support/users/binki/replied-to/)
 *   [Engagements](https://wordpress.org/support/users/binki/engagements/)
 *   [Favorites](https://wordpress.org/support/users/binki/favorites/)

 Search replies:

## Forum Replies Created

Viewing 2 replies - 1 through 2 (of 2 total)

 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress-Amazon-Associate] [Plugin: WordPress-Amazon-Associate] Plugin reporting AWS keys as Invalid?](https://wordpress.org/support/topic/plugin-wordpress-amazon-associate-plugin-reporting-aws-keys-as-invalid/)
 *  [binki](https://wordpress.org/support/users/binki/)
 * (@binki)
 * [13 years, 11 months ago](https://wordpress.org/support/topic/plugin-wordpress-amazon-associate-plugin-reporting-aws-keys-as-invalid/#post-2975084)
 * Even though amazon’s error doesn’t give much information as to why the user is
   unable to use the API, maybe the plugin could be updated to suggest to the user
   that he may need to sign the usage agreement when it gets this “InternalError”.
   That would be awesome.
 *   Forum: [Plugins](https://wordpress.org/support/forum/plugins-and-hacks/)
    In
   reply to: [[WordPress-Amazon-Associate] [Plugin: WordPress-Amazon-Associate] Plugin reporting AWS keys as Invalid?](https://wordpress.org/support/topic/plugin-wordpress-amazon-associate-plugin-reporting-aws-keys-as-invalid/)
 *  [binki](https://wordpress.org/support/users/binki/)
 * (@binki)
 * [13 years, 12 months ago](https://wordpress.org/support/topic/plugin-wordpress-amazon-associate-plugin-reporting-aws-keys-as-invalid/#post-2975039)
 * I am experiencing the same problem. I’m not willing to downgrade from 3.4.1 to
   see if that will help, so I wonder when this will fix itself or if the plugins
   will need to be updated….

Viewing 2 replies - 1 through 2 (of 2 total)