<!-- Love localstack? Please consider supporting our collective:
👉  https://opencollective.com/localstack/donate -->
We have been trying to setup s3 and sqs on local stack. What we are trying to do is any object uploaded to s3 sqs queue needs to be notified. Find below bunch commands used. 

```
aws --endpoint-url=http://localhost:4572 s3 mb s3://march
aws --endpoint-url=http://localhost:4576 sqs create-queue --queue-name march
aws --endpoint-url=http://localhost:4572 s3api put-bucket-notification-configuration --bucket march --notification-configuration file://notification.json
aws --endpoint-url=http://localhost:4572 s3 cp test.csv s3://march
aws --endpoint-url=http://localhost:4576 sqs receive-message --queue-url http://localhost:4576/queue/march
```
notification.json content
```
{
  "QueueConfigurations": [
    {
      "QueueArn": "http://localstack:4576/queue/march",
        "Events": [
          "s3:ObjectCreated:*"
        ]
    }
  ]
}
```

Is there anything missing in my above steps? Is this a know issue?
"""
        Return the Java classpath, using the parent folder of the
        given archive as the base folder.
        The result contains any *.jar files in the base folder, as
        well as any JAR files in the "lib/*" subfolder living
        alongside the supplied java archive (.jar or .zip).
        :param archive: an absolute path to a .jar or .zip Java archive
        :return: the Java classpath, relative to the base dir of "archive"
        """
        entries = ['.']
        base_dir = os.path.dirname(archive)
        for pattern in ['%s/*.jar', '%s/lib/*.jar']:
            for entry in glob.glob(pattern % base_dir):
                entries.append(os.path.relpath(entry, base_dir))
        result = ':'.join(entries)
        return result
EXECUTOR_LOCAL = LambdaExecutorLocal()
EXECUTOR_CONTAINERS_SEPARATE = LambdaExecutorSeparateContainers()
EXECUTOR_CONTAINERS_REUSE = LambdaExecutorReuseContainers()
DEFAULT_EXECUTOR = EXECUTOR_LOCAL
AVAILABLE_EXECUTORS = {
    'local': EXECUTOR_LOCAL,
    'docker': EXECUTOR_CONTAINERS_SEPARATE,
    'docker-reuse': EXECUTOR_CONTAINERS_REUSE
}