We detected 49,519 companies using AWS. The most common industry is Software Development (18%) and the most common company size is 11-50 employees (39%). We find new customers by discovering URLs with known URL patterns through web crawling or modifications to subprocessor lists.
Note: We only track companies that use AWS to host a piece of critical infrastructure (ie. observability, analytics, data warehouse, VPN, etc). We also track companies that use these AWS products separately:
Source: Analysis of job postings that mention AWS (using the Bloomberry Jobs API)
Job titles that mention AWS
i
Based on an analysis of job titles from postings that mention AWS.
Job Title
Share
Director of Engineering/Software Engineering
20%
VP of Engineering
11%
Director of Data Science/Analytics
10%
Director of IT/Technology
9%
My analysis shows that AWS purchasing decisions are driven primarily by engineering and technology leadership, with Directors of Engineering and Software Engineering representing 20% of roles, VPs of Engineering at 11%, and Directors of Data Science at 10%. These buyers are focused on cloud migration, platform modernization, and AI/ML infrastructure. Their strategic priorities center on building scalable systems that support digital transformation, with heavy emphasis on security, compliance, and multi-cloud architectures.
Day-to-day AWS users span a wide spectrum from data engineers building pipelines in Databricks and managing S3 buckets, to backend developers deploying microservices with Lambda and ECS, to security engineers implementing Zero Trust architectures. I noticed significant emphasis on practitioners working with AI and GenAI solutions, including RAG implementations, vector databases, and LLM integrations. DevOps engineers automate CI/CD pipelines while data scientists leverage AWS for model training and deployment at scale.
The pain points reveal companies struggling to modernize legacy systems while maintaining security and compliance. I found recurring phrases like "migration planning for large-scale WAN transformations," "translate innovation from across the enterprise into scalable standards," and "ensure technology roadmaps are aligned with corporate strategy." Organizations are particularly focused on "reducing developer friction," "improving platform reliability," and building "secure, scalable, cost-efficient" solutions that enable faster time-to-market while managing the complexity of hybrid cloud environments.
👥 What types of companies use AWS?
Source: Analysis of Linkedin bios of 49,519 companies that use AWS
I noticed AWS customers span an incredibly diverse range of industries, but what unites them is they're all trying to solve operational problems through technology. These aren't just tech companies. They're ski resorts managing gondola systems, real estate advisors coordinating property listings, bridal shops handling inventory, healthcare providers processing patient data, and schools tracking student progress. Many are in transitional industries like construction, logistics, education, and hospitality that are digitizing traditional operations. They're building platforms, managing data, connecting stakeholders, and automating previously manual processes.
Most appear to be in the growth or maturity stage rather than early startup. The employee counts cluster heavily in the 11-50 and 51-200 ranges, with very few showing recent venture funding. When funding is mentioned, it's often older seed rounds or grants rather than active Series A or B raises. Many emphasize their longevity, mentioning they've been established for 10, 15, or 25-plus years. These are businesses with established operations that need reliable infrastructure, not experimental ventures.
🔧 What other technologies do AWS customers also use?
Source: Analysis of tech stacks from 49,519 companies that use AWS
Commonly Paired Technologies
i
Shows how much more likely AWS customers are to use each tool compared to the general population. For example, 287x means customers are 287 times more likely to use that tool.
I noticed that AWS customers are building sophisticated cloud-native applications with strong operational maturity. The presence of API Gateway at such extreme correlation levels (771.9x) tells me these aren't companies just using AWS for basic hosting. They're building microservices architectures and managing complex distributed systems. The combination with Route 53 and SES suggests they're handling production infrastructure at scale, managing their own DNS and transactional email rather than relying on simpler third-party solutions.
The pairing of AWS with Metabase (291.7x more likely) is particularly revealing. These companies are data-driven enough to run their own business intelligence infrastructure rather than buying expensive BI platforms. Similarly, the Atlassian suite appearing so frequently (Cloud at 79.3x, StatusPage at 250.0x) points to engineering-heavy organizations that need sophisticated project management and transparent uptime monitoring. The StatusPage correlation especially suggests these are B2B companies with enterprise customers who demand visibility into system reliability.
My analysis shows these are product-led B2B software companies, likely in growth or scale-up stages. They've moved past the earliest startup phase where you might use simpler tools, but they're building rather than buying when it comes to infrastructure. The emphasis on API Gateway and operational transparency tools like StatusPage suggests they're serving technical buyers or offering API products themselves. They need the flexibility and control that comes from managing their own infrastructure stack.
Alternatives and Competitors to AWS
Explore vendors that are alternatives in this category