-
Type:
Improvement
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 9.10-HF14, 10.2
-
Component/s: Nuxeo Vision
-
Backlog priority:600
-
Sprint:nxAI Sprint 10.3.6, nxAI Sprint 10.3.7
-
Story Points:2
On 9.10-HF20 nuxeo-vision access some configuration keys:
org.nuxeo.vision.aws.region= org.nuxeo.vision.aws.key= org.nuxeo.vision.aws.secret=
When deploying Nuxeo on AWS and using AIM roles/Policies, we do not provide secret/key, but then the plugin fails because it does not use the environment variables automatically set up by AWS on the EC2 instance.
There should be a fallback in the code: If these configuration keys are empty, then, get the environment variables. I believe it is in the AmazonRekognitionProvider#getClient part of the code, here
On 10.3 the standard Nuxeo AWS service configuration keys are now used:
nuxeo.aws.region= nuxeo.aws.accessKeyId= nuxeo.aws.secretKey=
- is related to
-
NXP-26307 Allow AWS Rekognition configuration keys in nuxeo.conf
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
