Is there an existing issue for this?

• I have searched the existing issues

Feature description

As a User I NEED to be able to create objects in an s3 bucket with the system metadata(LastModified) I specify SO THAT I can properly test time related maintenance actions.

🧑‍💻 Implementation

I'm not familiar with the LocalStack code base yet, however as an idea it could be an environment toggle via S3_SYSTEM_META=1 and then when using the cli or sdk you can just include the LastModified data you want via their respective metadata options.

It may be that it is possible to use this with all system meta data, however for this ticket I'd suggest scoping to purely LastModified for simplicity.

Anything else?

I'm currently working on a maintenance feature to move a large number of files that are over the age six months from the working folder in an s3 bucket to archive folder where files are placed under, for example archive/2024-DEC, because above a certain number of objects sorting/searching doesn't work well in the UI(we have business users that sometimes need to access it).

Regardless of which technology(Lambda/Glue etc) I use for this the only way I test it is by creating S3 objects and then changing the time in my code for 5mins, 1 day so it's not really a proper test of the actual deployed code. I need to be careful because the first run will move(copy/delete) a LOT of files, subsequent daily runs will be a few. Yeah there's ways round it by splitting the code and keeping logs of original file dates and then writing more code to fix it if something goes wrong, but it would be really useful if we could change system meta data in LocalStack and just test it properly!