Posts

Global Service used to manage multiple AWS accounts centrally. The main account is called the Master Account, and other linked accounts are Child Accounts. Key Benefits Consolidated Billing All accounts share a single payment method managed by the master account. You receive one combined bill for all linked accounts. Pricing Benefits Aggregated usage provides volume discounts for services like EC2 and S3 across all accounts. Reserved Instances (RIs) are shared among accounts for maximum savings. Automation API support to automate AWS account creation (useful for sandbox or departmental accounts). Service Control Policies (SCPs) Used to restrict account privileges. Common exam topic. Multi-Account Strategy Why Use Multiple Accounts Easier management and security isolation. Organize by: Department (Sales, Finance, HR) Environment (Dev, Test, Prod) Project (Project-1, Project-2, etc.) Regulatory requirements (compliance-based isolation) Benefits Separate service limits per account. Improved resource isolation (different VPCs per account). Dedicated logging accounts for central log management. Best Practices Apply tagging standards across accounts for billing. Enable CloudTrail and CloudWatch Logs in all accounts. Send logs to a central S3 or logging account for visibility and compliance. Organizational Units (OUs) Used to group related accounts within an organization. Structure Example: Root OU (contains Master Account) Dev OU, Prod OU, etc. Nested OUs possible (e.g., Prod → Finance OU, HR OU). Allows hierarchical policy management using SCPs. Service Control Policies (SCPs) Manage permissions centrally across accounts. Whitelist or blacklist IAM actions at OU or account level. Do not apply to the Master Account. Behavior Affect users and roles (including root users) within child accounts. Do not affect service-linked roles (used internally by AWS services). SCPs must have explicit “Allow” statements; otherwise, actions are denied by default. Use Cases Restrict access to specific AWS services (e.g., deny EMR in production). Enforce compliance (e.g., disable non-PCI-compliant services). Examples Blacklist example: 1 2 3 4 5 { "Effect": "Deny", "Action": "dynamodb:*", "Resource": "*" } Denies all DynamoDB actions. Whitelist example: 1 2 3 4 5 { "Effect": "Allow", "Action": ["ec2:*", "cloudwatch:*"], "Resource": "*" } Allows only EC2 and CloudWatch actions; all others denied. Key Exam Points AWS Organizations = Global Service for multi-account management. Master account pays bills via Consolidated Billing. Aggregated usage and shared RIs reduce costs. SCPs manage account-level permissions, not IAM roles directly. SCPs don’t apply to the master account or service-linked roles. Use CloudTrail and centralized logging for auditing all accounts. AWS Organizations – Consolidated Billing Purpose Consolidated Billing in AWS Organizations allows centralized payment management and shared cost benefits across multiple AWS accounts under one organization. ...

AWS STS (Security Token Service) Overview AWS STS is a core AWS service used to create temporary, limited-privilege credentials for accessing AWS resources. These credentials are short-term and consist of: Access Key ID Secret Access Key Session Token (time-limited) Purpose Provides temporary security credentials instead of long-term IAM user credentials. Commonly used when: Access must be limited in time or scope. Cross-account access is required. Federated users (from external identity systems) need AWS access. Applications or EC2 instances assume roles to access AWS services securely. How It Works A user or service assumes a role using an STS API call (for example, AssumeRole). STS returns temporary credentials (access key, secret key, session token). These credentials are used to access AWS resources as defined by the role’s permissions. Credentials expire automatically after a specified duration. Key Use Cases Identity Federation Users managed in an external system (e.g., corporate directory, SSO provider) can obtain STS tokens to access AWS resources. Allows integration with systems like Active Directory, Google Workspace, or SAML providers. Cross-Account Role Access Allows an IAM user in one AWS account to assume a role in another account. Facilitates secure sharing of resources between AWS accounts. EC2 Instance Roles EC2 instances can assume IAM roles automatically. AWS refreshes credentials in the background using STS to maintain temporary access tokens. ...

