Best strategy to archive specific records from RDS to a cheaper storage in AWS

I have the following requirements:

• For every deleted record in RDS we need to archive it into somewhere cheaper on AWS.
• Reduce storage cost
• Not using Glacier
• Context oriented (e.g. a file per table)
• re-import is not a requirement

I'm not an experienced user with AWS, so I'm still a bit lost among the amount of options it has to offer and I'd like to know if you have more ideas to help me clear it out.

Initial thoughts:

1. The microservice that deletes the record, might send it to a broker (RabbitMQ for e.g.) and another microservice (let's call it archiver) will listen to it, write into a file, zip and send to S3. This approach has some technical challenges though: in order to make sense create big files, I need to wait the queue to growth a bit, wrap it into a stream and zip inside S3. The transaction control is very weak as well, since file writing and ack on messages are signal based i.e. I'll remove the messages from the broker just after the file is created.
2. Add a new column to the "archiveble" tables as "deleted (bool)" and run a separate job fetching only those records and saving them into S3. Discarded they don't want the new microservice with access to other's databases.
3. Following the same approach as in the first item, but instead of save into S3, save into a cheaper database. SimpleDB?

option 1, but instead of rabbitmq, write it to a kinesis firehose and direct that to an s3 location - it doesn't get much cheaper or easier than that.