The canvas now asks what a connection means, at the moment you draw it

Draw a line from a Lambda to a DynamoDB table and that one line can mean two very different pieces of infrastructure: an IAM policy that lets the function read and write the table, or a DynamoDB stream that triggers the function on every change. Until now you picked between them in the properties panel after connecting — easy to skip, and the default wasn't always the one you meant. Now the choice surfaces the moment you draw the edge: a small dialog asks which relationship you want, and the engine generates the right resources immediately. The template you export matches the diagram you drew, with no silent defaults in between. The same connect-time prompt covers every ambiguous pair on the canvas, not just Lambda-to-DynamoDB.

Try it: drop a Lambda and a DynamoDB table on the canvas and connect them.

Fixes & improvements

• •Properties panel widened so long resource names no longer truncate