1. Learning and Preparation

Before I even started studying, I wanted to understand what to expect. The Solutions Architect – Associate exam tests a wide range of topics: architectural principles, high availability, security, cost optimization, and many services like EC2, S3, RDS, Lambda, or VPC.

I divided my preparation into three phases:

Phase 1: Refreshing the basics
I started with the free AWS Skill Builder, where there’s an official course called "Exam Prep: AWS Certified Solutions Architect – Associate". It gives you a good sense of the structure and depth of the questions. Additionally, I bought two topic-related courses on Udemy to deepen my knowledge further – they offered many practical examples and explanations that helped me a lot in understanding more complex subjects.

Phase 2: Intensive training
Then I used Udemy courses from instructors like Stéphane Maarek and Tutorials Dojo. I found the many hands-on labs particularly helpful – for example, setting up a VPC or an Auto Scaling group. These exercises helped me a lot to truly understand the concepts.

Phase 3: Exam simulations
In the last two weeks before the exam, I focused on practice exams. The questions on platforms like Whizlabs or Tutorials Dojo were often very similar to the real ones – sometimes almost identical in the way they were phrased.
I tried not only to know the correct answer but also to understand why the other answers were wrong – that’s crucial!

2. Equipment and Room Requirements

I decided to take the exam online from home – convenient, but with clear rules.

Technical requirements:

• A reliable laptop or PC
• A stable internet connection (LAN preferred)
• A working webcam and microphone

Before the exam, a Pearson VUE tool automatically checks whether your camera, sound, and network are fine.

Room preparation:
The room must be clean and quiet – no books, no notes, no other person in the room. I even had to briefly show my walls by moving the camera around. My desk was completely empty, and I placed my smartphone far away. That may seem a bit strict, but it ensures fairness.

3. Registration and Identity Check

Registration is done through the AWS Certification Portal. There, you can choose whether to take the exam online or in a test center.

After registration, you receive an email with all the steps. On the day of the exam, I simply clicked “Start Exam”. Then a chat window opened with the proctor.

The proctor checked my identity using my ID, asked me to show the entire room with the webcam, and verified that there were no unauthorized items nearby. After a few minutes, everything was ready – and the exam could begin.

4. The Exam Process

The exam lasts 130 minutes and consists of about 65 multiple-choice questions. Some questions are short and direct, others quite long and describe complex architectural scenarios.

I got into the habit of first answering all the questions I was sure about and marking the rest. In the end, I still had enough time to calmly review about 10 difficult questions.

A small tip:

Read the questions very carefully – sometimes a single word (“cost-effective”, “highly available”, or “fault tolerant”) changes the entire meaning.

After I submitted the last question, the system immediately displayed: “Your result will be available in next 5 days.”
Then, the email came: “Congratulations! You passed the exam!”
That was a great feeling!

5. Useful Resources and Tips

If you want to pass the AWS Certified Solutions Architect – Associate exam, these resources can help you:

• AWS Skill Builder: Official, free learning platform
• AWS Whitepapers: Especially “Well-Architected Framework” and “Security Best Practices”
• Udemy: Courses by Stéphane Maarek or Neal Davis
• Tutorials Dojo / Jon Bonso Practice Exams: Realistic practice questions
• AWS Free Tier: To try out services without costs

Conclusion

The path to the AWS Certified Solutions Architect – Associate was not only a technical challenge for me but also a personal journey. I learned a lot about modern cloud architecture and understood how important good design in AWS really is.

So if you’re thinking about taking this step: Do it! With patience, curiosity, and solid preparation, you can succeed. And the certification opens many doors in the IT world.

Good luck and have fun on your own AWS adventure!

The post Mein Weg zum AWS Certified Solutions Architect – Associate appeared first on Rhein-Ruhr-Informatik.

In modern software development, speed and scalability are crucial. Companies want to deliver features quickly without worrying about maintaining infrastructure. This is where serverless computing shines.

With AWS Lambda and Amazon API Gateway, developers can build a fully functional REST API without managing servers. AWS automatically takes care of scaling, availability, and billing — you only pay for the requests that are actually processed.

In this article, we will explore how to set up a simple REST API using AWS API Gateway and AWS Lambda, with examples in Python.

What is Serverless?

The term serverless doesn’t mean “no servers” — servers are still involved, but they are fully managed by the cloud provider. Developers focus only on writing code, while AWS handles:

– Provisioning and scaling (from zero to millions of requests)
– High availability
– Security and patching
– Billing based on actual usage

For REST APIs, the combination of API Gateway and Lambda has become a common pattern. Let’s see how they work together.

Architecture Overview

The flow looks like this:
1. A client (browser, mobile app, Postman) sends a request to an API Gateway endpoint.
2. API Gateway routes the request to a configured Lambda function.
3. The Lambda function runs your custom code (Python in our case).
4. Lambda returns a response, which API Gateway forwards back to the client.

This simple architecture is powerful because you can connect multiple Lambda functions to different API routes and methods (e.g., GET /users, POST /orders).

Step-by-Step Setup

1. Create a Lambda Function

1. Log in to the AWS Management Console.
2. Go to AWS Lambda → Create function.
3. Choose Author from scratch, give it a name (e.g., hello-world), and select Python 3.x as runtime.
4. In the code editor, paste the following function:

import json

def lambda_handler(event, context):
    name = event.get("queryStringParameters", {}).get("name", "World")
    return {
        "statusCode": 200,
        "headers": {"Content-Type": "application/json"},
        "body": json.dumps({"message": f"Hello, {name}!"})
    }

2. Create an API Gateway

1. Go to Amazon API Gateway → Create API.
2. Choose HTTP API (simpler) or REST API (more configurable). For this tutorial, select HTTP API.
3. Create a new API and attach it to your Lambda function (hello-world).
4. Deploy the API.

3. Test the API

Once deployed, you will get an endpoint URL such as:

https://abc123.execute-api.us-east-1.amazonaws.com/default/hello-world

Now test it:

curl "https://abc123.execute-api.us-east-1.amazonaws.com/default/hello-world?name=Alice"

Response:
{ "message": "Hello, Alice!" }

Congratulations! You have just built a serverless REST API with AWS.

Why Use API Gateway + Lambda?

– Scalability: Handles traffic spikes automatically.
– Cost efficiency: Pay only when functions are executed.
– Simplicity: No server management, no patching, no scaling headaches.
– Flexibility: Connect Lambda to databases (DynamoDB, RDS), queues (SQS), or even event streams (Kinesis).

Next Steps

What we built is a minimal example. In production, you might:
– Add authentication & authorization (AWS Cognito, IAM policies, custom JWT).
– Use Infrastructure as Code (AWS SAM, CDK, or Terraform).
– Enable logging & monitoring (CloudWatch, X-Ray).
– Connect to other AWS services for full applications.

Conclusion

AWS API Gateway and AWS Lambda together make it incredibly easy to create serverless REST APIs. With just a few clicks and a small Python script, you can deploy an endpoint that scales automatically and costs only when used.

If you are building modern applications, experimenting with microservices, or simply want to avoid server management, this serverless approach is a great starting point.

The post Aufbau eines serverlosen REST-APIs mit AWS API Gateway und Lambda appeared first on Rhein-Ruhr-Informatik.