-
Notifications
You must be signed in to change notification settings - Fork 17
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.
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
S3 bucket.add_event_notification() does not deploy - No resource provider found for "Custom::S3BucketNotifications" #88
Comments
Hi! We just wanted to follow up to see whether your issue has been resolved. Were you able to get it working with the latest version of LocalStack? We would appreciate your feedback! |
Hello,
I upgraded to the latest version 2.3.2 and it still does not work.
Please find the updated log file attached.
Thanks,
Robert
…On Wed, Nov 15, 2023 at 8:22 AM Gábor Németh ***@***.***> wrote:
Hi! We just wanted to follow up to see whether your issue has been
resolved. Were you able to get it working with the latest version of
LocalStack? We would appreciate your feedback!
—
Reply to this email directly, view it on GitHub
<#88 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALIKGKINGC635NJ3MLIAHQLYES6YPAVCNFSM6AAAAAA5LVF25OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMJSGUZDSNJTGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Here is the log file |
Same issue here. Also posted about it here: localstack/localstack#9352 (comment) This is a blocker for us from using LocalStack |
Super important! Blocker from our side as well |
Hi! Please do not hesitate to contact us if you experience any other issues. |
Here's a hack to bypass the custom resource created by CDK. We can access the underlying L1 CDK construct, and from there set This example is in TypeScript. const bucket = new s3.Bucket(...);
const lambda = new NodejsFunction(...);
if (isDeployingToLocalStack()) { // implement or replace `isDeployingToLocalStack()` as required
const cfnBucket = bucket.node.defaultChild as s3.CfnBucket;
cfnBucket.notificationConfiguration = {
lambdaConfigurations: [
{
creationStack: [],
event: 's3:ObjectCreated:*',
function: lambda.functionArn,
},
],
};
} This works for newly created S3 and Lambda resources. I don't know what impact it'll have if you bypass the inline Python script added by CDK. (In the worst case scenario, you can add your own.) |
ENV
CDK-2.97.0
CDK-Python
Python 3.10.12
Problem
As the title suggests, calling add_event_notification() with any target results in the following error as seen towards the end of the log file:
localstack.log
If I set the notification through awslocal cli:
all my code works properly.
Code
The text was updated successfully, but these errors were encountered: