I created an ION API with a target endpoint that matches a bucket and folder.
I loaded the AWS Access key and secret key
I have converted Amazon's AWS S3 JSON based Swagger document to YAML which is just easier to work with.
I generated the Swagger documentation and tested the input.
I invoke the default GET, or "/" and the end point returns a 200 response.
The response can be a listing of the bucket or folder contents, or lists all records if the end point includes a DSV.
However, if I use any of additional GET methods, a 403 Error is returned: SignatureDoesNotMatch.
There is another related discussion on this topic, and the solution for that is I presume publishing the API, then completing the Authorization header.
I understand that solution, but my question persists: Why are additional methods that are properly defined in the Swagger.yaml being ignored by the ION API Swagger interface ?
I should be able to append the target endpoint and authorize an awsSigv4 header using yaml references.
The target end point works, at least for GET. I can change it at will, and the default methods works.
if I append the end point, all fails.
This is not an issue of JSON vs YAML, either format is acceptable and the YAML structure is correct.
It appears that the Infor's ION API is ignoring documentation beyond the target end point.
