Tosha Ellison

Key notes from the discussion include:

• Reviewed PR from Abdullah with updates to the DynamoDB Test Case Documentation. This is an example of ongoing work the group can undertake to keep artifacts current.
• When submitting PRs reminder to include information about the reference or source of the update (e.g. new documentation, personal experience, etc.), e.g. 

• All documents should be converted to markdown as it's much easier to see/track changes. Spreadsheets might pose a problem so identifying additional tooling may be required.
• Confirmed that the group is open to additional input regarding the content, tools, frameworks to be developed by the group, including an open source tool to automate the tests.
• Reviewed the S3 control spreadsheet 
  
  • This spreadsheet provides the high level categories that are common across internal control frameworks and external regulatory requirements.
  • This is a filled in version to give an indicator of the type of content to be included.
  • The expectation is that a consumer (e.g. a bank) might insert a column to include internal references/naming conventions that would be for their firm's own internal use.
  • Called out example of "manual attestation", which is used where things can't yet necessarily be done in an automated way. This highlights opportunities to work with vendors to automate or to collectively build automation.
  • Reviewed a specific row of content in detail and agreed that the level of detail is appropriate.
  • Some discussion around the speed of linting services compared to running the tests. It is possible to optimize tooling to run the tests quickly. 
• Request for more participation and feedback with the aim of "assigning" entire services and completing them within a month. Goal is to also start on Microsoft and Google services as soon as feasible.