AWS Foundations

#2 – IAM Basics

AWS Identity and Access Management (IAM) is a global AWS service used to manage access to AWS resources. When an AWS account is first created, a root account is created automatically. The root user has full access to the account. However, it is best practice not to use the root user for everyday tasks. Instead, […]

AWS Foundations

#1 – AWS Cloud Introduction

Amazon Web Services (AWS) started as an internal infrastructure used by Amazon. Over time, the company realised other organisations could benefit from the same infrastructure, so they began offering it as a service. The first AWS service launched was SQS (Simple Queue Service), which allowed applications to communicate asynchronously using message queues. Today AWS provides

Cloud

Moving 500GB of Data Globally into Amazon S3

When collecting large datasets from systems distributed across multiple continents, the main challenge is usually reliable and fast data transfer into a central storage location. A common pattern in AWS for this scenario is combining S3 Transfer Acceleration and Multipart Upload. This approach works particularly well for workloads such as log aggregation, telemetry collection, or

Cloud

AWS Lambda Foundations

I created this presentation for an AWS Lambda knowledge-sharing session. The topics covered include event triggers, asynchronous workflows, AWS SAM, and security best practices.  This material is based on AWS public documentation and hands-on learning.

Cloud

Basics of DNS

Computers on the internet are identified using IP addresses. These can be up to 12 characters long for IPv4 (e.g. 255.255.255.255) and up to 39 characters long for IPv6 (e.g., 2001:db8::7334). Since these numbers are difficult for humans to remember, domain names are used as easy-to-read aliases for IP addresses. However, computers still need the

Software Engineering

Event driven architecture using request reply pattern

Here’s a short tutorial on using the request-reply pattern in an event-driven system. I find this particularly interesting because I’ve often wondered how a message producer can receive a response in such a system. How does that work in an event-driven architecture? Well, here’s the answer: you can design an event-driven system to handle responses

Scroll to Top