How to implement GDPR Right to erasure with AWS Timestream

In an application that collects data from IoT devices from multiple customer in a single AWS Timestream table, what if a customer leaves and requests all of its data to be deleted, according to GDPR's right to erasure?

Timestream doesn't support deleting records, only updating them.

Possible solutions we came up so far:

• update all records of the customer with zero values
• use table per customer and then delete the whole table (problematic with large number of customers)
• don't actually delete the data, but make it not relatable to the customer anymore (probably not GDPR compliant anyway)

Are there any other options here? Or is there no solution and we have to dump Timestream altogether and use a different product that supports deletes?

One other alternative is to use data retention to delete the data in Timestream after a period of time you define.

GDPR mentions that you need to delete the data after 1 month (it seems you can have 2 more month but then you need to inform the user that data deletion would take longer).

Keeping data in Timestream can become expensive. I usually store the data in Timestream (short retention) and S3. I use Timestream for fast analytics or near real time dashboarding. I use S3 for adhoc query, ML or historical dashboarding.