-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AppScaling DescribeScalingPolices FailedResourceAccessException due to throttling #1472
Labels
service-api
This issue is due to a problem in a service API, not the SDK implementation.
Comments
jasdel
added
the
service-api
This issue is due to a problem in a service API, not the SDK implementation.
label
Aug 15, 2017
s-maj
changed the title
DescribeScalingPolices FailedResourceAccessException due to throttling
AppScaling DescribeScalingPolices FailedResourceAccessException due to throttling
Aug 15, 2017
Looking at the
|
Cheers. |
s-maj
pushed a commit
to s-maj/terraform-provider-aws
that referenced
this issue
Aug 16, 2017
nbaztec
pushed a commit
to nbaztec/terraform-provider-aws
that referenced
this issue
Sep 26, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version of AWS SDK for Go?
aws-sdk-go/1.8.34
Version of Go (
go version
)?go1.8.3; darwin; amd64
What issue did you see?
On DescribeScalingPolices, due to throttling, I am getting:
FailedResourceAccessException: Unable to retrieve alarms for scaling policy $policy_arn due to reason: Rate exceeded (Service: AmazonCloudWatch; Status Code: 400; Error Code: Throttling; Request ID: ce1253eb-81e9-11e7-ba0a-dd79b677bd46)
From what I understand DescribeScalingPolices is doing DescribeAlarms on behalf and this call is being throttled. FailedResourceAccessException is a very general error and I'm not quite sure how to handle it. I can retry but what if there is a real permission problem or the alarm resource does not exist anymore?
Steps to reproduce
DescribeScalingPolices very fast using tons of resources
The text was updated successfully, but these errors were encountered: