429 Errors

Last few days goodsync stoped working with "Too Many Requests (status code 429)". please advise what can be done

I've also begun having issues with GoodSync over the past few days. Log shows "Too many requests (status code 429): System unavailable. Please back off for a while and try again later."

Please advise.

Just started getting the 429 message today for a similar app. The official docs say that the 429 message is related to rate limits. The main developer of the app I'm using says users can go get their own API keys to work around the rate limit issue but that it is a pain in the butt to do so, which is why they bundle default API keys with their app. Why are you making it so hard to use your system? The 429 issue is obviously an ongoing problem. You also apparently don't let people delete things via your API but the web interface can, so I periodically have to go in and manually empty the trash folder (ugh). The Amazon Cloud Drive web interface is garbage, which is why the API is potentially useful - that is, the API makes Cloud Drive barely usable via other tools. Either figure out how fix your system so it works all the time - maybe make it really, really easy for an ordinary user to get and use an API key? - or get rid of the API altogether so that users can seek out a service that does work.

It's not based on IP address and it starts to get annoying. I have this now for nearly every request (about 1/100 of my requests work). There is another thread/issue on github acd-cli: https://github.com/yadayada/acd_cli/issues/74 Quite a few people seem to have this problem now, is there any official response what these limits are exactly?

We are having the same problem with our application, so all customers using us to connect to Amazon Cloud get the 429 error. I could reproduce it by simply creating a folder in the Amazon Cloud repository. Please fix this asap

The users on my app are reporting the same thing. This makes my app but completely unusable for several users. Please let us know whats happening asap.

Thank you for your post. At this time we do not publish rate limits for development and production. We have received multiple reports of developers receiving a 429 Rate Exceeded response from the Amazon Cloud Drive API. We are investigating the issue at the moment to identify the root cause. If you would like to email clouddrive-api-support@amazon.com and provide us with your client id that would be helpful. We will post more details when we have them.

We found the root cause of the issue. We enabled new throttling behavior and rolled back our changes as soon as we understood the impact to developers like yourself. The Amazon Cloud Drive API is now normalizing as the roll back nears 100% deployment. We apologize for this issue and inconvenience it may have caused you and your customers. Please feel free to email clouddrive-api-support@amazon.com if you have any further questions.

Thanks for the quick fix, Sean! It is looking much better today. Cheers!