AWS Request Rate
kapil.thangavelu at canonical.com
Thu Feb 20 15:12:13 UTC 2014
1) try firewall-mode: global
juju is trying to create sec groups per machine, which hopefully can get
better with a move to vpc (dynamic sec groups on instances). That should
reduce aws api usage a bit for machine provisioning.
2. afaicr for a given failed provisioning request, there is no retry in
3. its across all users on the same account against a given region. if your
using iam for separate users, the rate limit is still against the
underlying account., each api has its own throttle rate.
On Thu, Feb 20, 2014 at 10:02 AM, David Britton <david.britton at canonical.com
> Hi Juju Folks --
> I've been getting this from time to time:
> agent-state-info: '(error: cannot set up groups: Request limit
> exceeded. (RequestLimitExceeded))'
> instance-id: pending
> series: precise
> Which lead me to this:
> Which says this:
> Amazon EC2 API requests are throttled to help maintain the performance
> of the service. If your requests have been throttled, you'll get the
> following error: Client.RequestLimitExceeded. For more information, see
> Query API Request Rate in the Amazon Elastic Compute Cloud User Guide.
> Some questions:
> 1) Is there something I can do to prevent this? I'm deploying a stack
> with juju-deployer.
> 2) When it happens, it seems that juju is dead in the water on that
> operation (in this case launching an instnace). Should it instead
> throttle back and keep trying? I have to terminate-machine,
> destroy-service, and re-run deployer (which thankfully picks up where it
> left off). Is that expected behavior for the juju system?
> 3) This is a shared Amazon account, is this requestLimit across all of
> the people that have api credentials, or just me?
> David Britton <david.britton at canonical.com>
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Juju