LogPipelinelogBucketNotifications183A08DA: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation: Unable to validate the following destination configurations

[SeagullTian]

Describe the bug

Face following error during the deployment:

Received response status [FAILED] from custom resource. Message returned: Error: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation: Unable to validate the following destination configurations

Logical ID: LogPipelinelogBucketNotifications183A08DA

May I ask if there's any insight how to solve this problem?

Thanks in advance.

Expected Behavior

Make this deployment work

Current Behavior

Deployment Failure with error:

Received response status [FAILED] from custom resource. Message returned: Error: An error occurred (InvalidArgument) when calling the PutBucketNotificationConfiguration operation: Unable to validate the following destination configurations

Reproduction Steps

Use the Template for China Region and it will face the error

Possible Solution

No response

Additional Information/Context

No response

Log Hub Version

N/A

AWS Region. e.g., us-east-1

cn-north-1

Other information

No response

[YikaiHu]

Hi @SeagullTian , could you please check the region of your log source bucket? It should be the same as your Log Hub deploy region (cn-north-1).
This error log seems like caused by the failure of S3 notification creation.

[SeagullTian]

Thanks Kervin for checking. I can confirm that the source bucket is in the same region

[YikaiHu]

Hi @SeagullTian , what's the type of the Log in this pipeline?
And can you provide the earliest error message in CloudFormation Stack's event?

[SeagullTian]

WAF Log, I'm not sure if this is what you ask for.

as you can see, the error I shared is the earliest one.

i also tried to check the CloudWatch log but it seems useless:

[YikaiHu]

Hi @SeagullTian , sorry for the late reply.

According to our experiments, we found that this is an open issue related to AWS S3 notification. We will continue to follow the progress of this root issue aws/aws-cdk#18090.

The workaround is delete this WAF Log Pipeline in Log Hub console and recreated one.

[SeagullTian]

May i ask if there's an ETA for the fix? Even I tried to create the S3Notification manually in Management Console does NOT help.

Currently, I'm not able to use LogHub console to recreate a pipeline. Please let me know if there's any other way we can do this.

[owenCCY]

Hi @SeagullTian, thanks for your info and we have added this issue in our backlog. For now, this issue can not be fixed and we are also waiting for CDK team's update. Sorry for the inconvenience, I will end this thread for now.

[wchaws]

Root cause: aws/aws-cdk#18090 (comment)

[JoeShi]

We changed to EventBridge in v2.3, no longer exists