Create example step function to be triggered by an hdf file in an s3 bucket and send to splunk.

TODO:

• Pass S3 contents to stepFunctions
• Verify the result of stateMachine Execution output
• Verify results in Splunk
• Configure command_string from stateMachineTrigger lambda to pass to saf-lambda
• Lambda input - Pass private command data in as env variables
• Update the stateMachineTrigger lambda function to process the correct file(s), in other words, investigate event.Records[0]. Test with multiple files in the bucket.
• Fix SAF Lambda trigger so it is only called once (instead of twice). Test with s3:ObjectCreated:Put.
• Add more role requirements for use by organizations (add path, and permission boundary).
• Add documentation for use of this
• Add updated diagram of the workflow
• Refer to the specific resources.Resources for IAM permissions and remove Resource: "*" from all statements (example snippet below)

Resource:
  Fn::Join:
    - ''
    - - 'arn:aws:s3:::'
      - Ref: ServerlessDeploymentBucket
      - '/*'

Enhancements:

• Find a way to add a trigger inside stepFunctions instead of Lambda (CloudWatch)
• Accept s3 bucket name as an environment variable or generate it if not specified. s3 bucket-name: ${opt:stage}-${self:service}-sample-name (sample-name could be generated blah string)
• Pass s3 object file contents to saf-lambda instead of s3 bucket name and file name.
• Consider Secrets Manager for Splunk credentials