AWS_XRAY_CONTEXT_MISSING and AWS_XRAY_DAEMON_ADDRESS is set about dynamo-types

[breath103]

First, That's not an "Error". that's just a log from aws-xray-sdk of informing xray configurations.
Second, what kind of environment are you in on AWS? is it ec2 or lambda or..

[thakursunakshi]

lambda
due to this, I am unable to save data in dynamodb

[breath103]

Well in short, this doesn't have any effect other than showing that log, so you can ignore it.
As of xray usage, unless you set the environment variable dynamo-typeorm doesn't use xray (code)
but xray-sdk itself has sort of bug that if you just "require" that package even without actually using it, it still print out that log. currently, i have no plan for fixing it since it's really xray-sdk problem

[breath103]

closing because of lack of response