https://cerbos.dev logo
Join Slack
Powered by
We are trying to setup cerbos in Lambda. We were a...
# help
v
We are trying to setup cerbos in Lambda. We were able to set that up but unable to find documentation on how to invoke the APIs. If we try the normal way, <API-gateway-IP-endpoint>:3592/ it is failing to start Cerbos as per the cloudwatch logs. Any assistance or support on this would be really helpful.
a
Hey what is the error you are getting?
v
Hi Alex, Thanks for the quick support. Yes, I am using the above repo only.
Will share the error log here
d
There’s no need to specify a port number. Please use 
<API-gateway-IP-endpoint>
v
log-events-viewer-result.csv
log-events-viewer-result.csv
a
" 1674549904291,"cerbos: error: failed to create store: failed to read blob configuration: workDir unspecified and failed to determine user cache dir: neither $XDG_CACHE_HOME nor $HOME are defined This is the issue - the instance is never starting.
v
I will re-check the config set by our platform team and re-try deploying the service. Will reach out if I fail again.
I assumed that the above error was due to S3 permissions of sort.
In sam.yml I have set the stack name to a different string however while make publish-lambda it is picking up the default stack name ‘Cerbos’ itself.
I deleted the default Stack to redeploy everything clean but blocked here.
For now I manually changed the stack name to new name in sam.yml and retrying the same.
a
Did it work this time?
v
Yes it did get deployed successfully.
But when I try to invoke the Cerbos endpoint. It is returning internal server error.
log-events-viewer-result-2.csv
log-events-viewer-result-2.csv
a
Copy code
1674568349340,"cerbos: error: failed to create store: failed to read blob configuration: workDir unspecified and failed to determine user cache dir: neither $XDG_CACHE_HOME nor $HOME are defined
Something still isn’t right with the workDir so it isn’t starting up - what did you change earlier?
7 Views
Open in Slack
PreviousNext
Powered by