<!-- 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?
{'filter': ['type1', 'type2']},
                {},
                False
            ),
            (
                'or string filter with no match',
                {'filter': ['type1', 'type2']},
                {'filter': {'Type': 'String', 'Value': 'type3'}},
                False
            ),
            (
                'or string filter no match with an array',
                {'filter': ['volleyball', 'basketball']},
                {'filter': {'Type': 'String.Array', 'Value': "['soccer', 'rugby', 'hockey']"}},
                False
            ),
            (
                'anything-but string filter with match',
                {'filter': [{'anything-but': 'type1'}]},
                {'filter': {'Type': 'String', 'Value': 'type1'}},
                False
            ),
            (
                'anything-but string filter with no match',
                {'filter': [{'anything-but': 'type1'}]},
                {'filter': {'Type': 'String', 'Value': 'type2'}},
                True
            ),
            (
                'prefix string filter with match',