What this measures
Work that leaves no trace in git.
Someone who spends a week keeping servers alive produces no commits and reads as idle everywhere else in this platform. CloudTrail is the only record that the work happened and who did it.
A CloudTrail write is not a unit of work, so events are weighted rather than counted. Signing in, changing your own password and opening a CloudShell terminal are all writes, and all score zero — presence is not delivery. Creating a load balancer and toggling a notification setting are both one row, and are not worth the same.
Only 90 days exist. No CloudTrail trail is configured on this account, so nothing before 2026-08-28 can ever be recovered. An empty period means “not retained”, never “nothing happened”.
Weighted points
10961
3328 scoring changes
People
13
across 29 days
Concentration
46%
held by Pankaj Kumar
Bus factor
3
people holding 80% of it
Invisible to every other measure
Infrastructure work in this period, and no commits at all.
This is the question the AWS ingest was built to answer. Without it each of these people reads as having delivered nothing.
Ranking
Weighted by what each change did. infra-v1.
| # | Person | Points | Changes | Days | Mix | Services |
|---|---|---|---|---|---|---|
| 1 | Pankaj Kumar | 5067 | 1513 | 19 | Provisioning 505Deployment 136Access & security 254Configuration 61817 unscored | amplify cloudformation cloudfront ec2 +2 |
| 2 | Harsh Patel | 3590 | 1035 | 17 | Provisioning 336Deployment 118Access & security 276Configuration 30543 unscored | acm amplify autoscaling cloudformation +13 |
| 3 | Rushendra Varma Mudunuru | 727 | 239 | 19 | Provisioning 32Access & security 153Configuration 5450 unscored | access-analyzer bedrock budgets cloudtrail +12 |
| 4 | Anshuman Parmar | 697 | 222 | 7 | Provisioning 32Deployment 3Access & security 151Configuration 3680 unscored | autoscaling cloudformation ec2 elasticbeanstalk +6 |
| 5 | Aziz Bohra | 327 | 138 | 9 | Provisioning 17Configuration 12123 unscored | q route53 ses sts |
| 6 | Ankur Kumar | 290 | 86 | 13 | Provisioning 25Deployment 2Access & security 39Configuration 2015 unscored | amplify ec2 iam route53 +1 |
| 7 | Abhishek Kulkarni | 69 | 19 | 5 | Provisioning 7Access & security 10Configuration 235 unscored | cloudformation ec2 iam s3 +1 |
| 8 | Akash Kumar | 65 | 26 | 4 | Provisioning 4Access & security 1Configuration 219 unscored | ec2 q route53 ses |
| 9 | Dhiraj Ambekar | 58 | 19 | 7 | Provisioning 2Deployment 6Access & security 2Configuration 913 unscored | amplify autoscaling cloudformation elasticbeanstalk +2 |
| 10 | Rushikesh Powar | 45 | 21 | 8 | Provisioning 1Configuration 204 unscored | ec2 route53 s3 |
| 11 | Jitu Prosad Saha | 26 | 10 | 2 | Provisioning 2Configuration 83 unscored | route53 ses |
| 12 | Pranav Ojha | 0 | 0 | 2 | 3 unscored | |
| 13 | MOHD NAVED | 0 | 0 | 1 | 3 unscored |
Access posture
Read off the sign-in events already ingested. Not part of any score.
This says nothing about how well anyone works and feeds no ranking. It is here because CloudTrail records whether a console sign-in used MFA, this platform already reads CloudTrail, and reporting infrastructure work while sitting on evidence that none of it is protected would be a strange kind of silence.
| AWS user | Sign-ins | With MFA | Failed | IPs |
|---|---|---|---|---|
| dhiraj | 3 | none | 3 | |
| Akash | 2 | none | 2 | |
| Harsh_Patel | 2 | none | 1 | |
| Rushendra_Verma | 2 | none | 2 | |
| pankaj | 1 | none | 1 | |
| Abhishek_K | 3 | 1 | 3 | 4 |
| Anshuman_P | 8 | 5 | 6 | |
| Harsh-V | 17 | 17 | 6 | |
| Rushendra_V | 13 | 13 | 13 | |
| Aziz-B | 8 | 8 | 1 | 8 |
| Pankaj-S | 8 | 8 | 5 | |
| Dhiraj-A | 4 | 4 | 4 | |
| Ankur | 2 | 2 | 2 |
How a change is weighted
The whole formula.
Brought infrastructure into existence or removed it — stacks, instances, load balancers, databases, apps.
Shipped a change to a running environment — builds, releases, environment rebuilds.
Changed who or what can reach something — security groups, IAM policies, keys, bucket policies.
Tuned infrastructure that already existed — attributes, scaling settings, DNS records.
Signing in, securing your own login, opening a shell. Presence, not delivery — scored at zero.
Where the work happened
AWS services touched, by change count.