DEV Community: Khalid ElGazzar

Power Up Your Website: A Serverless Frontend and Backend using 8 AWS services

Khalid ElGazzar — Mon, 08 Jul 2024 13:03:00 +0000

I recently made a presentation and demo for AWS meetup titled “Building Frontend and Backend using AWS S3 & Serveless, A Practical Project”. In this project, I created a serverless application that hosted a static website frontend on an S3 bucket and allowed communication from web forms on this static website to a serverless backend to provide a fully-fledged functionality (i.e. both frontend and backend). In this blog post, I will provide an overview of the 8 AWS services that were used in the demo to come up with the Web app up and running.

Furthermore, a brief description of the 8 AWS services and the steps used will be provided. This blog post (and demo) can be particularly useful to developers new to serverless architecture and to AWS users looking to explore serverless options. It can be beneficial in certain use cases such as: building a simple portfolio/company website or developing a landing page for a marketing campaign.

You can check the event presentation from this link. You can also fork my GitHub Repo containing the code and simple instructions from this link. Also, make sure to check this post shortly as I will be providing a video recording of the session to show the detailed steps. Furthermore, Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

I. Introduction

Serverless architecture offers numerous benefits for modern web applications. It removes the need to manage servers, allowing developers to focus mainly on the application logic. This mini-project demonstrates how to leverage AWS services to create a cost-effective and scalable serverless application containing both a frontend and a backend.

I will be hosting a static website consisting of 5 HTML pages (index, services, about, contact, & an error page) on an S3 bucket. These static files have a webform that can post data to the backend. In order to add backend functionality, I will be using an AWS python lambda function to receive a post request from the front end, store it in a DynamoDB, and then return a response.

The static assets also include a css file (for simple styling) and a JavaScript file (to implement fetchAPI call the backend). This call is received by the API gateway) and then passed over to the Lambda function for further processing.

The contact form contains a simple email registration form (name, email & submit button) that posts this data to the serverless backend upon click the submit button. I used Postman to simulate the post request during implementation. Note that the static files (HTML, CSS, JavaScript, and images) were stored on a GitHub repo and then were uploaded to an S3 bucket that was configured to be a static website hosting.

II. Frontend Services Overview

As explained earlier, the frontend of this application is a static website composed of HTML, CSS, and JavaScript files. Here’s a breakdown of the AWS services used for the frontend:

Amazon S3: S3 is a scalable object storage service that acts as the foundation for our static website. I uploaded the website’s HTML, CSS, and JavaScript files to an S3 bucket configured for static website hosting. This also mandated using ACLs or bucket policies to ensure granting proper public access. S3 provides ease of use, scalability, and cost-effectiveness for our use case.
Amazon Route 53: Route 53 is a highly available and scalable Domain Name System (DNS) web service. We used Route 53 to manage the domain name for our website. For more information about Route 53, you may check my earlier blog post covering in-depth details about Route 53.
Amazon Certificate Manager (ACM): ACM is a service that allows us to easily provision, manage, and deploy public and private SSL/TLS certificates for our websites. I used ACM to obtain an SSL certificate for our domain name.
Amazon CloudFront: CloudFront is a content delivery network (CDN) service that improves website performance by caching content at geographically distributed edge locations. In this project, I created a CloudFront distribution using AWS POPs that allows delivering content from caching locations near to the geographic location of the user and also allows converting the HTTP traffic into HTTPS.

III. Backend Services Overview

The backend for this application is serverless, meaning I will utilize services that allow automatic provisioning and scalability based on incoming requests. This is a huge advantage for developers eliminating the headache of managing and maintaining infrastructure. Here’s a look at the serverless backend services:

Amazon API Gateway: API Gateway is a fully managed service that allows developers to create, publish, and maintain APIs for various backends. It acts as the single entry point for frontend requests to our serverless backend. In this demo, I used REST APIs and configured the API GW to use REST.
AWS Lambda: Lambda is a serverless compute service that lets us run code without provisioning or managing servers. I created a Python Lambda function that handled the incoming API Gateway requests, inserted the received record into a DynamoDB table, and then responded to the frontend with a response.
Amazon DynamoDB: DynamoDB is a NoSQL database service that provides fast and scalable storage for applications. I used DynamoDB to store form data submitted from the website’s contact form in a simple JSON format.
AWS Identity and Access Management (IAM): IAM is a service that helps control access to AWS resources. I created the needed IAM roles to grant the Lambda function permission to interact with DynamoDB. Further roles were also created in order to grant the API GW access on the lambda function.

IV. High-Level steps to build the serverless web app in AWS

Here is a simplified overview of the steps involved in building this serverless application. You can refer to the video recording for the detailed steps:

Create an S3 bucket and configure website hosting. Upload the static website files (HTML, CSS, JavaScript) to the S3 bucket.
Purchase a domain name and configure Route 53 to manage the DNS records for your domain.
Obtain an SSL certificate from ACM for your domain name.
Create a CloudFront distribution and configure it to serve content from the S3 bucket with website hosting enabled.
Create an API Gateway and define an API resource.
Create a Lambda function to handle API Gateway requests. The Lambda function should process the request data and interact with DynamoDB.
Create a DynamoDB table to store the data submitted from the website’s contact form.
Configure IAM roles to grant the Lambda function permission to interact with DynamoDB.

IV. Conclusion

This blog post has provided a high-level overview on how to build a serverless application with a static website as the frontend and then connect it to a serverless backend. The overall steps take around 2 hours which clearly demonstrates that we can leverage AWS services to create a cost-effective and scalable application while focusing on development logic rather than server management. Note that this is not a production-level application and further optimizations and security hardnening can be implemented to reach this level.

You can check the event presentation from this link. You can also fork my GitHub Repo containing the code and simple instructions from this link. Also, make sure to check this post shortly as I will be providing a video recording of the session to show the detailed steps. Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

تعزيز موقع الويب الخاص بك: واجهة أمامية و خلفية بدون خادم باستخدام 8 خدمات من أيه دبليو إس

Khalid ElGazzar — Thu, 04 Jul 2024 12:55:00 +0000

Building AWS Serverless front & back ends | OneKC.pro

مرحبا بكم فى كبسولات الحوسبة السحابية من ألف محترف سحابي حيث نقدم مقدمة مبسطة للخدمات الرئيسية لأيه دبليو اس.

مقدمة

في الآونة الأخيرة، قدمت عرضًا توضيحيًا و مشروعا عمليا لعرض AWS Meetup بعنوان “بناء الواجهة الأمامية والخلفية باستخدام AWS S3 و منهجية Serverless و مشروع عملي”. في هذا المشروع، قمت بإنشاء تطبيق بدون خادم (serverless) يستضيف واجهة أمامية لموقع ويب على S3 Bucket ويسمح بالاتصال بالواجهة الخلفية منweb form لتوفير وظائف متكاملة ما بين الواجهة الأمامية والخلفية. في هذا المقال التقنى، سوف أقدم نظرة عامة على خدمات AWS الثمانية التي تم استخدامها في هذا المشروع المصغر. علاوة على ذلك، سيتم تقديم وصف موجز لخدمات AWS الثمانية والخطوات المستخدمة.

يمكن أن تكون هذا المقال التقني (و العرض التوضيحي و الفيديو المسجل للاجتماع) مفيدا بشكل خاص للمطورين الجدد على البنية بدون خادم (Serverless Architecture) وابضا ستكون مفيدة لمستخدمي AWS الذين يتطلعون إلى استكشاف خيارات البناء على AWS بدون خادم (Serverless). كذلك سيكون المشروع المصغر مفيدًا في حالات استخدام معينة مثل: بناء موقع ويب بسيط للشركة / موقع شخصى لعرض سابقة الأعمال أو تطوير صفحة landing page لصالح حملة تسويقية.

يمكنكم الاطلاع على العرض التقديمى التفصيلي من خلال هذا الرابط. كما يمكنكم أيضًا نسخ مستودع GitHub الخاص بي الذي يحتوي على الكود والتعليمات البسيطة من هذا الرابط. أيضًا تأكد من مراجعة هذا المنشور قريبًا حيث سأقوم بتوفير تسجيل فيديو للجلسة لعرض الخطوات التفصيلية.

يرجى ملاحظة أن جميع حقوق الملكية الفكرية لهذا المقال محفوظة. نظرًا لأنني واجهت العديد من حالات القرصنة مؤخراً، فقد نُشر هذا المقال فقط على منصة ألف محترف حوسبي
وبشكل موازى على موقع dev.to
اما اذا كنت تقرأه في مكان آخر، فيرجى إبلاغنا.عبر هذا الرابط

ما الذى سنقوم بعمله فى هذا المشروع المصغر؟

تقدم بنية بدون خادم (Serverless Architecture) العديد من الفوائد لتطبيقات الويب الحديثة حيث تزيل الحاجة إلى إدارة الخوادم، مما يسمح للمطورين بالتركيز بشكل أساسي على منطق التطبيق. يوضح هذا المشروع المصغر كيفية الاستفادة من خدمات AWS لإنشاء تطبيق ويب بدون خادم (ٍٍServerless) يحتوي على كل من الواجهة الأمامية والخلفية.

