Go SDK Release Feedback

[johnduhart]

I don't see a mechanism for providing feedback about the Go SDK, so I'm opening this issue. Reviewing the examples and code published, I'm seeing a large number of packages that don't feel exactly like idiomatic Go. Package names such as awscryptographyencryptionsdksmithygeneratedtypes are not meaningful as a developer, and expecting every user to set aliases doesn't seem realistic.

Publicly exposed packages such as SerializeFunctions appear to be machine generated, don't have any documentation, and appear non-useful for end users.

Compared to the AWS Go SDK, this isn't the level of quality that I'd expect from a AWS library that's GA.

[ShubhamChaturvedi7]

Hi @johnduhart - thanks for the feedback. This is the right place for any Go Encryption SDK related feedback.

Our Encryption SDKs are not entirely written in the native language. If you look at the repo, you'd see that we write everything in Dafny and then transpile it in different languages. Our goal is to provide Encryption SDK in as many languages as possible - and Dafny allows us to do that. Being a verification-aware programming language, Dafny also offers some security properties which are desirable when implementing a cryptography library.

Dafny is ever evolving and so are our libraries. We might be able to address some of these things in future versions. In the meantime, if you need any documentation you can head over to AWS docs: https://docs.aws.amazon.com/encryption-sdk/latest/developer-guide/go.html