Skip to content

Technology

AWS Step Functions

Last fetched

AWS Step Functions is a technology in WhisperGraph's PredictLeads-derived TECHNOLOGY corpus, categorized under frameworks and libraries, with a published adopter count of 6,418 hostnames.

Profile

Broader grouping
programming
Published adopter count
6,418

AWS Step Functions is a serverless function orchestrator that makes it easy to sequence AWS Lambda functions and multiple AWS services into business-critical applications. Through its visual interface, users can create and run a series of checkpointed and event-driven workflows that maintain the application state. This technology allows users to build visual workflows that enable fast translation of business requirements into technical requirements. Applications can be built in a matter of minutes, and when needs change, users can swap or reorganize components without customizing any code.

Vendor site: https://aws.amazon.com/step-functions/

Sample adopters

20 hostnames WhisperGraph observed running AWS Step Functions, a sample of the 6,418 published adopters.

Hosting concentration

The networks announcing the IP addresses of a sample of 20 AWS Step Functions adopters, not of all 6,418 published adopters. A hostname counts once per network.

Related pages

Pivot from AWS Step Functions into its category and the vendor behind it.

Queries

Resolves the slug's technology-name candidate(s) and projects the winner's fields.


MATCH (t:TECHNOLOGY)
WHERE t.name =~ $pattern
WITH t ORDER BY t.adopterCount DESC, t.name ASC
WITH collect(t)[0] AS winner, count(t) AS candidates
RETURN winner.name AS name,
       winner.description AS description,
       winner.category AS category,
       winner.parentCategories AS parentCategories,
       winner.adopterCount AS adopterCount,
       winner.url AS url,
       winner.vendorApex AS vendorApex,
       candidates
Run yourself →

Reads a 20-host adopter sample and the ASNs announcing its IP addresses.


MATCH (:TECHNOLOGY {name: $name})<-[:RUNS_TECHNOLOGY]-(h:HOSTNAME)
WITH h LIMIT 20
OPTIONAL MATCH (h)-[:RESOLVES_TO]->(:IPV4)-[:ANNOUNCED_BY]->(ap:ANNOUNCED_PREFIX)
OPTIONAL MATCH (a:ASN)-[:ROUTES]->(ap) WHERE a.name IS NOT NULL
RETURN h.name AS host, a.name AS asn
LIMIT 200
Run yourself →

Or query Whisper from your own LLM workflow via the Whisper MCP server.