سأستضيف موقعًا ويب ثابتً يتكون من 5 صفحات (index, services, about, contact, & an error page) علىِ AWS S3 bucket تحتوي هذه الملفات الثابتة على Web form يمكنه ارسال البيانات إلى واجهة التطبيق الخلفية.

من أجل إضافة وظائف خلفية، سأستخدم AWS Lambda Python لاستقبال POST Request من الواجهة الأمامية، وتخزينه في قاعدة بيانات DynamoDB، ثم بعد ذلك يتم ارسال الرد على الواجهة الأمامية (Send a JSON response).

تتضمن ملفات المشروع أيضًا ملف CSS وملف JavaScript (لتنفيذ استدعاء واجهة تطبيقات الخلفية عبر FetchAPI). يتم تلقي الRequest بواسطة بAWS API Gateway ثم يتم تمريرها إلى Lambda للمعالجة الإضافية.

تحتوي ال Web form على نموذج تسجيل بريد إلكتروني بسيط (الاسم و البريد الإلكتروني و زر الإرسال) يقوم بارسال هذه البيانات إلى الواجهة الخلفية عند النقر فوق زر الإرسال. قمت أيضا باستخدام Postman لمحاكاة طلب POST أثناء التنفيذ. علما بأنه قد قمنا بتحميل الملفات الثابتة (HTML و CSS و JavaScript والصور) من GitHub إلى S3 bucket لاستضافة موقع ويب ثابت.

شكل رقم 1: المعمارية الكلية للتطبيق توضح واجهتى التطبيق الأمامية و الخلفية باستخدام Serverless AWS Services

نظرة عامة على خدمات الواجهة الأمامية

كما أوضحنا سابقًا، فإن الواجهة الأمامية لهذا التطبيق عبارة عن موقع ويب ثابت يتكون من ملفات HTML و CSS و JavaScript. فيما يلي تفصيل لخدمات AWS المستخدمة للواجهة الأمامية:

Amazon S3 هي خدمة تخزين (Object Storage Service) تعمل كأساس لموقع الويب الثابت. لقد قمت بتحميل ملفات HTML و CSS و JavaScript للموقع الإلكتروني إلى S3 bucket الذي تم تكوينه مع ضبط الاعدادات الخاصة به لاستضافة موقع ويب ثابت. يتطلب هذا أيضًا استخدام ACLs أو Bucket Policies لضمان منح وصول عام مناسب (granting public access to bucket objects). يوفر S3 سهولة فى الاستخدام و سعة لامحدودة و توفر عالي (High Availability) و تكلفة فعالة لحالة الاستخدام الخاصة بنا.
Amazon Route 53 هي خدمة ويب لنظام أسماء النطاقات (DNS) عالية التوفر. لقد استخدمت Route 53 لإدارة اسم المجال لموقعنا الإلكتروني. لمزيد من المعلومات حول Route 53، يمكنك مراجعة هذا المقال التقني باللغة الإنجليزية الذي يغطي تفاصيل أكثر حول Route 53.
Amazon Certificate Manager (ACM) هي خدمة تسمح لنا بتوفير وإدارة ونشر شهادات SSL/TLS العامة والخاصة لمواقعنا الإلكترونية بسهولة. لقد استخدمت ACM للحصول على شهادة SSL لاسم المجال الخاص بى فى هذا المشروع.
Amazon CloudFront هي خدمة شبكة توصيل المحتوى (Content Delivery Network – CDN) تتيح بالاساس تحسين أداء مواقع الويب عن طريق تخزين المحتوى مؤقتًا في مواقع متفرقة جغرافيًا. في هذا المشروع، قمت بإنشاء توزيع CloudFront باستخدام نقاط وجود (AWS POPs) والتي تسمح بتقديم المحتوى مواقع تخزين مؤقتة قريبة من الموقع الجغرافي للمستخدم بالاضافة إلى التحويل من HTTP إلى HTTPS.

نظرة عامة على خدمات الواجهة الخلفية

نظام التشغيل الخلفي لهذا التطبيق بدون خادم (Serverless Backend)، مما يعني أنني سأستفيد من الخدمات التي تسمح بال provisioning التلقائي وقابلية التوسع بناءً على الطلبات الواردة. هذه ميزة كبيرة للمطورين حيث توفر الجهد و الوقت اللازمين لإدارة وصيانة البنية التحتية. لنأخذ الان نظرة عامة على خدمات الواجهة الخلفية:

Amazon API Gateway هي خدمة مُدارة بالكامل تسمح للمطورين بإنشاء واجهات برمجة تطبيقات (APIs) ونشرها وصيانتها لواجهات خلفية مختلفة. تعمل كنقطة دخول واحدة لطلبات الواجهة الأمامية إلى نظامنا الأساسي بدون خادم. في هذا العرض التوضيحي، استخدمت واجهات برمجة تطبيقات من نوعية REST API وقمت بتكوين API Gateway لاستخدام REST.
AWS Lambda هي خدمة حوسبة بدون خادم تتيح لنا تشغيل التعليمات البرمجية (Code) دون الحاجة إلى provisioning أو إدارة الخوادم. لقد قمت بإنشاء دالة Lambda Python لمعالجة طلبات API Gateway الواردة، وإدراج البيانات المستلمة (على شكل JSON) في جدول DynamoDB، ثم ارسال الرد البرمجي (Response) على الواجهة الأمامية.
Amazon DynamoDB هي خدمة قاعدة بيانات NoSQL توفر تخزينًا سريعًا وقابلًا للتطوير للتطبيقات. لقد استخدمت DynamoDB لتخزين بيانات النماذج التي تم إرسالها من نموذج اتصال موقع الويب بتنسيق JSON بسيط.
AWS Identity and Access Management (IAM) هي خدمة تساعد في التحكم بالوصول إلى موارد AWS. لقد قمت بإنشاء أدوار IAM الضرورية لمنح دالة Lambda الإذن للتفاعل مع DynamoDB. كما تم إنشاء أدوار أخرى لمنح API Gateway حق الوصول إلى دالة Lambda.

شكل رقم 3: تم استخدام 4 خدمات أخرى لAWS لبناء واجهة التطبيق الخلفية بمعمارية Serverless

الخطوات المختصرة لبناء التطبيق

فيما يلي نظرة عامة مبسطة على الخطوات المتضمنة في بناء هذا التطبيق. يمكنك الرجوع إلى تسجيل الفيديو للخطوات التفصيلة:

إنشاء S3 Bucket و تجهيزه لاستضافة موقع ويب. قم بتحميل ملفات موقع الويب الثابتة (HTML و CSS و JavaScript) إلى S3 Bucket .
شراء اسم مجال (Domain Name) وتكوين Route 53 records لإدارة سجلات DNS لمجالك.
الحصول على شهادة SSL من ACM لاسم المجال الخاص بك.
إنشاء توزيع CloudFront ضبطه لتقديم المحتوى من S3 Bucket.
إنشاء API Gateway وتحديد مورد واجهة برمجة تطبيقات (API).
إنشاء دالة Lambda لمعالجة طلبات API Gateway. حيث يجب أن تعالج دالة Lambda بيانات الطلب (request) ثم تتفاعل مع DynamoDB لتخزين البنات التى تم استلامها من واجهة التطبيق الأمام.
إنشاء جدول DynamoDB لتخزين البيانات المقدمة من نموذج اتصال موقع الويب.
تكوين أدوار IAM لمنح دالة Lambda الإذن للتفاعل مع DynamoDB.

خاتمة

لقد قدم هذا المقال التقني نظرة عامة حول كيفية بناء تطبيق بدون خادم (Serverless) ذو واجهة أمامية بدون خادم ثم توصيله بواجهة خلفية بدون خادم أيضاً. تستغرق الخطوات الإجمالية للمرحلتين حوالي ساعتين مما يوضح بشكل جلي أنه يمكننا الاستفادة من خدمات AWS لإنشاء تطبيق سريع و عملى و قابل للتطوير و ذو تكلفة قليلة مع التركيز على منطق التطوير بدلاً من إدارة الخوادم. لاحظ أن هذا ليس تطبيقًا على مستوى الإنتاج (Not Production Ready) ويمكن تنفيذ المزيد من التحسينات وتعزيز الأمان (Security Best practices) للوصول إلى هذا المستوى.

اذا اعجبكتم هذه الكبسولة السحابية فسارعوا بالاشتراك فى قائمة ألف محترف حوسبي البريدية ليصلكم كل جديد – نقوم بنشر كبسولة جديدة كل فترة قصيرة على أمل أن نساعدكم فى تطوير مهاراتكم التقنية.

كذلك تابعونا على منصات التواصل الاجتماعى لتصلكم عروضنا الجديدة و كوبونات توفير ألف محترف سحابي.

Demystifying AWS: An Introductory Guide to 4 Key AWS Services

Khalid ElGazzar — Mon, 24 Jun 2024 11:02:00 +0000

Introduction

