Store result to database(such as DDB) to support report versioning

[ensean]

Pick a category

• [] New Checks/Rules
• [] New Services coverage
• [] UI improvement
• New Features (e.g: new parameter, new filter, new page)
• [] Others...

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like

• Stores the result to database(maybe DDB)
• Create a S3 bucket to host the static files, such as html/css/js
• Security staff can view/check the report by date/version and view the difference between versions.

Describe alternatives you've considered
NA

Additional context
NA

[kuettai]

There is a pipeline for the DDB + versioning. Estimate guide will be available at early Q4 Y2024.

For S3 to host static file, we are not keen to recommend that as the report might consists sensitive information. Customer may refers to the AWS Official Guide on S3 Hosting instead: https://docs.aws.amazon.com/AmazonS3/latest/userguide/WebsiteHosting.html

Thank you for all these feedback, keep it coming.

[emillg]

@kuettai Any news on the database support? We are interested in seeing the trend of findings as graphs (without details).

[jainlokesh2]

Hi @kuettai Please let us know when it will be available?

[kuettai]

Can you check if this can helps you? https://github.com/aws-samples/service-screener-v2/tree/main/usecases/scheduler

Else need to run with --mode api-raw to generate and build your own :)

[kuettai]

Sorry missing out the link earlier: https://github.com/aws-samples/service-screener-v2/tree/main/usecases/scheduler