Update the CloudFormation template with the rest of the resources

[Nr18]

• Added some deployment documentation to the README
• Added a .gitignore so that only the actual code get's committed
• Added resources to the CloudFormation template and replaced the environment references with the actual resource references
• Added the account id in the path of the processor.py

[Nr18]

Noticed that the creation of the Athena table still resulted in a failure fixed it by applying the correct paths

[concurrencylabs]

Thanks for all the improvements, just to let you know we're still reviewing. We need to make sure our running processes continue to work. For example, the setting of environment variables and paths.

[concurrencylabs]

FYI... haven't forgotten about this PR. We're trying to make it work with existing stacks in both cross-account and single account scenarios and it's taking some time to set it up and test it. Will soon come back with a commit.

[concurrencylabs]

I had to make a number of changes to this PR, in order to make it work with the way the tool it's currently used, especially in cross-account scenarios. They should be compatible with the way you're using it, except you need to make sure S3 prefixes that are passed as parameters in the SAM template end in a "/". More details here:

• For consistency with how this tool is already used (for example, in cross-account processing), we need S3 prefixes to end in "/". Updated relevant parts of the code to reflect this.
• Due to known limitations in SAM, where conditions are not recognized, I had to split the SAM templates, so now there is a separate one for executions triggered by an S3 event (curprocessor-sam.yml), and another one for cross-account executions (curprocessor-xacct-sam.yml). There is a bit of duplication as a result of having two SAM templates, but otherwise there are many issues in trying to make both scenarios work in the same template.
• Updated README file, to reflect some of the changes.
• Added an extra validation to the S3 starter function, since AWS places two different Manifest.json files each time there is a new Cost and Usage report. This would result in two Step Function executions, unnecessarily, without the added validation.

Thanks for all the improvements!

[Nr18]

You're welcome