If you are thinking about creating a new system or moving your existing systems to the cloud, it is important that you have a good knowledge of the cloud services provided by AWS, as AWS cloud services provide reliable, secure, efficient, and cost-effective systems effectively in the cloud.

This blog post unravels the core concepts of cloud computing, explores the advantages of using AWS, and delves into four of AWS fundamental services. Whether you’re a tech enthusiast or a developer venturing into the cloud realm, this blog post equips you with the knowledge to navigate the exciting world of AWS.

I recently made a presentation for AWS meetup titled “Introduction to AWS ey Services”. You can check the event presentation from this link. Also, make sure to check this post shortly as I will be providing a video recording of the session to show the detailed steps.

Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

Cloud Computing 101

Cloud computing refers to the on-demand delivery of IT resources—servers, storage, databases, networking, software, analytics, intelligence, and more—over the internet. Unlike traditional on-premises infrastructure, where you manage physical hardware and software, cloud computing offers a scalable, pay-as-you-go model. This eliminates the upfront costs of hardware and simplifies maintenance, allowing you to focus on your core business activities.

Why Choose AWS?

AWS stands out as the frontrunner in the cloud computing landscape, boasting a vast array of services, global reach, and unparalleled security. With a multitude of regions and availability zones strategically located worldwide, AWS ensures exceptional service uptime and low latency. Additionally, AWS consistently ranks at the forefront of Gartner reports, solidifying its position as a trusted and reliable cloud platform.

Understanding Virtualization and Containerization

Virtualization, a foundational concept in cloud computing, enables the creation of multiple virtual machines (VMs) on a single physical server. This allows efficient utilization of hardware resources and facilitates running various operating systems and applications simultaneously. Containerization leverages a more lightweight approach, packaging an application and its dependencies into a container that can be seamlessly deployed across different environments. Containers offer faster startup times and better resource utilization compared to VMs.

Evolution of Cloud and Hosting

Cloud computing has undergone a remarkable transformation, evolving from dedicated servers to the serverless architecture we witness today. Dedicated servers provide complete control but require extensive hardware management. Virtual Private Servers (VPS) emerged as a more cost-effective solution, offering dedicated resources within a shared physical server. Shared hosting further reduces costs but comes with limitations on resource allocation. Cloud hosting and the subsequent rise of cloud computing models like IaaS (Infrastructure as a Service), PaaS (Platform as a Service), SaaS (Software as a Service), and FaaS (Function as a Service) signify a significant shift towards on-demand, scalable, and flexible IT solutions.

Demystifying Cloud Computing Models

IaaS (Infrastructure as a Service): Provides the building blocks – servers, storage, networking – for you to deploy and manage your own applications.
PaaS (Platform as a Service): Offers a complete development and deployment platform, eliminating the need to manage underlying infrastructure.
SaaS (Software as a Service): Delivers ready-to-use applications accessible over the internet, such as Salesforce or Gmail.
FaaS (Function as a Service): Executes code snippets without the need to provision or manage servers, ideal for microservices and event-driven architectures.

Deployment Models: Public, Private, Hybrid, and Community Cloud

Public Cloud: Offers shared resources over the internet, ideal for cost-effective solutions.
Private Cloud: Provides dedicated infrastructure for a single organization, ensuring greater security and control.
Hybrid Cloud: Combines aspects of both public and private cloud, offering a flexible and scalable environment.
Community Cloud: Shared infrastructure among multiple organizations with a common interest, often used for specific research or education projects.

Navigating the AWS Infrastructure

AWS boasts a robust global infrastructure that spans Regions, Availability Zones (AZs), Local Zones, Wavelength Zones, and Points of Presence (PoPs). Regions are geographically distinct locations with multiple AZs for redundancy. Local Zones offer ultra-low latency connections for latency-sensitive applications. Wavelength Zones place AWS compute and storage services at the edge of the mobile network, enabling seamless mobile application experiences. PoPs provide internet connectivity for efficient data transfer.

AWS Services: A Glimpse into the Key AWS Services

While AWS offers a vast array of services, this post highlights a few fundamental ones:

Identity and Access Management (IAM): Controls access to AWS resources, ensuring security and compliance.
Virtual Private Cloud (VPC): Creates a logically isolated network within the AWS cloud for your resources.
Amazon Elastic Compute Cloud (EC2): Provides scalable virtual servers for running a wide range of applications.
Amazon Simple Storage Service (S3): Offers secure, highly available object storage for various data needs.

Kickstart your AWS Cloud Journey

AWS offers a Free Tier that allows you to experiment and explore its services without any upfront costs. To embark on your AWS journey, you’ll need to create an account and set up an IAM user, and a credit card. Your credit card will not billed for the first 12 months if you only used the AWS free tier services.. Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

You can check the event presentation from this link. Also, make sure to check this post shortly as I will be providing a video recording of the session to show the detailed steps.

مقدمة إلى خدمات أيه دبليو إس

Khalid ElGazzar — Thu, 20 Jun 2024 12:02:00 +0000

مقدمة إلى خدمات AWS الجزء الأول | كبسولات حوسبية احترافية |
Intro to AWS – part 1

مرحبا بكم فى كبسولات الحوسبة السحابية من ألف محترف سحابي حيث نقدم مقدمة مبسطة للخدمات الرئيسية لأيه دبليو اس (AWS).

مقدمة إلى خدمات (أيه دبليو أس)

إذا كنت تفكر في إنشاء نظام جديد أو نقل أنظمتك الحالية إلى السحابة الإلكترونية، فمن المهم أن تكون لديك معرفة جيدة بالخدمات السحابية التى تقدمها AWS، حيث توفر خدمات السحابة من أيه دبليو أس أنظمة موثوقة وآمنة وفعالة و اقتصادية التكلفة بشكل فعال في السحابة.

يمكنكم الاطلاع على العرض التقديمى التفصيلي من خلال هذا الرابط.

دليل الشخص المبتدئ للتعامل مع الحوسبة السحابية من أيه دبليو إس

تعتبر هذه المقالة مقدمة شاملة لخدمات أمازون للويب (AWS)، وهي أبرز منصة للحوسبة السحابية. حيث نعرض المفاهيم الأساسية للحوسبة السحابية، و نوضح مزايا استخدام AWS، و الخدماتها الأساسية التى تقدمها.

سواء كنت مهتمًا بالتكنولوجيا أو مطورًا أو ترغب فى بد رحتلك فى عالم التكنولوجيا، فإن هذا الدليل يزودك بالمعرفة للتنقل في خدمات AWS المختلفة.

الشعار الجديد (يمين) و القديم (بسار) لخدمات أمازون السحابية

أساسيات الحوسبة السحابية

تشير الحوسبة السحابية إلى تقديم الموارد التقنية – مثل الخوادم والتخزين وقواعد البيانات والشبكات والبرمجيات والتحليلات والذكاء وغيرها – عند الطلب عبر الإنترنت. على عكس البنية التحتية التقليدية في المواقع، حيث تدير الأجهزة والبرمجيات المادية، تقدم الحوسبة السحابية نموذجًا يتيح الدفع حسب الاستخدام والتوسع بسهولة. وهذا يقضي على التكاليف الأولية للأجهزة ويبسط الصيانة، مما يسمح لك بالتركيز على الأنشطة الأساسية لعملك.

لماذا تختار أيه دبليو إس؟

تبرز AWS كمقدم خدمة سحابية رائد في مجال الحوسبة السحابية، بفضل مجموعة واسعة من الخدمات، والتواجد العالمي، والأمان غير المسبوق. بفضل العديد من المناطق ومناطق التوفر المتاحة استراتيجيًا في جميع أنحاء العالم، تضمن AWS فترات تشغيل متواصلة وانخفاض في التأخير. بالإضافة إلى ذلك، تحتل AWS دائمًا مكانة رائدة في تقارير Gartner، مما يؤكد مكانتها كمنصة سحابية موثوقة وموثوق بها.

لمحة من خدمات امازون السحابية المختلفة

فهم المحاكاة الافتراضية و الحاويات

مبدأ ال Hardware Virtualization هو أحد المفاهيم الأساسية في الحوسبة السحابية، حيث يتمكن المستخدم من إنشاء العديد من الآلات الافتراضية (VMs) على خادم مادي واحد. يتيح هذا استخدامًا فعالًا للموارد الأجهزة ويسهل تشغيل أنظمة التشغيل والتطبيقات المختلفة بشكل متزامن.

أما الContainers (و ما يعرف بالحاويات) فهي تتيح نهج أخف وزنًا أكثر من الVMs، حيث يتم تغليف تطبيق و مشتملاته في حاوية يمكن نشرها بسهولة عبر بيئات مختلفة. توفر الحاويات أوقات بدء أسرع واستخدامًا أفضل للموارد مقارنة بـ VMs.

تطور الحوسبة السحابية والاستضافة

شهدت الحوسبة السحابية تحولًا ملحوظًا، و تطورًا كبيرا فى الخدمات التى تقدمها مما اتاح للعديد من الشركات الناشئة سرعة تنفيذ منتاجاتها البرمجية و سرعة و سهولة الوصول إلى المستخدم المستهدف.

