Broken Default Dynamodb DescribeTimeToLive Behavior

[real-mday]

Critical SDK bug

• I confirm that this issue is to report a critical defect in the SDK, one that severely or completely inhibits my usage of the v1 AWS SDK for Go, for which there is no workaround.

Describe the bug

This tool https://aws-controllers-k8s.github.io/community/docs/contributor-docs/code-generation/ automatically generates controllers based on the aws-sdk-go schema. Currently this auto generated schema includes DescribeTimeToLive which can only be used 30 times per minute and that limit is not defined so it creates broken tools downstream

Regression Issue

• Select this option if this issue appears to be a regression.

Expected Behavior

Expect that the polling behavior is defined in the schema

Current Behavior

Current behavior is tools downstream are getting throttled

Reproduction Steps

Either use the existing Dynamodb controller https://github.com/aws-controllers-k8s/dynamodb-controller or recreate the controller from the aws-sdk-go repo using the How To here https://aws-controllers-k8s.github.io/community/docs/contributor-docs/code-generation/

Possible Solution

Include definition of maximum polling in the schema

Additional Information/Context

No response

SDK version used

v1.55.7

Environment details (Version of Go (go version)? OS name and version, etc.)

go 1.23

[lucix-aws]

What schema are you referring to?

Also, does the DescribeTimeToLive operation (however this thing is generating it) work atomically? Like, can it make an API call and get a response?

If yes then this isn't really a critical defect.

[real-mday]

This is the schema https://github.com/aws/aws-sdk-go/blob/main/models/apis/dynamodb/2012-08-10/api-2.json#L356 This is a critical defect because if the api includes this endpoint but does not restrict its use then any account with more than 30 tables will stop having a responsive api within a minute

[real-mday]

Removing this completely from the schema would be another valid solution

[lucix-aws]

AWS API schemas don't model their rate limits like you're implying, so this isn't really actionable. This sounds like something the calling application just needs to account for.

[github-actions]

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.