pinned lambda blocking on socket connection

I need to talk to a legacy system via TCP socket.
My thought was to create a pinned Greengrass Lambda in python3 that blocks on the client connection, does some handshaking with the client, then keeps the socket open as long as the Greengrass Core is running. The protocol to the legacy client as various back and forth messaging I will have to emulate.

I would use some of the data received from the socket to publish some MQTT messages but the trigger function would essentially be a stub and never be called. So the only data the lambda would receive would be from outside the AWS ecosystem.

Is this sane or will it light the atmosphere on fire?