Kinesis errors with AWS SDK 1.X instrumentator

I am not sure if it is better with 2.X but I can confirm that it is not working out of the box, that's caused by Kinesis doing calls to DynamoDB in the worker threads before the application has access to the worker thread to create a segment so the context missing error appears.
I was able to work around it with the help of this SO thread: https://stackoverflow.com/questions/49280253/how-can-use-the-java-kinesis-client-library-together-with-x-ray
But I was expecting out of the box support or in the worse case no support, but this situation of not using the instrumentator for the other services to avoid this error is really weird.
I don't have traces at hand to share but should be easy to replicate. If needed I can try to provide you with some.

Inizia riproducendo il comportamento dei worker thread di AWS SDK 1.X Kinesis descritto nell’issue, usando come contesto il thread di Stack Overflow collegato. Traccia le chiamate DynamoDB effettuate prima che il worker thread abbia accesso al segmento e verifica che l’instrumentator non produca più errori context-missing, mentre la strumentazione degli altri servizi rimane abilitata.

Scritto dal modello di indicizzazione a partire dal testo della issue.