Totally different APIs and programming paradigm in AWS SDK at least between its Java and Golang versions

[michaelmnguyen]

Describe the bug

As a Best Practice, any SDK should provide the same APIs, regardless of the programming languages. The only difference should be the syntax among the programming languages. Could AWS do that for its SDK at least between Java and Golang ? As is, AWS APIs and their paradigms at least between Java and Golang are totally different.

Expected Behavior

The same APIs and programming paradigm in AWS SDK at least between its Java and Golang versions.

Current Behavior

Totally different APIs and programming paradigm in AWS SDK at least between its Java and Golang versions

Reproduction Steps

Compare differences between

https://pkg.go.dev/github.com/aws/aws-sdk-go-v2/credentials/ec2rolecreds
and

https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/auth/InstanceProfileCredentialsProvider.html

It is as if they are for totally different SDKs. For instance, Golang version of AWS SDK does not have the equivalent code for InstanceProfileCredentialsProvider.

Possible Solution

The same APIs and programming paradigm in AWS SDK at least between its Java and Golang versions.

Additional Information/Context

No response

SDK version used

1.44.137

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

Golang v1.19 and the latest Java JDK

[RanVaknin]

Hi Michael,

Since we already addressed this in your previous thread and there is an action item to fix the documentation on imds on Go I'm going to assign this a documentation label and keep this issue as tracking.

Thanks,
Ran

[michaelmnguyen]

That's fine Ran.

Thanks.

Michael,

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