نماذج الحوسبة السحابية

IaaS (البنية التحتية كخدمة): توفر القواعد الأساسية – الخوادم والتخزين والشبكات – لنشر وإدارة تطبيقاتك الخاصة.
PaaS (منصة كخدمة): تقدم منصة تطوير ونشر كاملة، مما يلغي الحاجة إلى إدارة البنية التحتية الأساسية.
SaaS (برنامج كخدمة): توفر تطبيقات جاهزة للاستخدام عبر الإنترنت، مثل Salesforce أو Gmail.
FaaS (وظيفة كخدمة): تنفذ مقاطع الشفرة (source code) دون الحاجة إلى توفير أو إدارة الخوادم، مثالية للخدمات المعمارية الصغيرة والمحركة بالأحداث.

نماذج النشر (Deployment Models) : سحابة عامة، وخاصة، وهجينة، ومجتمعية

السحابة العامة (Public Cloud) : توفر موارد مشتركة عبر الإنترنت، مثالية لحلول فعالة من حيث التكلفة.
السحابة الخاصة (Private Cloud) : توفر بنية تحتية مخصصة لمؤسسة واحدة، مما يضمن مزيدًا من الأمان والتحكم.
السحابة الهجينة **(Hybrid Cloud)** : تجمع بين جوانب السحابة العامة والخاصة، مما يوفر بيئة مرنة وقابلة للتوسيع.
السحابة المجتمعية **(Community Cloud) :** بنية تحتية مشتركة بين عدة مؤسسات ذات مصلحة مشتركة، وغالبًا ما تستخدم لمشاريع بحثية أو تعليمية محددة.

التنقل في بنية البنية التحتية لـ أيه دبليو إس

لدى AWS ببنية تحتية قوية تمتد عبر المناطق (Regions) ومناطق التوفر (Availability Zones) والمناطق المحلية (Local zones) ومناطق الطول الموجي (Wavelength zones) ونقاط الوجود (Points of Presence). تعتبر المناطق مواقع جغرافية كبيرة تحتوي على عدة مناطق توفر. توفر المناطق المحلية اتصالات بالنسبة إلى التأخير المنخفض لتطبيقات التأخير الحساسة. تضع مناطق الطول الموجي خدمات AWS للحوسبة والتخزين عند حافة الشبكة المحمولة، مما يتيح تجارب تطبيق متماسكة للتطبيقات المحمولة. توفر نقاط الوجود توصيل الإنترنت لنقل البيانات بكفاءة.

خدمات أيه دبليو إس: لمحة عن الخدمات الرئيسية

بينما تقدم AWS مجموعة واسعة من الخدمات تزيد عن 200 خدمة، يسلط هذا الجزء الضوء على بعض الخدمات الأساسية و التى سنراها سويا فى الجزء العملى:

إدارة الهوية والوصول (IAM): تتحكم في الوصول إلى موارد AWS، مما يضمن الأمان والامتثال.
شبكة خاصة افتراضية (VPC): تنشئ شبكة منعزلة لوجيكيًا داخل سحابة AWS لمواردك.
خدمة الحوسبة المرنة لأمازون (EC2): توفر خوادم افتراضية قابلة للتوسع لتشغيل مجموعة واسعة من التطبيقات.
خدمة تخزين الكائنات البسيطة لأمازون (S3): توفر تخزينًا آمنًا ومتاحًا بشكل عالي لاحتياجات البيانات المختلفة.

كيف يمكنك البدء مع AWS؟

تقدم AWS خدمات مجانية لمدة سنة بحيث يمكنك تجربة واستكشاف خدماتها دون أي تكاليف مقدمة. للانطلاق في رحلتك مع AWS، ستحتاج إلى إنشاء حساب وإعداد مستخدم IAM بالاضافة إلى كارت ائتمانى.

الخلاصة:

فى هذا العرض التقديمى تحدثنا عن الخدمات السحابية الأساسية التى تقدمها AWS. يمكنكم الاطلاع على العرض التقديمى التفصيلى من خلال هذا الرابط. و سوف يتم تخصيص عروض تقديمة أخري لتوضيح التفاصيل المختلفة لكل خدمة من هذه الخدمات.

كذلك تابعونا على منصات التواصل الاجتماعى لتصلكم عروضنا الجديدة و كوبونات توفير ألف محترف سحابي.

10 Essential System Design Elements You Need to Know (Part 2)

Khalid ElGazzar — Tue, 26 Dec 2023 15:17:00 +0000

Introduction

In the first part of this series, I covered 5 essential system design elements, such as load balancers, proxy servers, database sharding, caching, and indexing. These elements are critical for building scalable, efficient, and reliable systems. In this second part, we’ll cover 5 more essential system design elements, such as message queues, microservices, containerization, event-driven architecture, and monitoring. These elements are also critical for building modern systems, and understanding them is essential for any developer.

1. Database Sharding

In the first part of this blog post, I provided an overview of databases and how they are a prominent component in any system design problem. Now, it is time to take a closer look at some of the techniques used mostly with NoSql databases in order to allow distributing the data across multiple servers and improve performance and scalability. Database sharding is a technique for splitting a large database into smaller, more manageable pieces. It can be done in various ways, such as range-based sharding or hash-based sharding. In range-based sharding, the data is partitioned based on a range of values, such as date or ID. In hash-based sharding, the data is partitioned based on a hash value of a column. Sharding has its challenges, such as data consistency and distribution, but it’s an essential technique for building large-scale, high-performance systems. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

2. Microservices

The second essential system design element I will be covering is microservices. Microservices are a modern approach to building large, complex systems. Microservices architectures break down a system into smaller, independent services that can be developed, deployed, and scaled independently. Each microservice has its own business logic and data storage, and communicates with other microservices through APIs or message queues. This enables greater flexibility, scalability, and fault tolerance, as well as easier maintenance and development. Microservices architectures are commonly used in large-scale web applications, such as e-commerce sites and social media platforms. Popular tools for building microservices include Spring Boot, Docker, and Kubernetes.

3. Containerization

The third essential system design element we’ll cover is containerization. Containerization is the process of packaging an application and its dependencies into a single container, which can then be deployed and run on any system that supports the containerization platform. Containerization enables greater portability, scalability, and flexibility, as well as easier maintenance and deployment. Containerization platforms, such as Docker and Kubernetes, have become popular in recent years due to their ease of use and scalability.

4. Event-Driven Architecture

The fourth essential system design element I will cover is event-driven architecture. Event-driven architecture (EDA) is an architectural pattern that emphasizes the use of events to trigger and communicate between different components of a system. In EDA, components can publish events when certain actions or changes occur, and other components can subscribe to these events to react accordingly. EDA enables greater flexibility, scalability, and fault tolerance, as well as easier maintenance and development. EDA is commonly used in modern web applications, such as social media platforms and online marketplaces, to enable real-time updates and notifications. Popular tools for implementing EDA include Apache Kafka, AWS Lambda, and Azure Event Grid.

5. Monitoring and Observability

The fifth and final essential system design element I will cover is Observability. Observability is all about ensuring that our system emits useful data about all of its internal systems in order to have a bird’s eye view of the system’s health and performance. Monitoring is about tracking a single metric or a single system. Monitoring can help detect and prevent system failures, identify bottlenecks and performance issues, and provide insights for system optimization and improvement. Monitoring can be done at various levels, such as the application, infrastructure, or network level. Popular monitoring and observability tools include Prometheus and Grafana. From a cloud perspective, Amazon CloudWatch is a well-known AWS tool for monitoring. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

Conclusion

In this second part of my series on essential system design elements, I’ve covered 5 more critical components of modern systems, such as message queues, microservices, containerization, event-driven architecture, and monitoring. These elements are essential for building scalable, efficient, and reliable systems. Understanding these elements is critical for any developer who wants to build modern, high-performance systems. I hope you found the series useful!

10 Essential System Design Elements You Need to Know (Part 1)

Khalid ElGazzar — Sat, 23 Dec 2023 02:02:20 +0000

Introduction

Building a scalable, efficient, and reliable system is a challenging task. You need to consider various factors such as performance, availability, security, and maintainability. One critical aspect of building a successful system is system design. Good system design is the foundation for building high-performance, robust systems. It involves making the right tradeoffs among various factors, such as performance, scalability, and maintainability. In this blog post, we’ll cover 10 essential system design elements that every developer should know. These elements are critical for building efficient, scalable, and reliable systems. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

1. Load Balancers and Proxy Servers

The first essential system design element I’m going to cover in this blog post is load balancers and proxy servers. Load balancers are critical components of modern web applications. They distribute incoming traffic across multiple servers to improve performance and availability. Load balancers can be either hardware or software-based. They monitor the health of the servers and route traffic to the healthy servers. Load balancing ensures that no single server is overloaded, which can lead to slow response times or even system failure.

