The easy part first: The sst Table construct is for a single DynamoDB table. If you have multiple DynamoDB tables, you'll need multiple SST Table constructs

The harder question: DynamoDB has a concept of single table design. Although controversial in some circles, it's largely considered a best practice when working with DynamoDB. The concept is that you use a single table to support a variety of access patterns in your application (e.g. fetch overdue invoices for user, fetch inventory by company, etc) by storing multiple entity types in the same table. The single table paradigm is meant to eliminate the expensive join operations of the RDBS solutions by storing your related data together in a single table.

The paradigm can be challenging to learn if you're coming from a RDBMS background, so it can have a steep learning curve. There are completely valid uses of multiple DyanmoDB tables, so it's not a "one size fits all" suggestion to use single table design. However, it's a widely adopted approach to successfully using DynamoDB and should probably be your default starting point

If you want to get on the fast track for what all this means, watch . Alex is the author of The DynamoDB Book, which is the best resource for learning DynamoDB if you want to go deeper.