Demand for unregistered services

The evidence behind DevCloud’s coverage target. Sampled 2026-09-05; re-derive with python3 scripts/demand_rank.py.

What this measures

DevCloud has no usage telemetry, so this page does not measure what its users ask for. It measures revealed demand: how many of three independent projects have already built each AWS service DevCloud does not register. Each serves a population DevCloud names as its own, and each only adds a service when somebody asks.

SourceWhat it isServicesUnmatched names
motoPython AWS mocking library — boto3 developers running tests1630
LocalStackLocal AWS emulator; community + pro1194
terraform-provider-awsOne Go package per service — the IaC population2734

Read a high support count as this service is worth emulating to someone, not as our users want this. The live measurement of DevCloud’s own traffic is GET /devcloud/api/unrouted, which accrues behind this page; its ceiling is in coverage.md.

“Unmatched names” is the join diagnostic: a name a source publishes that matches neither the missing set nor a registered service. A large number there would mean name normalisation is dropping matches and the support counts are too low.

Readings

ReadingValue
Upstream model files431
Registered when sampled148
R1 — missing set M283
R2 — M with support 38
R2 — M with support 249
R2 — M with support 1111
R2 — M with support 0115
R2 — M with support ≥ 257 (20.1% of M)

Full ranking

Ordered by support count, then name — the order the work was done in, so stopping at any point would have stopped on the best surface available.

All 57 services with support ≥ 2 are registered, down to and including workspaces-web; TestDemandSetIsRegistered fails if any of them stops being. 56 serve at least one operation, and the one that does not (rds-data) is named with its reason in coverage.md. Everything below them — support 1 and support 0 — is the 226 services that carry no depth commitment. They are registered and engine-served, so a call to one is answered locally rather than billed; what this study declined to promise is that it is answered faithfully. See the two axes.