Proxy servers are another essential component of modern web applications. They act as intermediaries between the clients and the servers. Proxy servers can be used for various purposes, such as caching, load balancing, and security. There are 2 main types of proxy servers: Forward proxy and Reverse proxy. A forward proxy acts as a delegate in expecting web requests, while a reverse proxy usually hides complex network schema behind. Caching proxies are an example of Forward Proxies. They store a copy of the response from the server and serve it to subsequent requests, reducing the number of requests to the server. On the other hand, Security proxies are an example of reverse proxies that protect your servers and applications from security threats, such as DDoS attacks or SQL injection attacks. A very prominent example of a reverse proxy that I have used in many projects is Nginx, which is a web server that can also be used in many other uses including reverse proxy, load balancer, mail proxy, and HTTP cache. For more information about Forward and Reverse proxies, click the corresponding link.

2. Databases

Databases are an essential system design component in any system design problem. Databases are critical components of modern systems. They store and manage data and provide efficient access to it. There are various types of databases, such as relational databases, NoSQL databases, and graph databases, etc. Relational databases are the most commonly used type of database. They store data in tables with a defined schema and support SQL for querying the data. NoSQL databases, on the other hand, store data in a schemaless way, allowing for more flexible data models. Graph databases store data as nodes and edges, making them ideal for working with complex data structures. Choosing the right type of database depends on various factors, such as data complexity, scalability, and performance requirements. In the second part of this blog post, I will provide more details about techniques used with NoSql Databases to achieve scalability and higher performance.

3. Caching and Indexing

The third essential system design element is caching and indexing. Caching is the process of storing frequently accessed data in memory or on disk to reduce the number of requests to the server. Caching can be done at various levels, such as application-level caching or database-level caching. Application-level caching involves storing data in memory or on disk within the application. Database-level caching involves caching query results or table data. Caching can significantly improve system performance, but it requires careful management to ensure data consistency and expiration.

Indexing is another essential technique for improving system performance. Indexing involves creating indexes on columns in a database table to improve the speed and accuracy of searches. Indexes allow the database to quickly locate the data based on the search criteria, reducing the number of rows that need to be scanned. However, indexing has its challenges, such as storage overhead and maintenance.

4. Throttlers

The fourth essential system design element I’m going to cover in this blog post are throttlers. Throttling is the process of limiting the number of requests a client can make to a server. Throttling can prevent server overload and ensure fair usage of resources. Throttling can be implemented at various levels, such as the network, application, or API level. Network throttling limits the bandwidth or connection speed of the client. Application throttling limits the number of requests a client can make to the application. API throttling limits the number of requests a client can make to the API. Throttling can be configured based on various factors, such as the client’s IP address, user agent, or session ID.

5. Message Queues

An essential system design element I will cover is message queues. Message queues are used to decouple different components of a system, enabling asynchronous communication. A message queue allows one component to send a message to another component, without the sender having to wait for the receiver to process the message. This enables greater scalability, fault tolerance, and flexibility. Message queues are commonly used in distributed systems, such as microservices architectures, to enable reliable communication between components. Popular message queue systems include Apache Kafka, RabbitMQ, and Amazon Simple Queue Service (SQS).

Conclusion

In this blog post, I covered 5 of the 10 essential system design elements that every developer should know. Load balancers and proxy servers are critical components of modern web applications. Database sharding, caching, and indexing are essential techniques for improving system performance. Databases are the backbone of modern systems, and choosing the right type of database is critical for success. Throttlers are essential for preventing server overload and ensuring fair usage of resources. In the next blog post, I’ll cover the remaining 5 essential system design elements, so stay tuned! Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

In the second part of this series, I will cover 10 more essential system design elements, such as message queues, microservices, containerization, event-driven architecture, and monitoring. These elements are critical for building scalable, efficient, and reliable systems. I will also provide practical tips and best practices for implementing these elements in your systems. Don’t miss it!

For more articles about System Design, please visit the System Design subsection at the Software, Architecture and Cloud blog - SWAC.blog.

Driving Business Growth through Digital Transformation: Key Factors to Consider

Khalid ElGazzar — Fri, 15 Dec 2023 12:47:26 +0000

Introduction

As technology continues to evolve at a breakneck pace, businesses that fail to adapt risk being left behind. Digital transformation is no longer an option but a strategic imperative for businesses of all sizes and industries. In this article, we’ll explore the key drivers of digital transformation, the types of digital transformation, the steps to implementing a digital transformation strategy, the benefits of digital transformation, the challenges and risks of digital transformation, and successful case studies of digital transformation.

Key Drivers of Digital Transformation

Digital transformation is driven by several key factors, including increasing customer expectations, competition and market pressures, and technological advancements. Customers today expect personalized and seamless experiences across multiple channels, and businesses that fail to deliver risk losing customers to competitors. Competition is fiercer than ever, with startups and disruptors entering the market and disrupting traditional business models. Technological advancements such as cloud computing, artificial intelligence, and the Internet of Things (IoT) are enabling businesses to operate more efficiently and create new revenue streams. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

Types of Digital Transformation

Digital transformation can take several forms, including business process transformation, customer experience transformation, product/service innovation transformation, and cultural/organizational transformation. Business process transformation involves reengineering existing processes to make them more efficient and effective using technology. Customer experience transformation involves improving the way customers interact with a business across multiple touchpoints. Product/service innovation transformation involves using technology to create new products or services or improve existing ones. Cultural/organizational transformation involves changing the way people work, think, and collaborate to drive digital innovation.

Steps to Implementing a Digital Transformation Strategy

Implementing a digital transformation strategy requires careful planning and execution. The following are the key steps to implementing a successful digital transformation strategy:

Identify business goals and priorities: Define the business objectives that the digital transformation strategy should address, such as increasing revenue, reducing costs, improving customer experience, or enhancing operational efficiency.
Assess current technology infrastructure and capabilities: Conduct a thorough assessment of the current technology landscape to identify gaps and opportunities for improvement.
Create a roadmap for digital transformation: Develop a comprehensive plan for the digital transformation journey, including timelines, budgets, and resources required.
Develop a plan for change management and employee training: Create a plan to manage the change associated with digital transformation, including employee training and communication.
Monitor and measure progress: Track the progress of the digital transformation strategy using key performance indicators (KPIs) and adjust the strategy as necessary based on the results. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

Benefits of Digital Transformation

Digital transformation can deliver a wide range of benefits to businesses, including:

Improved customer experience and engagement: By leveraging technology to deliver personalized and seamless experiences across multiple channels, businesses can increase customer loyalty and satisfaction.
Increased operational efficiency and productivity: Digital transformation can help automate and streamline business processes, reducing manual effort and errors, and enabling employees to focus on higher-value activities.
Enhanced decision-making and data-driven insights: Digital transformation can provide businesses with real-time data and insights, enabling better decision-making and more informed strategic planning.
Creation of new revenue streams and business models: By leveraging technology, businesses can create new products, services, and revenue streams that were previously impossible.
Increased competitiveness and market share: Digital transformation can help businesses stay ahead of the competition by enabling them to operate more efficiently, deliver superior customer experiences, and create innovative products and services.

Challenges and Risks of Digital Transformation

While digital transformation offers many benefits, it also poses some challenges. Here are some of the key challenges businesses may face when implementing digital transformation:

1. Resistance to Change

One of the biggest challenges businesses face when implementing digital transformation is resistance to change from employees. Employees may be resistant to change due to fear of job loss, lack of digital skills, or a preference for traditional ways of working.

2. Security Risks

Digital transformation exposes businesses to new security risks, such as cyber attacks and data breaches. This requires businesses to invest in robust cybersecurity measures and ensure that all employees are trained in best practices for data security.

3. Cost and Resource Requirements

Implementing digital transformation requires significant investments in technology, training, and infrastructure. This can be a significant cost for businesses, particularly small and medium-sized enterprises (SMEs) with limited resources.

4. Integration Challenges

Digital transformation involves integrating new technologies with existing systems and processes, which can be a complex and time-consuming process. This requires businesses to carefully plan and execute their digital transformation strategy to ensure seamless integration.

Conclusion

Digital transformation is no longer a buzzword; it is a necessity for businesses that want to remain competitive in today’s fast-paced and constantly evolving business environment. By embracing digital technologies, businesses can improve efficiency, enhance customer experience, and gain valuable insights into their operations. However, implementing digital transformation also poses challenges, such as resistance to change, security risks, and cost requirements. To overcome these challenges, businesses must carefully plan and execute their digital transformation strategy and ensure that all employees are trained in digital skills and best practices for data security.

I hope this blog post has provided you with a comprehensive overview of digital transformation and its benefits and challenges. If you have any questions or comments, please feel free to leave them in the comments section below. For more articles about Digital Transformation, please visit the Digital transformation subsection at the Software, Architecture and Cloud blog - SWAC.blog.

The Essential Guide to Linux System Monitoring with Top, Htop, and Vmstat

Khalid ElGazzar — Tue, 05 Dec 2023 13:11:00 +0000

Introduction

When it comes to running Linux servers and applications, monitoring system performance is crucial to ensuring everything is running smoothly. In this guide, we will provide an overview of three powerful command-line utilities that can help you monitor system performance: top, htop, and vmstat.

1- Getting Started with top

