Learning priority #2 of 10

AWS core services

AWS appears in 277 positions, 2.5x more than GCP (111) or Azure (100), and pairs with Python in 146 roles. About 74% of GCP and Azure listings also mention AWS, so learn AWS first and treat a second cloud as optional.

4,022 remote positions from 975 source pagesData captured October 2026
Priority
#2
in the ranked recommendations
Positions naming any
291
23.0% of skill-tagged listings
Positions naming all
5
ask for the full bundle
Largest family
Software Eng.

The skills in this priority

How the bundle overlaps

Positions naming both skills in each pair

SkillAWSAmazon S3AWS LambdaAWS IAM
AWS277302910
Amazon S330382010
AWS Lambda2920365
AWS IAM1010513

The diagonal shows each skill's own total.

Where it pays off

Role families of positions naming any skill in the priority

A practical sequence

  1. Set up an AWS account with billing alerts and least-privilege IAM users or roles from day one.
  2. Learn S3 for storage, IAM for permissions and CloudWatch for logs, since nearly every workload touches them.
  3. Deploy a serverless function with AWS Lambda behind an API, then the same workload on a container service.
  4. Learn VPC basics: subnets, security groups and how services reach each other privately.
  5. Codify what you built with infrastructure as code so it can be destroyed and recreated.

A portfolio project that proves it

Deploy a file-processing pipeline: uploads land in S3, trigger a Lambda function that transforms them, results are written back with tightly scoped IAM permissions, and everything is defined in Terraform or CloudFormation.

How to show each skill

  • AWS: Deploy a small application on AWS using infrastructure as code, least-privilege IAM roles, and logging, then document the architecture and its estimated monthly cost.
  • Amazon S3: Configure an S3 bucket with encryption, a least-privilege bucket policy, lifecycle rules, and an event notification that triggers a Lambda function to process uploaded files.
  • AWS Lambda: Deploy Lambda functions through infrastructure as code that process events from API Gateway and SQS, with structured logging, retries, a dead-letter queue, and least-privilege roles.
  • AWS IAM: Write least-privilege IAM policies and roles for an application and its CI pipeline, then verify the permissions with IAM Access Analyzer or the policy simulator.