Openscapes / Openscapes/openscapes.cloud

AWS Usage Report: Add human-annotated notes

Open
#35 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

usage-reporting
Dominant language
JavaScript
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Big picture idea/question: this automated report is awesome to have monthly. Could we also have place for human-annotated notes once someone has looked at this automated report? Could it be a separate page that is added to the end? We would have to think of the workflow. But somewhere to help the reader, with notes like this.

Annotation For June 2024:

  • The total cost of all AWS Services in June 2024 was $1289 - this is stable compared to previous months during the April-May Champions cohort
  • March was anonymously highest so far in 2024. This is due to large instances that are expensive to support the EMIT workshop hosted by LP DAAC
  • EC2 compute costs had a slight May increase for 2024-SBG Workshop (EMIT+ECOSTRESS)
  • EFS storage costs have reduced from active cleanup & teaching good practices.
  • AWS Backup have reduced since we have deleted unaccessed after 6mo
  • Champions home directories: one user has used the most. [action: we have reached out, or some explanation...]

Originally posted by @jules32 in https://github.com/NASA-Openscapes/2i2cAccessPolicies/pull/13#discussion_r1678264038

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file, test, or entry point is named. Start by locating the automated AWS usage report and reviewing how monthly reports are generated; define the annotation workflow and verify that a separate notes page can be added for readers with the supplied June 2024 example.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, javascript
Domain
cloud, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.