Amazon WorkSpaces (Managed Desktop as a Service – DaaS) Definition Amazon WorkSpaces is a fully managed Desktop-as-a-Service (DaaS) offering from AWS. Allows users to provision Windows or Linux virtual desktops in the AWS Cloud. Purpose Replaces on-premises Virtual Desktop Infrastructure (VDI) solutions. Provides a secure, scalable, and cost-effective way to deliver desktop environments to users. Key Features Managed DaaS: AWS manages the infrastructure, storage, and desktop provisioning. Platform Support: Supports both Windows and Linux desktops. Security: Integrated with AWS KMS for encryption and can operate within a VPC for network isolation. Pay-as-you-go Pricing: Pay only for the desktops you use (hourly or monthly). Remote Access: Users can securely connect from anywhere (home, office, etc.) to their cloud desktop. Use Case Example A company wants to give employees secure remote access to corporate resources without managing physical laptops or VDI infrastructure. IT admins provision WorkSpaces for employees to access internal systems securely via the cloud. Performance and Latency Minimize latency by deploying WorkSpaces in regions closest to end users. Example: U.S. office → Deploy WorkSpaces in a U.S. region. European office → Deploy WorkSpaces in a European region. General Rule: For any AWS application, deploy resources close to users to improve performance and reduce latency. Exam Tips If you see keywords like: “Managed desktop in the cloud” “Virtual Desktop Infrastructure (VDI) replacement” “Secure Windows/Linux desktops for remote users” Remember: WorkSpaces = Managed Virtual Desktops in AWS Cloud Amazon AppStream 2.0 Definition Amazon AppStream 2.0 is a fully managed desktop application streaming service. It allows users to stream individual desktop applications to any device through a web browser, without installing or managing infrastructure. Purpose Designed for application delivery, not full desktops. Lets users access software like Blender, Eclipse, OpenOffice, Firefox, etc., directly in a browser. Removes the need for local installations or on-premises servers. Key Features Application-Focused: Streams specific apps, not entire desktops. Browser-Based Access: Users access apps via any device with a web browser. No Infrastructure Setup: AWS handles scaling, maintenance, and provisioning. Customizable Performance: Configure instance types per application (e.g., more CPU/GPU for Photoshop or Blender). Scalable and Secure: Easily supports multiple users, securely managed through AWS. Comparison: AppStream 2.0 vs WorkSpaces Feature Amazon WorkSpaces Amazon AppStream 2.0 Type Desktop-as-a-Service (DaaS) Application Streaming Service Purpose Provides full Windows/Linux desktops Streams single applications Access Via remote desktop client Via web browser Use Case Virtual desktop for users Delivering apps without local installs Example Full desktop for remote employees Running Blender or Photoshop in browser Use Case Example An organization wants employees or students to use desktop applications remotely (e.g., 3D modeling or coding tools) without installing them locally. They use AppStream 2.0 to stream these applications through a web browser on any device. Exam Tips Keywords like “stream applications,” “run desktop apps in a browser,” or “no full desktop environment” point to Amazon AppStream 2.0. Remember: WorkSpaces = Full virtual desktop (VDI) AppStream 2.0 = Application streaming to browsers IoT Core Overview AWS IoT Core lets connected devices (sensors, appliances, etc.) communicate securely with AWS services. Supports MQTT, HTTP, and WebSockets for messaging. Enables real-time data ingestion, device management, and rule-based data routing. Example: Sending temperature data from IoT sensors to AWS Lambda or DynamoDB. Elastic Transcoder Overview Amazon Elastic Transcoder converts (transcodes) media files from one format to another for playback on various devices. Fully managed and scalable. Example: Convert uploaded videos in S3 to mobile-friendly MP4 versions. (Note: AWS MediaConvert is the modern replacement, but Elastic Transcoder still appears in CCP-level content.) AppSync AWS AppSync is a managed GraphQL API service that allows applications to query and update data in real time across multiple data sources (DynamoDB, Lambda, RDS, etc.). Automatically handles data synchronization and offline access. Example: A mobile app fetching user data through a single GraphQL endpoint. Amplify AWS Amplify helps developers build, deploy, and host full-stack web and mobile applications quickly. Integrates with backend services like AppSync, Cognito, S3, and Lambda. Example: Rapidly building a React web app with AWS backend resources automatically configured. AWS Infrastructure Composer AWS Infrastructure Composer is a visual tool for designing and deploying AWS architectures using drag-and-drop components. Generates Infrastructure as Code (IaC) templates (CloudFormation or CDK). Speeds up architecture prototyping and deployment. Device Farm Overview AWS Device Farm is an app testing service that lets you test Android, iOS, and web apps on real physical devices in the AWS Cloud. Identifies issues across devices and operating systems. Example: Automatically testing a mobile app on multiple phone models. AWS Backup Overview AWS Backup provides centralized, automated backup management across AWS services (EBS, RDS, DynamoDB, EFS, etc.). Supports backup policies, retention rules, and cross-region backup. Ensures data protection and compliance. Disaster Recovery Strategies AWS defines several Disaster Recovery (DR) strategies, based on cost vs recovery speed: ...

Shell Scripting A shell script is an executable text file that contains shells commands and other specific programming structures. What is a Shell? A shell is a program that acts as a bridge(interface) between you(user) and the operating system(kernel). It takes commands you type, sends them to the operating system kernel, and then shows you the output. Think of it as a command interpreter. Tip: Use this command to check your current shell ...

Shell Expansion In Section we are going to learn about Shell Expansion, How bash perform the Shell Expansion What is Expansion? When you type a command and press Enter, the shell performs several steps before execution. After tokenization, Command Identification (splitting the command into words/tokens) and parsing, the shell performs expansions. Expansion = the process of replacing symbols, variables, or patterns with their actual values. Example: 1 echo $HOME Here $HOME is expanded into your actual home directory path (like /home/ahmad). ...

