Skip to content

Prove your AWS skills

Knowing service names is the easy part of AWS. Lemma looks at how you design, secure and debug real setups, through connected infrastructure code, live sessions and an adaptive assessment.

How AWS is assessed

Preparing for an interview? AWS interview questions, junior to senior

What AWS competence looks like

A competent AWS engineer picks services for reasons. They can explain why a workload fits Lambda better than containers, or why a managed database beats running their own. IAM policies follow least privilege, networking is deliberate, and nothing sits in a public bucket by accident.

They also run what they build. Infrastructure lives in code, so environments are reproducible. They set up alarms on what matters, read CloudWatch logs to find the real failure, and keep an eye on the bill. When something breaks at night, they know where to look first.

AWS session
Live · 41:07

A live architecture walk-through

60 min · Learning · with Bruno H.

VPC layout Nina S. is sharing
ClientsLoad balancer
ServiceService
CacheDatabase

Bruno H. rated the session

Practitioner · after the call

Clear reasoning on iam and least privilege. Talked through trade-offs first.

Added to AWSAdded to record

IAM and least privilege

Roles, policies and boundaries that grant exactly what each service needs, and nothing more.

Networking and VPCs

Subnets, routing, security groups and private connectivity designed to keep internal services off the internet.

Compute choices

Choosing between EC2, containers and Lambda based on workload shape, cost and operational effort.

Storage and databases

Using S3, DynamoDB and RDS appropriately, with backups, encryption and access patterns in mind.

Infrastructure as code

Defining resources with CloudFormation, CDK or Terraform so environments are reviewable and repeatable.

Monitoring and cost

CloudWatch alarms, logs and tracing, plus tagging and budgets that keep spending visible and explainable.

What counts as evidence of AWS skills?

Certificates in AWS show an exam was passed. Lemma records how you work: sessions where you talked through a design or an incident, an adaptive test, and configuration in repositories you link. Every entry says where it came from. See the evidence methodology for how each source is weighed.

Skills Passport
Signed
71

AWS

Jordan L. · SCI recomputed 9 Oct

Evidence · 4 entries

  1. Infrastructure code in a repository

    GitHub connector · 9 Oct

    Verified
  2. A live architecture walk-through

    Live session · 2 Oct

    Rated 5.0
  3. Diagnosing a policy or template

    Adaptive assessment · 24 Sep

    Level 7.2
  4. Teaching IAM or networking

    Live session · 11 Sep

    Taught · 1.5x
Signature valid · checked today Share link
GitHub connector

Infrastructure code in a repository

Connect GitHub and attach a repository or commit with CloudFormation, CDK or Terraform you wrote. Lemma confirms the repo exists and your account can access it, then re-checks it periodically.

Live session

A live architecture walk-through

In a session, design or review an AWS setup with a practitioner: where traffic enters, how services talk, what fails first. Your reasoning about trade-offs is what they rate.

Adaptive assessment

Diagnosing a policy or template

The adaptive assessment shows realistic situations, such as an IAM policy that grants too much or a template that will not deploy, and you pick the correct diagnosis or fix from the options.

Live session

Teaching IAM or networking

Teaching a session on least privilege or VPC design counts more than learning it. Explaining the why behind a policy is strong evidence of real understanding.

How is an AWS skills test run on Lemma?

The AWS test is adaptive, 15 to 25 questions on failure modes, permissions and cost rather than service names, and it stops once your level holds steady. With sessions and linked work it sets your AWS SCI, where recent evidence carries more weight.

AWS assessment
0:42
Question 11Stops when your level holds
Difficulty7/10

A reporting job's IAM policy allows "s3:*" on "*". What is the right fix?

  1. AScope it to the bucket and actions it needs
  2. BAdd MFA to the role
  3. CMove the job to another region
  4. DRotate the access keys daily
Locks on submit
  1. Connect your infrastructure code

    Attach GitHub repositories or commits where you defined AWS resources. Reviewers see that real infrastructure exists behind your claim, and Lemma keeps checking that the link is still valid.

  2. Design a system in a live session

    Book a session with an AWS practitioner and work through a design or an outage together. They probe your choices on IAM, networking and compute, then rate the session.

  3. Take the adaptive AWS assessment

    Scenario-based multiple-choice questions cover security, architecture and operations. Difficulty adjusts after each answer, harder questions count for more, and timed questions with no going back keep it honest.

AWS skills: common questions

How do employers verify AWS skills beyond certifications?

Many ask candidates to walk through an architecture or debug a broken setup. Lemma gives you evidence of both: live sessions where a practitioner probes your design choices, and an adaptive assessment built on realistic policy and architecture scenarios. Connected infrastructure code on GitHub shows real work behind it.

Is an AWS certification enough to get a cloud job?

AWS certifications show broad knowledge of services and best practice, which is useful. Hiring teams also want proof you can apply it: secure IAM, sensible networking, reproducible infrastructure. Pairing a certification with hands-on evidence, like infrastructure code and rated sessions, gives a fuller picture.

What AWS projects make good portfolio evidence?

Pick projects defined in code that show judgement: a service with least-privilege IAM, a VPC with private subnets, or a serverless pipeline with alarms and retries. A short readme explaining the trade-offs helps. Attach the repository through GitHub so it sits on your AWS record.

Does Lemma access my AWS account?

No. Lemma does not connect to AWS accounts. Your AWS evidence comes from code you attach through GitHub, live sessions with practitioners and the adaptive assessment. You never share cloud credentials to build your record.

Start your AWS evidence record.

Lemma is in early access. Request an invite and we will email you when your place is ready.