E

EmpCloud

conf 0.55

Thunder Marketing · 1Touch-dev

Infrastructure

20374 points from 6290 changes by 13 people

2026-07-02 → 2026-09-30 · showing up to 2026-09-30 · live data last updated 29 Sept, 05:07 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-07-02 can ever be recovered. An empty period means “not retained”, never “nothing happened”.

Weighted points

20374

6290 scoring changes

People

13

across 85 days

Concentration

36%

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 Mudunuru298 changes · 29 days · 0 commits

Ranking

Weighted by what each change did. infra-v1.

#PersonPointsChangesDaysMixServices
1Pankaj Kumar
7375
220555
Provisioning 707Deployment 237Access & security 370Configuration 89145 unscored
acm amplify cloudformation cloudfront +4
2Harsh Patel
6347
196037
Provisioning 537Deployment 213Access & security 390Configuration 82063 unscored
acm amplify autoscaling cloudformation +15
3Abhishek Kulkarni
2926
93441
Provisioning 189Deployment 132Access & security 227Configuration 386437 unscored
agreement-marketplace amplify apigateway apprunner +20
4Anshuman Parmar
886
28119
Provisioning 49Deployment 10Access & security 157Configuration 65142 unscored
agreement-marketplace amplify autoscaling cloudformation +9
5Ankur Kumar
843
24328
Provisioning 91Deployment 2Access & security 80Configuration 7028 unscored
amplify ec2 ec2-instance-connect iam +3
6Rushendra Varma Mudunuru
814
27529
Provisioning 32Access & security 168Configuration 7563 unscored
access-analyzer bedrock budgets cloudtrail +15
7Dhiraj Ambekar
671
18422
Provisioning 54Deployment 56Access & security 29Configuration 4536 unscored
amplify autoscaling cloudformation ec2 +6
8Aziz Bohra
327
13810
Provisioning 17Configuration 12135 unscored
q route53 ses sts
9Akash Kumar
102
366
Provisioning 5Deployment 6Access & security 3Configuration 2215 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
pankaj29none17
dhiraj26none25
Harsh_Patel19none15
Rushendra_Verma14none9
ankur@kyma.world12none8
Akash8none8
abhishek6none6
Jitu_Shah2none1
Aziz-Bohra1none71
Abhishek_K431311
Anshuman_P21518
Harsh-V17176
Rushendra_V131313
Aziz-B9919
Pankaj-S885
Dhiraj-A444
Ankur222

How a change is weighted

The whole formula.

Provisioning5 points × 1684

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

Deployment4 points × 659

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

Access & security3 points × 1424

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

Configuration2 points × 2523

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

Housekeeping0 points × 879

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.

ec2993
iam938
apigateway7
servicequotas7
s360
agreement-marketplace6
ecs57
autoscaling524
ec2-instance-connect48
ses48
cloudfront46
pricingplanmanager4