Error while populating event database about eventbridge-canon HOT 4 OPEN

Thanks @lorcanoeire for your help. The issue was eventually related to the credentials method. I tried to use the SSO login option, which is working well for most cases of AWS CLI, and it didn't work in this case. Once I've updated the temporary credentials in the ~/.aws/credentials file it worked. Thanks again for this great tool and support.

from eventbridge-canon.

@guyernest I encountered this exact stack trace and problem using SCHEMA_REGISTRY_NAME=discovered-schemas on a newly created eventbus.

My problem?

I had forgotten to enable schema discovery for my new eventbus! Once enabled I ensured I fired events at the same eventbus to the point that at least one event schema was discovered.

HTH,

Lorcan

from eventbridge-canon.

Hey @guyernest @lorcanoeire

Sorry for the late response, this issue managed to go through the net!

Sounds like you managed to fix the issue 🙏, yeah I need to update the docs and method to focus on moving away from ENV variables, so I will make a note of that!

If you have any ideas, or feedback for canon feel free to share!

Hope you enjoy the tool

Cheers,
Dave!

from eventbridge-canon.

It's also probably worth mentioning that I opted not to specify any credentials in the .env file in favour of using an AWS profile (I just happen to be using aws-vault but I'm sure a basic profile would also work).

$ aws-vault exec my-profile-name -- npm run populate

My .env file:

EVENT_BUS_NAME=my-eventbus-name
SCHEMA_REGISTRY_NAME=discovered-schemas
REGION="us-east-1"

AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_SESSION_TOKEN=

from eventbridge-canon.