docs: AWS Security Digest mention in the README

[michaelthomasletts]

All submissions

• Does your pull request title follow Conventional Commits (type(scope)!: summary)?
  • Allowed type values in this repository: feat, fix, perf, refactor, docs, style, test, build, ci, chore, revert.
  • Example pull request title: fix(cache): add a new parameter to Client.
  • For breaking changes in PR titles, use ! before : (example: feat!: remove deprecated cache API).
  • You can find additional details here.
  • Release Please uses these commit types to determine release bumps (feat -> minor, fix/perf -> patch, ! -> major).
  • You can skip releases by adding '[skip release]' into the PR title.
  • You can specify alpha and beta versions by adding something like Release-As: 0.1.0b1 in the footer of the PR body.
• Did you verify that your changes pass pre-commit checks before opening this pull request?
  • The pre-commit checks are identical to required status checks for pull requests in this repository. Know that suppressing pre-commit checks via the --no-verify | -nv arguments will not help you avoid the PR status checks!
  • To ensure that pre-commit checks work on your branch before running git commit, run pre-commit install and pre-commit install-hooks beforehand.
  • If needed, run the full suite locally with pre-commit run --all-files.
• Have you checked that your changes don't relate to other open pull requests?

Submission details

The following PR simply adds AWS Security Digest's mention of elhaz from issue 260 to the README.