Following on from #3

Add support for creating the config rules, and maybe some form of alerting?

This would be disabled by default but could be enabled with a flag:

s3audit --enable-config-rules

e.g. creating public access config blocks. This would be disabled by default but could be enabled with a CLI flag, e.g.

s3audit --fix-public-access-block

I have 100+ buckets and default console format isn't very practical. It would be great to have table output where I could see colored icons in table cells - 100 buckets would probably fit on single screen.

I could try to make PR. I would probably take current CSV export as input because it should be closer to expected output than current console format.

Probably relevant to #5

There is mention in readme that we should use credentials from AWS Vault but there is no mention which permissions it actually requires - I would like to create IAM role with minimal permission scope.

Add a section to check for the existence of AWS managed Config rules related to S3:

https://docs.aws.amazon.com/config/latest/developerguide/managed-rules-by-aws-config.html#managed-rules-by-aws-config-storage

e..g YAML and JSON. This would allow other tooling to be built around the s3audit output.

Enabled via a flag, e.g.

s3audit --output=yaml

When triggering

s3audit --bucket=my-bucketname with the aws creds als environment variables set

(node:135) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'length' of undefined
at /usr/local/lib/node_modules/s3audit/lib/formatters/console.js:145:28
at processTicksAndRejections (internal/process/task_queues.js:93:5)
(node:135) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:135) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

node --version

v12.11.0

Installed via npm install ..

Not sure if I am using it wrong, if this is a version issu .. or somethnig else

Either with an enable-check flag to only do specific checks, or with a disable-check flag to be able to do all except specific checks. Both methods should be available to users.