1 Answer
- Newest
- Most votes
- Most comments
0
Hi,
Yes, AWS service APIs can be used from any language if you use them at the REST layer.
You have then to properly structure and encode all parameters to match them,
The hard part is usually to get SigV4 right to sign those requests with valid AWS credentials. See https://docs.aws.amazon.com/AmazonS3/latest/API/sig-v4-authenticating-requests.html
To avoid this pain, this project may be useful to you: https://github.com/mattandneil/aws-sdk
It is a good starting point to get wroking Apex code and extend it to faceliveness API. The repo doesn't seem to specify license. So, I'd suggest to reach the authors.
Best,
Didier
Relevant content
- asked 3 years ago
AWS OFFICIALUpdated 2 years ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- How do I use an interface VPC endpoint to access an API Gateway private REST API in another account?AWS OFFICIALUpdated 6 months ago
I can manage to get AWS credential working fine. But as written earlier the CreateFaceLivenessSession rest api creates the session Id successfully, but StartLivenessSession always fails With a 200 HTTP code but with response body as
{ "Output": { "__type": "com.amazon.coral.service#UnknownOperationException", "message": null }, "Version": "1.0" }
This API has given this spec.
https://docs.aws.amazon.com/rekognition/latest/APIReference/API_rekognitionstreaming_StartFaceLivenessSession.html
But I am not sure why is AWS failing to recognize the service.
I think "StartFaceLivenessSession" cannot be called from REST api, apart from supported AWS sdk. Please confirm this once, if you have any strong evidence for this.