Shell Operation in Bash The shell (e.g., bash) follows a multi-step process to interpret and execute commands. Each command goes through reading, breaking down, expanding, redirecting, and finally execution. Steps of Command Processing Read Input From terminal (interactive use) or file/script. Reads line by line. Tokenization (Lexical Analysis) Breaks input into words and operators. Follows specific syntax rules. Alias expansion happens at this stage. Parsing / Command Identification Tokens are recognized as: Simple commands (like ls -l) Compound commands (like if, for, pipelines, etc.) Shell Expansions (performed in order): Brace expansion → {a,b,c} → expands to a b c Tilde expansion → ~ → expands to home directory Parameter & variable expansion → $VAR Command substitution → `command` or $(command) Arithmetic expansion → $((2+3)) → 5 Process substitution → <(command) or >(command) Word splitting → breaks expanded words into fields Filename expansion (globbing) → *.txt → matches files Quote Removal Removes " ' and ` while preserving meaning. Redirections Handles input/output redirection, e.g. > >> < 2>&1. Execution The command is executed. If required, the shell waits for the command to finish. Exit status ($?) is collected. Key Points Tokenization is the first transformation stage. Expansions are ordered; each depends on the result of the previous. Redirection happens before execution. Exit status is important for scripting (conditional logic). Shell Tokenization Definition: The process of breaking input into tokens (smallest meaningful units). A token = sequence of characters treated as a single unit by the shell. How Tokenization Works Input Source From terminal or a file (script). Meta Characters Special unquoted characters that separate words. List of meta characters: Space ( ) Tab (\t) Newline (\n) | & ; ( ) < > Types of Tokens Words: tokens without unquoted meta characters. Operators: tokens containing at least one unquoted meta character. Note: If quoted, they lose their special meaning. ...

Variables in Shell Scripting Variables are placeholders to store data (strings, numbers, paths, etc). They don’t require explicit declaration type (untyped). Stored as strings by default in bash/sh. Creating Variables 1 2 name="Ahmad" age=20 Note: ⚠️ No spaces around =. Using Variables 1 2 echo $name echo "I am $age years old" $var → expands value(referencing the value of a variable) ${var} → safer form, avoids ambiguity, and useful for appending 1 2 file="report" echo "${file}_2025.txt" # report_2025.txt Types of Variables User-defined variables (you create) city="Multan" Environment variables (system-wide, inherited by child processes) 1 2 echo $PATH export MYVAR="hello" Best Practices ...

What is RMPC? RMPC is a TUI (terminal UI) client for MPD. It does not do audio output itself, it just sends commands to MPD. (mierak.github.io ) So the setup has two parts: Install & configure MPD (the server/daemon that plays music) Install & configure RMPC to connect to MPD Step 1: Install MPD + required clients/tools On Arch-like systems: ...

React.js is a JavaScript library for building user interfaces. Developed by Facebook (now Meta) in 2013. It is component-based, declarative, and allows for efficient UI updates. Key Features of React Component-Based Architecture: UI is built using reusable components. Virtual DOM: Updates only the changed parts, making React fast. Unidirectional Data Flow: Props and state maintain a predictable data structure. JSX (JavaScript XML): A syntax extension that lets you write HTML inside JavaScript. Hooks: Allow functional components to have state and other features. Mutable vs Immutable Mutable (Changeable) Mutable data types can be changed after creation. Example: Objects & Arrays are mutable. 1 2 3 let arr = [1, 2, 3]; arr.push(4); // Modifies the original array console.log(arr); // [1, 2, 3, 4] Immutable (Unchangeable) Immutable data cannot be changed directly. Instead, you create a new copy. Example: Strings & Numbers are immutable. 1 2 3 let str = "Hello"; str[0] = "M"; // This won't change the string console.log(str); // "Hello" Example of immutable object handling (creating a new object instead of modifying the original): ...

How anyone can be more effective with less effort by learning how to identify and leverage the 80/20 principle–the well-known, unpublicized secret that 80 percent of all our results in business and in life stem from a mere 20 percent of our efforts. The 80/20 principle is one of the great secrets of highly effective people and organizations. Did you know, for example, that 20 percent of customers account for 80 percent of revenues? That 20 percent of our time accounts for 80 percent of the work we accomplish? The 80/20 Principle shows how we can achieve much more with much less effort, time, and resources, simply by identifying and focusing our efforts on the 20 percent t at really counts. Although the 80/20 principle has long influenced today’s business world, author Richard Koch reveals how the principl works and shows how we can use it in a systematic and practical way to vastly increase our effectiveness, and improve our careers and o r companies. ...