top is a simple and powerful tool that provides a real-time, dynamic view of the processes running on your Linux system. Here’s how you can get started with top:

Install top: Top is usually included with most Linux distributions. If it’s not installed on your system, you can install it using the package manager of your distribution. For example, on Ubuntu and Debian, you can install top with the command sudo apt-get install procps.
Launch top: To launch top, simply open a terminal window and type top.
Understanding the output: Top provides a lot of information, including CPU usage, memory usage, and process information. The default output shows the processes with the highest CPU usage at the top of the list. You can use the arrow keys to move up and down the list, and the q key to quit top. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

2- Getting Started with htop

htop is an improved version of top that provides a more user-friendly interface and additional features. Here’s how you can get started with htop:

Install htop: Htop is not usually installed by default on most Linux distributions. You can install it using the package manager of your distribution. For example, on Ubuntu and Debian, you can install htop with the command sudo apt-get install htop.
Launch htop: To launch htop, simply open a terminal window and type htop.
Understanding the output: Htop provides a similar set of information as top, but with a more user-friendly interface. You can use the arrow keys to move up and down the list, and the q key to quit htop.

3- Getting Started with vmstat

vmstat is a tool that provides information on the usage of system resources, including CPU, memory, and I/O. Here’s how you can get started with vmstat:

Install vmstat: Vmstat is usually included with most Linux distributions. If it’s not installed on your system, you can install it using the package manager of your distribution. For example, on Ubuntu and Debian, you can install vmstat with the command sudo apt-get install procps.
Launch vmstat: To launch vmstat, simply open a terminal window and type vmstat.
Understanding the output: Vmstat provides a lot of information, including CPU usage, memory usage, and I/O usage. The default output shows a summary of system activity since boot, as well as a real-time view of system activity. You can use the q key to quit vmstat.

4- Advanced Usage of top, htop, and vmstat

While top, htop, and vmstat provide a wealth of information on system performance out of the box, they also offer advanced options for more detailed analysis. Here are some examples of advanced usage:

Filtering: You can filter top and htop to show specific processes or system resources. For example, to show only the processes owned by a specific user, you can use the following command:

top -U username

Similarly, to show only the processes using a certain amount of CPU, you can use the following command:

top -o %CPU

Sorting: You can sort the output of top and htop based on various criteria such as CPU usage, memory usage, and process ID. To sort top by CPU usage, you can press the “P” key. To sort htop by memory usage, you can press the “F6” key and select the “MEM%” option.
Color-coded output: htop provides color-coded output to help you identify the processes that are consuming the most system resources. By default, processes using more than 75% of CPU or memory are displayed in red. You can adjust these values by pressing the “F2” key and selecting the “Display options” menu.
Continuous monitoring: vmstat can be used for continuous monitoring of system performance. You can use the “-n” option to set the interval between updates. For example, to monitor system performance every 5 seconds, you can use the following command:

vmstat -n 5
Redirecting output: You can redirect the output of top, htop, and vmstat to a file or another command for further analysis. For example, to save the output of top to a file, you can use the following command:

top -n 1 > top_output.txt

This command saves the output of top to a file called “top_output.txt”. Similarly, to pipe the output of vmstat to another command, you can use the following command:

vmstat 1 | awk '{print $1}'

This command pipes the output of vmstat to the awk command, which prints the first column of data (the timestamp) on each line.

With these advanced options, you can gain deeper insights into system performance and troubleshoot issues more effectively.

5- Conclusion

In conclusion, top, htop, and vmstat are powerful command-line utilities for monitoring system performance in Linux. With these tools, you can gain valuable insights into CPU, memory, and I/O usage on your system, and troubleshoot issues more effectively.

While top and htop provide real-time information on system performance, vmstat offers a more detailed view of system resource usage over time. By combining these tools and their advanced options, you can get a comprehensive view of your system’s performance.

In addition, the ability to filter, sort, and color-code output allows you to quickly identify processes that are consuming the most resources and take action accordingly. And with the ability to redirect output to a file or another command, you can perform further analysis on system performance data.

By mastering these tools and incorporating them into your Linux administration toolkit, you can optimize system performance and ensure that your applications are running smoothly. Whether you’re a system administrator or a developer, knowledge of these tools is essential for maintaining the health and performance of your Linux systems.

We hope this guide has provided you with a useful overview of top, htop, and vmstat, and their advanced usage. If you have any questions or comments, please feel free to leave them in the comments section below. Thank you for reading! Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

For more articles about AWS & how to begin your AWS journey, visit AWS section on the Software, Architecture & Cloud blog - SWAC.blog

GNU Linux File Permissions: Introductory Guide and Best Practices

Khalid ElGazzar — Wed, 29 Nov 2023 12:10:00 +0000

Introduction

Linux is a powerful operating system used by millions of people around the world. It is known for its stability, security, and flexibility, and is used in a wide range of applications, from servers and desktops to embedded devices and supercomputers.

One of the key features of Linux is its file system, which is based on a hierarchical tree-like structure. Each file and directory in the file system has a set of permissions that control who can access it and what actions they can perform on it. Understanding file permissions is essential for any Linux user, whether you’re a system administrator managing a large network of servers or a casual user working on a personal computer.

In this post, we’ll provide a comprehensive guide to Linux file permissions, starting with the basics of file permissions and ownership and moving on to more advanced topics like modifying permissions and best practices for setting file permissions. By the end of this post, you should have a solid understanding of how file permissions work in Linux and how to work with them effectively. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

Basic Concepts

Before we dive into the chmod command, let’s first cover some basic concepts related to file permissions in Linux.

In Linux, every file and directory has three sets of permission bits that determine who can read, write, and execute the file. The permission bits are represented by the letters r (read), w (write), and x (execute). Each set of permission bits represents a different class of users: the owner of the file, the group that the file belongs to, and everyone else.

For example, consider the following output from the ls command:

$ ls -l test.txt
-rw-r--r-- 1 john users 0 Apr 18 2023 test.txt

In this case, the file test.txt has the following permissions:

The owner of the file (john) has read and write permissions.
The group that the file belongs to (users) has read permissions.
Everyone else has read permissions.

The first character in the output (a hyphen in this case) indicates that this is a regular file. If the file were a directory, this character would be replaced by a d.

Ownership also plays a role in file permissions. In Linux, every file and directory has an owner and a group. The owner is usually the user who created the file, while the group is a collection of users who have certain permissions on the file.

For example, consider the following output from the ls command:

$ ls -l test.txt
-rw-r--r-- 1 john users 0 Apr 18 2023 test.txt

In this case, the file test.txt is owned by the user john and belongs to the group users.

The Different Types of Users

As we mentioned earlier, there are three types of users that can have permissions on a file in Linux: the owner, the group, and everyone else.

The owner is the user who created the file. The owner has the most control over the file and can read, write, and execute it (if the appropriate permission bits are set).

The group is a collection of users who have certain permissions on the file. By default, when a file is created, it belongs to the primary group of the user who created it. However, the group can be changed using the chgrp command.

Everyone else refers to all other users who are not the owner or a member of the group that the file belongs to. Everyone else has the least amount of control over the file and can only read it (if the appropriate permission bits are set).

The chmod Command

Now that we understand the basic concepts of file permissions in Linux, let’s move on to the chmod command.

The chmod command is used to modify the permissions of a file or directory. The syntax of the chmod command is as follows:

chmod [options] mode file/directory

The options for the chmod command can be used to modify the behavior of the command. Here are some of the most common options:

-R: Recursively apply the permissions to all files and directories under the specified directory.
-v: Verbose output. Show each file that is modified by the command.
-c: Verbose output. Show each file that is modified by the command, but only display if the permissions are actually changed.

The mode argument is used to specify the new permissions for the file or directory. There are two ways to specify the mode: numeric mode and symbolic mode.

Numeric Mode

In numeric mode, the permissions are represented by a three-digit number. Each digit represents a different set of permission bits: the first digit represents the permissions for the owner, the second digit represents the permissions for the group, and the third digit represents the permissions for everyone else.

Each digit is calculated by adding up the following values:

4: Read permission
2: Write permission
1: Execute permission

For example, to set read and write permissions for the owner, read permissions for the group, and no permissions for everyone else, you would use the following command:

$ chmod 640 test.txt

In this case, the first digit (6) represents the permissions for the owner (4 + 2 = 6), the second digit (4) represents the permissions for the group (4 = 4), and the third digit (0) represents the permissions for everyone else (no permissions).

Symbolic Mode

In symbolic mode, the permissions are represented by a combination of letters and symbols. Here are the different letters and symbols that can be used:

r: Read permission
w: Write permission
x: Execute permission
u: User (owner)
g: Group
o: Other (everyone else)
+: Add permissions
-: Remove permissions
=: Set permissions to exactly what is specified

For example, to set read and write permissions for the owner, read permissions for the group, and no permissions for everyone else, you would use the following command:

$ chmod u+rw,g+r,o-rwx test.txt

In this case, we’re using the u+rw option to add read and write permissions for the owner, the g+r option to add read permissions for the group, and the o-rwx option to remove all permissions for everyone else.

