ECS capacity errors have inconsistent behavior. about aws-sdk-ruby HOT 2 CLOSED

Hi @bensherman ,

Thanks for reaching out. The SDK maps the returned service error to the predefined list of errors specified by this service in their API model.

In ECS's RunTask documentation, ClientException is in fact a modeled exception that can be returned for this specific operation. While I agree that the service should have modeled a better exception name for this specific case, the SDK team cannot directly introduce new Exceptions since the SDK is directly code-generated from the API model of each API service.

From a service perspective, changing the returned exception will be considered a breaking change since some customers may be explicitly relying on this error when error handling capacity exceptions.

Because of this, this is not actionable by the SDK team.

I do however I agree that the documentation is too narrow and does not cover this specific case:

ClientException

These errors are usually caused by a client action. This client action might be using an action or resource on behalf of a user that doesn't have permissions to use the action or resource. Or, it might be specifying an identifier that isn't valid.

HTTP Status Code: 400

I will create a documentation request with the ECS service team to expand the definition of this exception to match this specific undocumented edge case, but we cannot commit to a timeline of the fix since the change would need to be made by the ECS team itself and not the SDK team. If you wish you can submit additional documentation related feedback using the Feedback button on the top right of each documentation page.

Thanks again,
Ran~

from aws-sdk-ruby.

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

from aws-sdk-ruby.