We reached out to AWS regarding the source of truth for the specification used by the different official AWS clients, since we are currently relying on the one present in the go-aws-sdk repository.
After some investigation on AWS, their response was the following:
These JSON file formats are intentionally not publicly defined. These files are generated using an internal process based on service API model definitions. While customers could reverse engineer these files, we don't provide any support for their format nor contents. So many third party SDKs rely on them that they're basically a de-facto standard at this point.
So we then asked if our current approach of using the ones from the aws-sdk-go project is the way to go for us. This was confirmed by the AWS person.
(I'm creating this issue to share and document this conversation for the future)
We reached out to AWS regarding the source of truth for the specification used by the different official AWS clients, since we are currently relying on the one present in the go-aws-sdk repository.
After some investigation on AWS, their response was the following:
So we then asked if our current approach of using the ones from the aws-sdk-go project is the way to go for us. This was confirmed by the AWS person.
(I'm creating this issue to share and document this conversation for the future)