Fixed multiple full scan AWS buckets scanning deployment name conflict

[samthesecret]

TITLE

Change Summary

PR Checklist

• [ X] I've read and followed the Contributing Guide.
• Documents/Readmes
  • Updated accordingly
  • [ X] Not required
• Plugins that have versioning
  • Version bumped and follows Semantic Versioning
  • [ X] Not required

Other Notes

This is resolution against the bug #121

[trend-jack-c-tang]

• Max bucket name length is 63. With prefix included, step function name length will exceed the max length which is 80. Please consider not giving state machine name, and output the name and ARN in the stack outputs for customers to use.
• PR description needs to be completed: update title and change summary
• The branch has unresolved conflict that needs to be resolved
• Use conventional commit message for the commit: fix: Multiple full scan AWS buckets scanning deployment name conflict

[trend-jack-c-tang]

The issue related to this PR should be #120

[samthesecret]

Thanks for the correction on bug number, I missed attaching the correct one.

I have resolved the conflict.

Shall I make change to control the step function length ?

[trend-jack-c-tang]

Shall I make change to control the step function length ?

Yes, this should be addressed, or it won't work for longer bucket name. I'd suggest not giving default name for the step function. What do you think?

[samthesecret]

I have made changes to make sure the length of StateMachine function should be in limit.

[trend-jack-c-tang]

Why is it SSM but not SM? How about we just remove the acronym, since we already know that's a state machine/step function? By the way, would you please also use capital for the first char, like ScannerLoop?