ServicemotoLocalStackterraform-provider-awsSupport
api-gatewayyesyesyes3
elastic-load-balancingyesyesyes3
emr-serverlessyesyesyes3
mediastoreyesyesyes3
rds-datayesyesyes3
redshift-datayesyesyes3
s3-controlyesyesyes3
timestream-queryyesyesyes3
ampyes—yes2
apigatewaymanagementapiyesyes—2
app-meshyes—yes2
budgetsyes—yes2
cleanroomsyes—yes2
cloudhsm-v2yes—yes2
codestar-connections—yesyes2
connectyes—yes2
data-pipelineyes—yes2
databrewyes—yes2
datasyncyes—yes2
daxyes—yes2
devops-agentyes—yes2
direct-connectyes—yes2
directory-serviceyes—yes2
dsqlyes—yes2
emr-containersyes—yes2
fsxyes—yes2
greengrassyes—yes2
guarddutyyes—yes2
inspector2yes—yes2
ivsyes—yes2
kinesis-analytics—yesyes2
kinesis-videoyes—yes2
macie2yes—yes2
mediaconnectyes—yes2
medialiveyes—yes2
mediapackageyes—yes2
mediapackagev2yes—yes2
mediastore-datayesyes—2
network-firewallyes—yes2
networkmanageryes—yes2
opensearchserverlessyes—yes2
osisyes—yes2
payment-cryptographyyes—yes2
quicksightyes—yes2
resiliencehubyes—yes2
route-53-domainsyes—yes2
s3vectorsyes—yes2
securityhubyes—yes2
service-catalogyes—yes2
service-catalog-appregistryyes—yes2
service-quotasyes—yes2
signeryes—yes2
syntheticsyes—yes2
timestream-influxdbyes—yes2
vpc-latticeyes—yes2
workspacesyes—yes2
workspaces-webyes—yes2
accessanalyzer——yes1
account-access——yes1
agent-registry——yes1
appconfigdata—yes—1
appfabric——yes1
appflow——yes1
appintegrations——yes1
application-insights——yes1
application-signals——yes1
apprunner——yes1
appstream——yes1
arc-region-switch——yes1
arc-zonal-shift——yes1
auditmanager——yes1
auto-scaling-plans——yes1
bcm-data-exports——yes1
billing——yes1
chatbot——yes1
chime——yes1
chime-sdk-media-pipelines——yes1
chime-sdk-voice——yes1
cloud9——yes1
clouddirectoryyes——1
cloudfront-keyvaluestore——yes1
codecatalyst——yes1
codestar-notifications——yes1
compute-optimizer——yes1
connectcampaignsyes——1
connectcases——yes1
controltower——yes1
cost-and-usage-report-service——yes1
cost-optimization-hub——yes1
customer-profiles——yes1
dataexchange——yes1
datazone——yes1
detective——yes1
device-farm——yes1
directory-service-data——yes1
dlm——yes1
docdb-elastic——yes1
drs——yes1
ec2-instance-connectyes——1
ecr-public——yes1
evs——yes1
finspace——yes1
fms——yes1
gamelift——yes1
global-accelerator——yes1
grafana——yes1
groundstation——yes1
imagebuilder——yes1
inspector——yes1
interconnect——yes1
internetmonitor——yes1
invoicing——yes1
ivschat——yes1
kafkaconnect——yes1
keyspaces——yes1
kinesis-video-archived-mediayes——1
lambda-core——yes1
lambda-microvms——yes1
launch-wizard——yes1
license-manager——yes1
lightsail——yes1
location——yes1
m2——yes1
mailmanager——yes1
marketplace-meteringyes——1
mediapackage-vod——yes1
mgn——yes1
mpa——yes1
mwaa-serverless——yes1
neptune-graph——yes1
networkflowmonitor——yes1
networkmonitor——yes1
notifications——yes1
notificationscontacts——yes1
oam——yes1
observabilityadmin——yes1
odb——yes1
outposts——yes1
pca-connector-ad——yes1
pcs——yes1
pinpoint-sms-voice-v2——yes1
pricing——yes1
rbin——yes1
redshift-serverless——yes1
resiliencehubv2——yes1
resource-explorer-2——yes1
rolesanywhere——yes1
route53-recovery-control-config——yes1
route53-recovery-readiness——yes1
route53profiles——yes1
rum——yes1
s3files——yes1
s3outposts——yes1
savingsplans——yes1
schemas——yes1
securitylake——yes1
simpledbv2yes——1
ssm-contacts——yes1
ssm-incidents——yes1
ssm-quicksetup——yes1
ssm-sap——yes1
sso——yes1
storage-gateway——yes1
taxsettings——yes1
uxc——yes1
waf-regional——yes1
wellarchitected——yes1
workmail——yes1
agent-registry-control———0
aiops———0
amplifybackend———0
amplifyuibuilder———0
application-discovery-service———0
applicationcostprofiler———0
artifact———0
b2bi———0
backup-gateway———0
backupsearch———0
bcm-dashboards———0
bcm-pricing-calculator———0
bcm-recommended-actions———0
billingconductor———0
braket———0
chime-sdk-identity———0
chime-sdk-meetings———0
chime-sdk-messaging———0
cleanroomsml———0
cloudhsm———0
cloudsearch-domain———0
cloudtrail-data———0
cloudwatch-events———0
cognito-sync———0
compute-optimizer-automation———0
connect-contact-lens———0
connectcampaignsv2———0
connecthealth———0
connectparticipant———0
controlcatalog———0
deadline———0
eks-auth———0
elementalinference———0
finspace-data———0
freetier———0
gameliftstreams———0
geo-maps———0
geo-places———0
geo-routes———0
greengrassv2———0
health———0
iam-toolbox———0
inspector-scan———0
iot-jobs-data-plane———0
iot-managed-integrations———0
iotdeviceadvisor———0
iotfleetwise———0
iotsecuretunneling———0
iotsitewise———0
iotthingsgraph———0
iottwinmaker———0
ivs-realtime———0
keyspacesstreams———0
kinesis-video-media———0
kinesis-video-signaling———0
kinesis-video-webrtc-storage———0
license-manager-linux-subscriptions———0
license-manager-user-subscriptions———0
machine-learning———0
managedblockchain-query———0
marketplace-agreement———0
marketplace-catalog———0
marketplace-commerce-analytics———0
marketplace-deployment———0
marketplace-discovery———0
marketplace-entitlement-service———0
marketplace-reporting———0
mediatailor———0
medical-imaging———0
migration-hub———0
migration-hub-refactor-spaces———0
migrationhub-config———0
migrationhuborchestrator———0
migrationhubstrategy———0
mturk———0
neptunedata———0
nova-act———0
partnercentral-account———0
partnercentral-benefits———0
partnercentral-channel———0
partnercentral-revenue-measurement———0
partnercentral-selling———0
payment-cryptography-data———0
pca-connector-scep———0
pi———0
pinpoint-email———0
pinpoint-sms-voice———0
pricing-plan-manager———0
proton———0
qconnect———0
repostspace———0
route53-recovery-cluster———0
route53globalresolver———0
rtbfabric———0
security-ir———0
securityagent———0
signer-data———0
signin———0
snow-device-management———0
snowball———0
socialmessaging———0
ssm-guiconnect———0
sso-oidc———0
supplychain———0
support-app———0
supportauthz———0
sustainability———0
tnb———0
trustedadvisor———0
wickr———0
wisdom———0
workdocs———0
workmailmessageflow———0
workspaces-instances———0
workspaces-thin-client———0