<!-- Love localstack? Please consider supporting our collective:
👉  https://opencollective.com/localstack/donate -->

Under utils/common.py, 

TIMESTAMP_FORMAT_MILLIS = '%Y-%m-%dT%H:%M:%S.%fZ'

The %f produces time with microseconds, for example: 2020-03-18T19:43:18.115783Z.


However, when interacting the AWS s3 and sns apis, I receive DateTimes like this:

2020-03-02T22:32:13.240Z
i.e. milliseconds. 

This seems like a simple change to the utils. TIMESTAMP_FORMAT_MILLIS is named as if it should be millis as well. This is seems like a simple change. Is there a reason it should be microseconds?
try:
        socket.inet_aton(addr)
        return True
    except socket.error:
        return False
def is_zip_file(content):
    stream = BytesIO(content)
    return zipfile.is_zipfile(stream)
def unzip(path, target_dir, overwrite=True):
    if is_alpine():
        
        flags = '-o' if overwrite else ''
        return run('cd %s; unzip %s %s' % (target_dir, flags, path))
    try:
        zip_ref = zipfile.ZipFile(path, 'r')
    except Exception as e:
        LOG.warning('Unable to open zip file: %s: %s' % (path, e))
        raise e
    
    
    try:
        for file_entry in zip_ref.infolist():
            _unzip_file_entry(zip_ref, file_entry, target_dir)
    finally:
        zip_ref.close()
def _unzip_file_entry(zip_ref, file_entry, target_dir):