Don't panic when behavior-version-latest (or major version) not set

[k-bx]

Describe the feature

I've deployed my program to production server and it panics because I didn't put "behavior-version-latest" in my Cargo.toml. The code that communicates with the storage is totally optional so I'm catching any "Err"-response upon connection and just log it. To my surprise, it crashed the whole runtime which is not great.

Use Case

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

A note for the community

No response

[aajtodd]

Thanks for the feedback. This is documented behavior but I understand that it resulted in a frustrating experience.

The recommended way to create service clients is through the aws-config crate, you can find documentation on creating a service client this way in the developer guide.

I'm going to close this as it's expected behavior.

[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.