1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Well, there could be various reasons for this issue:
However, the main issue is that your connector is not able to fetch the connector offset topic __amazon_msk_connect_offsets_S3-Sink-Orders_ae585cdd-321c-4e70-8de0-a115ed0e127b-4-1 or your cluster doesn’t have that topic at all.
Make sure that you have given proper permissions(IAM role) to your connector to create this topic as per the below documentation:
[+] https://docs.aws.amazon.com/msk/latest/developerguide/msk-connect-service-execution-role.html
If the issue still persists, please reach out to us over a support case.
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa