Adding Secondary Indexes to Existing Amplify Tables Without Data Loss

Currently, I have a table structure without any secondary indexes. However, due to recent changes in my application requirements, I now need to add secondary indexes.

The issue is that when I attempt to add these indexes, the deployment process results in data loss. The tables are already in production and contain active user data, which cannot be deleted or recreated.

What is the recommended approach to introduce secondary indexes into existing Amplify-managed tables without causing data loss?