Skip to content
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

r/aws_appautoscaling_policy: Retry PutScalingPolicy on rate exceeded message #2275

Merged
merged 1 commit into from
Nov 15, 2017

Conversation

bflad
Copy link
Contributor

@bflad bflad commented Nov 14, 2017

Example:

* aws_appautoscaling_policy.EXAMPLE: 1 error(s) occurred:

* aws_appautoscaling_policy.EXAMPLE: Failed to create scaling policy: Error putting scaling policy: FailedResourceAccessException: Unable to create alarms for scaling policy DynamoDBReadCapacityUtilization:table/EXAMPLE due to reason: Rate exceeded (Service: AmazonCloudWatch; Status Code: 400; Error Code: Throttling; Request ID: 22fe569e-b29e-11e7-b187-ab649256b7c7)
    status code: 400, request id: 21614877-b29e-11e7-ac2e-d52b986f4ede

…message

Example:
```
* aws_appautoscaling_policy.EXAMPLE: 1 error(s) occurred:

* aws_appautoscaling_policy.EXAMPLE: Failed to create scaling policy: Error putting scaling policy: FailedResourceAccessException: Unable to create alarms for scaling policy DynamoDBReadCapacityUtilization:table/EXAMPLE due to reason: Rate exceeded (Service: AmazonCloudWatch; Status Code: 400; Error Code: Throttling; Request ID: 22fe569e-b29e-11e7-b187-ab649256b7c7)
    status code: 400, request id: 21614877-b29e-11e7-ac2e-d52b986f4ede
```
@radeksimko radeksimko added the bug Addresses a defect in current functionality. label Nov 15, 2017
Copy link
Member

@radeksimko radeksimko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the fix and example from the console output 👍

@radeksimko radeksimko merged commit 69de119 into hashicorp:master Nov 15, 2017
@ghost
Copy link

ghost commented Apr 10, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Addresses a defect in current functionality.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants