Consistently getting an error message on ProcessCloudTrailFunction

Issue #3 new
Captain Crabby created an issue

error.png

It appears that an incorrect bucket name is being used for the S3 trigger for CloudTrail files. I've deleted and re-created the stack several times now. All looks well in the CloudFormation console, but I see this error when viewing the function in the Lambda console.

Comments (5)

  1. Captain Crabby reporter

    I can see why the Aussies ignored me. Despite this error, everything appears to work as designed. Moral of the story, don't look at the Lambda console.

  2. danb

    @CaptainCrabby sorry! I got incredibly sick after shmoocon but I'm alive now. I have literally no idea where this error comes from, we get it too but everything works?

    I'll try and investigate more in the future but since it works it won't be high priority.

  3. Log in to comment