Best Practices

Now that we know how to use the chmod command to modify file permissions, let’s talk about some best practices for setting file permissions in Linux.

The principle of least privilege is a key concept in Linux security. It states that users and processes should be given only the minimum amount of access necessary to perform their tasks. In other words, don’t give users or processes more permissions than they need.

Here are some specific recommendations for setting file permissions in Linux:

Set the permissions to the minimum required for the user or process to perform their task.
Use groups to manage permissions instead of giving individual users permissions.
Use the umask command to set default permissions for newly created files and directories.

The umask command is used to set the default permissions for new files and directories. The umask value is subtracted from the maximum permissions to determine the default permissions. For example, if the umask value is 022, the default permissions for a new file would be 644 (666 – 022 = 644), and the default permissions for a new directory would be 755 (777 – 022 = 755).

Conclusion

In conclusion, understanding Linux file permissions is an essential skill for anyone working with Linux systems. The file system is the backbone of the operating system, and the ability to manage permissions is crucial for ensuring the security and stability of the system.

In this post, we’ve covered the basics of file permissions in Linux, including the meaning of the different permission bits, how ownership affects permissions, and how to use the chmod command to modify permissions. We’ve also discussed best practices for setting file permissions, including the principle of least privilege and the use of groups and the umask command.

By following these best practices and using the tools provided by Linux, you can ensure that your system is secure and that your files and directories are accessible only to those who need them. If you have any questions or feedback, please let us know. We hope this post has been helpful, and we wish you the best of luck in your Linux endeavors! Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

For more articles about AWS & how to begin your AWS journey, visit AWS section on the Software, Architecture & Cloud blog - SWAC.blog

Unlock your web development superpowers with WSL (Windows Subsystem for Linux)

Khalid ElGazzar — Tue, 21 Nov 2023 16:21:00 +0000

As a web developer working on Windows, you may have felt left out when it comes to certain tools and technologies that are more readily available on Linux-based operating systems. However, the introduction of Windows Subsystem for Linux (WSL) has changed the game for Windows developers, providing a way to run Linux commands and tools natively on Windows.

In this post, we’ll introduce you to WSL, explain how to install it, and explore some of the ways in which it can benefit your web development workflow. Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

What is WSL (Windows Subsystem for Linux) ?

Windows Subsystem for Linux is a feature of Windows 10 that allows you to run Linux-based applications directly on your Windows machine. This means that you can use tools and commands that were previously only available on Linux, without needing to set up a separate virtual machine or dual-boot your system.

There are two versions of WSL: WSL 1 and WSL 2. WSL 1 uses a translation layer to run Linux commands, while WSL 2 runs a full Linux kernel within a lightweight virtual machine. WSL 2 offers better performance and compatibility with Linux applications, but requires a more recent version of Windows 10.

Prerequisites

To use WSL, you’ll need a few things:

A Windows 10 machine with version 1903 or later
64-bit Windows
At least 4 GB of RAM

You’ll also need to enable the Windows Subsystem for Linux feature on your system. To do this, follow these steps:

Open the Start menu and search for “Turn Windows features on or off”.
Select the “Windows Subsystem for Linux” option and click OK.
Restart your computer when prompted.

Supported Distributions

WSL supports a variety of Linux distributions, including Ubuntu, Debian, Fedora, and more. You can install multiple distributions side-by-side and switch between them as needed.

Each distribution has its own set of packages and tools available, so you can choose the one that best suits your needs. For example, Ubuntu is a popular choice for web development due to its wide range of development tools and packages.

Installing WSL

There are a few different ways to install WSL on your system. Here are a few options:

Installing WSL through the Command Prompt (CLI)

To install WSL using the command prompt, follow these steps:

Open the Start menu and search for “Command Prompt”.
Right-click on the Command Prompt app and select “Run as administrator”.
Enter the following command and press Enter:

dism.exe /online /enable-feature /featurename:Microsoft-Windows-Subsystem-Linux /all /norestart
Restart your computer.

Installing WSL from the Windows CLI

Using the Microsoft Store to Install WSL

You can also install WSL through the Microsoft Store:

Open the Microsoft Store app.
Search for the Linux distribution you want to install (e.g. Ubuntu).
Click on the distribution and select “Get”.
Follow the prompts to install the distribution.

Installing Linux Distributions on WSL via the Terminal or GUI

Once you’ve enabled WSL on your system, you can install Linux distributions via the command line or using a graphical interface.

To install a distribution via the command line, open a terminal window and enter the following command:

wsl --install -d <distro>

Replace <distro> with the name of the distribution you want to install (e.g. “ubuntu”).

Alternatively, you can use the GUI method to install a Linux distribution:

Open the Microsoft Store app.
Search for the Linux distribution you want to install (e.g. Ubuntu).
Click on the distribution and select “Get”.
Wait for the distribution to download and install.

Running WSL for the first time

Accessing Linux Files from Windows

One of the benefits of using WSL is that you can access Linux files from within Windows, and vice versa. This means you can easily work with files and folders across both operating systems.

To access Linux files from Windows, you’ll need to know the file path. The file path for Linux files is different from the file path for Windows files, so you’ll need to use the appropriate path format.

For example, to access the home directory for the Ubuntu distribution, you would use the following path:

\\wsl$\Ubuntu\home\<username>

Replace <username> with your Ubuntu username.

Using WSL for Web Development

Now that you have WSL installed and set up, you can use it to improve your web development workflow in a variety of ways. Here are a few examples:

Running Web Servers

You can use WSL to run web servers on your local machine, just as you would on a Linux-based operating system. For example, you could install Apache or NGINX on your Ubuntu distribution and use it to serve web pages and applications.

Using Linux-Based Development Tools

Many web development tools and frameworks are designed to work best on Linux-based operating systems. With WSL, you can use these tools directly on your Windows machine, without needing to set up a separate virtual machine or dual-boot your system.

For example, you could use the command line tool “grep” to search for text within files, or use the “awk” tool to manipulate and analyze text data.

Developing Cross-Platform Applications

If you’re developing applications that need to run on both Windows and Linux, WSL can be a valuable tool for testing and debugging. You can use WSL to run your application in a Linux environment, ensuring compatibility and identifying any issues that may arise on different operating systems.

Removing WSL

If you decide you no longer need WSL on your system, you can easily remove it. To do so, follow these steps:

Open the Start menu and search for “Control Panel”.
Click on “Programs”.
Click on “Turn Windows features on or off”.
Uncheck the “Windows Subsystem for Linux” option and click OK.
Restart your computer.

Conclusion

Windows Subsystem for Linux (WSL) is a powerful tool for web developers working on Windows machines. With WSL, you can run Linux-based tools and applications directly on your Windows system, streamlining your workflow and improving your productivity. Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

By installing and using WSL, you can take advantage of Linux-based development tools, run web servers on your local machine, and develop cross-platform applications. And with support for a wide range of Linux distributions, you can customize your development environment to suit your needs.

So why not unlock your web development superpowers with WSL today? With a few simple steps, you can be up and running with a powerful Linux-based development environment on your Windows machine.

GNU Linux from a Developer’s Eye

Khalid ElGazzar — Thu, 16 Nov 2023 14:15:05 +0000

Linux (or GNU Linux) is a free and open-source operating system that has become the backbone of much of the modern technological landscape. While Linux has a reputation as a tool for system administrators and IT professionals, it is also an incredibly useful tool for developers.

In this blog post, I will introduce you to the basics of Linux from a developer’s perspective. We will cover the essential concepts that you need to know to be able to use Linux effectively in your development workflow. Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know

Brief Introduction to Linux

In this section, we will provide a brief introduction to Linux, including its history and its key features. We will also provide an overview of the various Linux distributions that are available and discuss which ones are most suitable for developers.

What is Linux?

Linux is a free and open-source operating system based on the Unix operating system. It was created in 1991 by Linus Torvalds, a Finnish software engineer, and has since become one of the most popular operating systems in the world.

Key Features of Linux

Linux has many features that make it an attractive choice for developers. Some of these key features include:

Free and open-source: Anyone can download, use, and modify Linux for free.
Stable: Linux is known for its stability and reliability.
Customizable: Linux is highly customizable, allowing developers to tailor their operating system to their specific needs.
Command-line interface: Linux is typically used through a command-line interface, which provides developers with powerful tools for managing their systems.

Linux Distributions (Distros / Flavors)

There are many different Linux distributions available, each with its own set of features and characteristics. Some of the most popular distributions among developers include:

Ubuntu: A Debian-based distribution that is known for its ease of use and broad community support.
Fedora: A community-driven distribution that is known for its cutting-edge software and frequent updates.
CentOS: A distribution based on the Red Hat Enterprise Linux codebase that is known for its stability and long-term support.
Arch Linux: A distribution that is highly customizable and allows developers to build their operating system from the ground up.

Which Linux Distro is Right for You?

Choosing the right Linux distribution is an important decision for developers. The best distribution for you will depend on your specific needs and requirements. For most developers, Ubuntu or Fedora are excellent choices due to their broad community support and ease of use.

Linux Basics for Developers

