Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to use event put-bucket-notification-configuration #98

Closed
jackthecodemonkey opened this issue Jul 14, 2020 · 1 comment · May be fixed by #598
Closed

Unable to use event put-bucket-notification-configuration #98

jackthecodemonkey opened this issue Jul 14, 2020 · 1 comment · May be fixed by #598

Comments

@jackthecodemonkey
Copy link

Hi,
I tried to hook S3 up with SQS queue by running a command

awslocal --endpoint-url=http://localhost:8000 s3api put-bucket-notification-configuration --bucket local-bucket --notification-configuration file://lead.json --profile s3local --region us-east-1

and my lead.json

{
    "QueueConfigurations": [
        {
            "QueueArn": "arn:aws:sqs:us-east-1:000000000000:lead",
            "Events": [
                "s3:ObjectCreated:*"
            ]
        }
    ]
}

The error message I got

An error occurred (NotImplemented) when calling the PutBucketNotificationConfiguration operation: A parameter you provided implies functionality that is not implemented

If I replace http://localhost:8000 with a S3 server generated by localstack.
it works fine but I would like to use this plugin instead of localstack.

Any ideas or did I miss something?
Thanks!
@ar90n
Copy link
Owner

ar90n commented Jul 18, 2020

Hi @jackthecodemonkey
Thanks for your comment! Unfortunately, serverless-s3-local doesn't support integration with SQS. Because it seems that s3rver which is our backend system doesn't support it.

In my opinion, you can write a simple lambda function to relay the S3 event to SQS as a workaround. I'm truly sorry for not being able to help you.

@80avin-sw 80avin-sw mentioned this issue Sep 1, 2022
Closed
@80avin 80avin mentioned this issue Sep 1, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@ar90n @jackthecodemonkey