I have only found one answer that suggested tagging the tables. Since I am picking up an existing system and not building from scratch this would be labor intensive.
I have scoured AWS for a week and found no tangible steps for creating/maintaining UAT for DynamoDB.
The Java, local Dynamo does not persist data.
I would be grateful for any information regarding establishing a sustainable UAT environment for DynamoDB.
At my current employer we create a separate AWS environment for UAT. The separate environment is done by having another AWS account. This account can be used for UAT. So in our code, if the keys are for the UAT account then it would access the UAT DynamoDB databases. If the keys are for production, or development, then it would access the production or development DynamoDB databases.
This has some pros and cons. One con is that you have to manage multiple AWS accounts. But that's also a pro on that you can easily assess your AWS costs per account.
One pro is that you can keep your table names intact across environments. You do not need a "myTableNameUat" and "myTableNameDev"... its just "myTableName", and the keys which are passed to your application at deployment will determine which environment is used.