You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've confirmed SES can write to S3, but when adding the Lambda to SES Ruleset I'll get errors like the following:
Error getting object incoming/8h2b7kv5td0h3nv9ndukoov1cm2edri16p6dvo81 from bucket pb30-lists-msp2. Make sure they exist and your bucket is in the same region as this function.
An error occurred (AccessDenied) when calling the GetObject operation: Access Denied: ClientError
Traceback (most recent call last):
File "/var/task/lambda.py", line 13, in lambda_handler
with email_message_for_event(event) as msg:
File "/usr/lib64/python2.7/contextlib.py", line 17, in __enter__
return self.gen.next()
File "/var/task/sestools.py", line 24, in email_message_for_event
raise e
ClientError: An error occurred (AccessDenied) when calling the GetObject operation: Access Denied
An error occurred (NoSuchLifecycleConfiguration) when calling the GetBucketLifecycleConfiguration operation: The lifecycle configuration does not exist: ClientError
Traceback (most recent call last):
File "/var/task/lambda.py", line 34, in lambda_handler
l.send(msg)
File "/var/task/listobj.py", line 317, in send
self.moderate(msg)
File "/var/task/listobj.py", line 401, in moderate
lifecycle = s3.get_bucket_lifecycle_configuration(Bucket=config.s3_bucket)
File "/var/runtime/botocore/client.py", line 312, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/var/runtime/botocore/client.py", line 601, in _make_api_call
raise error_class(parsed_response, operation_name)
ClientError: An error occurred (NoSuchLifecycleConfiguration) when calling the GetBucketLifecycleConfiguration operation: The lifecycle configuration does not exist
I've confirmed SES can write to S3, but when adding the Lambda to SES Ruleset I'll get errors like the following:
S3 Bucket Policy is adapted from link in #29:
The text was updated successfully, but these errors were encountered: