![]() To this thread then my 1st reply: For files that need to be tracked in this Until AWS stops penny-pinching and introduces listing byįile properties, here's another idea that I've used that is more relevant ![]() TheĬombination of leaving this basic feature out and billing for file listings I agree this sort of functionality would be very helpful in aws-cli. On Tue, at 10:00 AM, Josh Wieder You're right, sorry for my lame reply and ![]() Anyway, hope this helps and apologies again for my earlier derpy reply. depending on your application / system architecture that might make this sort of approach unfeasible. You'll need to change the condition on this loop, but hopefully this can give you an idea.ĭoing things this way relieves you of any charges related to listing the files in your bucket but it also depends on the client you are conducting the search on having access to the local file list. Where $FILE is your local filename index and $TODAY is the date you are searching for. Searching for a date then involves opening the file, looking for filenames that match the today's date could look something like this:Īws s3 sync $BUCKETURL /some/local/directory -exclude "*" -include "$fileName" A list of files is stored in a local text file (or could be db if you have gazillions of files to worry about). Until AWS stops penny-pinching and introduces listing by file properties, here's another idea that I've used that is more relevant to this thread then my 1st reply: For files that need to be tracked in this way, files are named with a timestamp. The combination of leaving this basic feature out and billing for file listings is highly suspect. You're right, sorry for my lame reply and I agree this sort of functionality would be very helpful in aws-cli.
0 Comments
Leave a Reply. |