In this section, we will introduce you to some of the basic concepts that you need to know to be able to use Linux effectively as a developer. We will cover topics such as file permissions, user management, and the command-line interface.

File Permissions

In Linux, file permissions are used to control who can access files and what they can do with them. There are three types of permissions: read, write, and execute. These permissions can be set for three different groups: the owner of the file, the group that the file belongs to, and all other users.

User Management

In Linux, user management is done through the command-line interface. Administrators can create, modify, and delete users using various commands. It is important to understand how user management works in Linux to be able to control access to your development environment.

The CLI (Command-Line Interface)

The CLI or command-line interface is a powerful tool for managing Linux systems. It allows developers to execute commands and scripts, navigate the file system, and perform various other tasks.

It can be intimidating at first, but with practice, you can become proficient and even prefer it over graphical user interfaces.

Basic Commands

Here are some basic Linux commands that every developer should know:

cd – change directory
ls – list directory contents
mkdir – make directory
rm – remove file or directory
cp – copy file or directory
mv – move or rename file or directory
chmod – change file or directory permissions

Using Pipes

Pipes allow you to redirect the output of one command to another command as input. This can be incredibly useful for manipulating and processing data.

For example, you can use the ls command to list the contents of a directory, and then use the grep command to filter the results based on a specific pattern. The following command will list all files in the current directory that contain the word “example”:

ls | grep example

Environment Variables

Environment variables are a way to store and retrieve information that can be used by programs running on your system. They can be used to store configuration information, set paths to files, and more.

To view a list of all environment variables on your system, use the following command:

printenv

You can also set and modify environment variables using the export command. For example, to set the PATH variable to include a new directory, you can use the following command:

export PATH=$PATH:/path/to/new/directory

Package Management

One of the key features of Linux is the use of package managers, which are software tools that allow you to easily install, update, and manage software packages on your system. Package managers are essential for developers who need to quickly install and configure the software they need for their development work.

apt-get

The apt-get command is one of the most popular and widely used package managers on Linux. It allows you to install, update, and remove packages from the official Ubuntu repositories as well as third-party repositories.

To install a package using apt-get, simply run the following command:

sudo apt-get install <package-name>

For example, to install Node.js, you can use the following command:

sudo apt-get install nodejs

snap

Snap is a new package format and package manager that is gaining popularity on Linux. It offers a number of advantages over traditional package managers, including support for sandboxing and automatic updates.

To install a package using snap, simply run the following command:

sudo snap install <package-name>

For example, to install Visual Studio Code, you can use the following command:

sudo snap install code --classic

Other Package Managers

There are many other package managers available on Linux, including yum, dnf, and pacman. The package manager you choose will depend on the Linux distribution you are using and your personal preferences.

Text Editors

Text editors are essential tools for developers, and Linux offers a variety of options to choose from. Here are some of the most popular text editors used by developers on Linux:

Vim

Vim is a powerful and highly configurable text editor that is popular among developers who prefer to work in the command line. It offers a wide range of features and can be customized with plugins and scripts.

Emacs

Emacs is another popular text editor that is highly customizable and extensible

Conclusion

In this blog post, we covered the basics of Linux and how it can be useful for developers. We started by discussing the history of Linux and how it evolved to become the most popular operating system for servers and other platforms.

We then covered the various features of Linux that make it a great choice for developers, including its flexibility, security, and scalability. We also discussed some of the key tools that are available in Linux for developers, such as the terminal, package managers, and text editors.

We then went through a step-by-step guide on how to install Linux on a computer, including creating a bootable USB drive and selecting the right distribution for your needs. We also covered some tips on how to troubleshoot common issues that you might encounter during the installation process.

Finally, we explored some advanced topics in Linux that can be useful for developers, such as virtualization, containerization, and cloud computing. We also discussed some of the key differences between Linux and other operating systems, such as Windows and macOS.

Overall, Linux is a powerful and versatile operating system that can be an excellent choice for developers. Whether you are building web applications, mobile apps, or desktop software, Linux has the tools and features that you need to get the job done.

Unlocking the Power of AWS Notifications and Email Services for Your Business

Khalid ElGazzar — Thu, 09 Nov 2023 12:47:00 +0000

I. Introduction

As more businesses move their applications to the cloud, the need for reliable and scalable email and notification services becomes increasingly important. Amazon Web Services (AWS) offers a range of services that can be used for messaging, notifications, and email, each with unique features and capabilities. In this blog post, we’ll explore some of the key AWS services that utilize email or notifications, categorized by their primary use case: developer tools, business tools, and collaboration tools. Note that All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

II. Developer Tools

II.1. Amazon Simple Notification Service (SNS)

Amazon SNS is a fully managed messaging service that can be used for both application-to-application (A2A) and application-to-person (A2P) communication. SNS allows you to publish messages to topics, which can be delivered to multiple subscribers or endpoints simultaneously. This makes it easy to send notifications to mobile devices, email, SMS, or other endpoints based on events or triggers.

II.2. AWS Lambda

AWS Lambda is a serverless compute service that can be used to trigger notifications or send emails based on events. With Lambda, you can create functions that automatically execute in response to events from AWS services, such as Amazon S3 or DynamoDB. This allows you to create workflows that trigger notifications or emails based on changes to your data or applications.

II.3. Amazon Simple Queue Service (SQS)

Amazon SQS is a fully managed message queuing service that can be used to send notifications between different applications or components. SQS allows you to decouple components in a microservices architecture, and enables asynchronous processing of job requests. You can also use SQS to build fault-tolerant applications, as it ensures that messages are processed at least once and in the order they are received.

II.4. Amazon EventBridge

Amazon EventBridge is a serverless event bus service that can be used to connect different applications and services, including triggering notifications or sending emails based on events. EventBridge allows you to create rules that match events and route them to one or more targets, such as an SNS topic, Lambda function, or Step Function. This makes it easy to build event-driven architectures and automate workflows.

III. Business Tools

III.1. Amazon Simple Email Service (SES)

Amazon SES is a flexible and highly scalable email service for sending and receiving email. With SES, you can send transactional emails, marketing emails, and other types of messages to your customers. SES provides a simple API and integrates with AWS services, such as Amazon S3 and Lambda, making it easy to send emails based on events or triggers. SES also includes advanced features, such as email feedback loops, spam filtering, and reputation monitoring.

III.2. Amazon Pinpoint

Amazon Pinpoint is a fully-fledged marketing solution from AWS. Think of it as AWeber or MailChimp on steroids. It is a managed service for sending targeted messages to your customers across multiple messaging channels, including email, SMS, and push notifications. Pinpoint allows you to segment your customers based on user behavior, preferences, and demographics, and send personalized messages that drive engagement and conversions. Pinpoint also includes advanced features, such as A/B testing, analytics, and message orchestration.

III.3. Amazon CloudWatch

Amazon CloudWatch is a monitoring and management service for AWS resources and applications, which can send notifications via email or other methods when certain events occur. CloudWatch allows you to collect and track metrics, collect and monitor log files, and set alarms based on thresholds. You can use CloudWatch to monitor the performance of your applications, detect anomalies, and troubleshoot issues.

III.4. AWS Step Functions

AWS Step Functions is a serverless visual workflow service that can be used to automate the flow of data between different AWS services, including triggering notifications or sending emails as part of the workflow. With Step Functions, you can create visual workflows that coordinate the components of your application, such as AWS Lambda functions, SQS queues, or SNS topics. You can also use Step Functions to build complex state machines that model the behavior of your application and handle errors

IV. Collaboration Tools

IV.1. Amazon Chime

Amazon Chime is a collaboration service that allows teams to communicate and collaborate securely, using chat, audio, and video conferencing. Think of Amazon Chime as Zoom on Steriods. Chime provides a range of features, such as screen sharing, file sharing, and virtual meeting rooms, making it easy for teams to collaborate in real-time. Chime also integrates with other AWS services, such as S3 and Lambda, enabling you to create custom workflows and automate processes.

IV.2. Amazon WorkMail

Amazon WorkMail is a secure and managed business email and calendar service that is fully compatible with Microsoft Outlook. WorkMail provides a range of features, such as mobile device management, encryption, and spam protection, making it easy to manage email and calendar across different devices and platforms. WorkMail also integrates with other AWS services, such as Lambda, enabling you to automate tasks and workflows.

V. Conclusion

AWS offers a range of services that can be used for messaging, notifications, and email, each with unique features and capabilities. These services can be categorized by their primary use case, including developer tools, business tools, and collaboration tools. By leveraging these services, businesses can build reliable, scalable, and secure applications that meet the needs of their customers and teams. Remember to use SEO best practices when writing your blog post to ensure that it reaches the right audience and provides value to readers. Lastly, All IP rights to this blog post are reserved. Since I have been facing several content piracy cases lately, this blog post has ONLY been published on the Software, Architecture, and Cloud blog - SWAC.blog and canonically to dev.to only. If you are reading it elsewhere, then please let us know.

For more articles about AWS & how to begin your AWS journey, visit AWS section on the Software, Architecture & Cloud blog - SWAC.blog