1 Answer
- Newest
- Most votes
- Most comments
1
this could be due to missing permission to initialize change stream. More specifically this is for source mongodb 4.x onwards please refer to section which tells how to create a role with that permission and also how to assign the same to dms user. https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Source.MongoDB.html#:~:text=Permissions%20needed%20when%20using%20MongoDB%20as%20a%20source%20for%20AWS%20DMS
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hi team, Why is it a admin DB? Seems I never specified db before, how to modify the db name?
Encountered an error while initializing change stream: 'not authorized on admin to execute command {....$db: "admin".....' [1020401] (change_streams_capture.c:356)