E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Infrastructure

19686 points from 6099 changes by 13 people

2026-06-28 → 2026-09-26 · showing up to 2026-09-26 · live data last updated 26 Sept, 08:33 UTC

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-06-29 can ever be recovered. An empty period means “not retained”, never “nothing happened”.

Weighted points

19686

6099 scoring changes

People

13

across 85 days

Concentration

38%

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.

Rushendra Varma Mudunuru289 changes · 27 days · 0 commits

Ranking

Weighted by what each change did. infra-v1.

#PersonPointsChangesDaysMixServices
1Pankaj Kumar
7391
221354
Provisioning 705Deployment 237Access & security 376Configuration 89547 unscored
acm amplify cloudformation cloudfront +4
2Harsh Patel
5742
179438
Provisioning 474Deployment 210Access & security 312Configuration 79862 unscored
acm amplify autoscaling cloudformation +15
3Abhishek Kulkarni
2952
94244
Provisioning 191Deployment 133Access & security 229Configuration 389440 unscored
agreement-marketplace amplify apigateway apprunner +21
4Ankur Kumar
825
23726
Provisioning 91Deployment 2Access & security 74Configuration 7026 unscored
amplify ec2 ec2-instance-connect iam +3
5Anshuman Parmar
801
25317
Provisioning 42Deployment 6Access & security 157Configuration 48144 unscored
agreement-marketplace amplify autoscaling cloudformation +8
6Rushendra Varma Mudunuru
790
26727
Provisioning 32Access & security 160Configuration 7562 unscored
access-analyzer bedrock budgets cloudtrail +15
7Dhiraj Ambekar
671
18422
Provisioning 54Deployment 56Access & security 29Configuration 4537 unscored
amplify autoscaling cloudformation ec2 +6
8Aziz Bohra
327
13810
Provisioning 17Configuration 12133 unscored
q route53 ses sts
9Akash Kumar
104
377
Provisioning 5Deployment 6Access & security 3Configuration 2317 unscored
amplify ec2 q route53 +1
10Rushikesh Powar
45
218
Provisioning 1Configuration 204 unscored
ec2 route53 s3
11Jitu Prosad Saha
38
133
Provisioning 2Deployment 3Configuration 85 unscored
amplify route53 ses
12Pranav Ojha
0
02
3 unscored
13MOHD NAVED
0
01
3 unscored

Access posture

Read off the sign-in events already ingested. Not part of any score.

9 without MFA

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 userSign-insWith MFAFailedIPs
pankaj31none19
dhiraj27none26
Harsh_Patel20none16
Rushendra_Verma14none9
ankur@kyma.world12none8
Akash10none10
abhishek6none6
Jitu_Shah2none1
Aziz-Bohra1none71
Abhishek_K461313
Anshuman_P22519
Harsh-V16166
Rushendra_V131313
Aziz-B8818
Pankaj-S885
Dhiraj-A444
Ankur111

How a change is weighted

The whole formula.

Provisioning5 points × 1614

Brought infrastructure into existence or removed it — stacks, instances, load balancers, databases, apps.

Deployment4 points × 653

Shipped a change to a running environment — builds, releases, environment rebuilds.

Access & security3 points × 1340

Changed who or what can reach something — security groups, IAM policies, keys, bucket policies.

Configuration2 points × 2492

Tuned infrastructure that already existed — attributes, scaling settings, DNS records.

Housekeeping0 points × 883

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.

iam929
ec2898
logs8
apigateway7
servicequotas7
s360
agreement-marketplace6
ecs57
autoscaling507
cloudfront49
ses48
ec2-instance-connect48