<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Core Compute on 🏠</title><link>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/</link><description>Recent content in Core Compute on 🏠</description><generator>Hugo</generator><language>en-us</language><atom:link href="https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/index.xml" rel="self" type="application/rss+xml"/><item><title>5. EC2</title><link>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/ec2/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/ec2/</guid><description>&lt;h2 id="ec2-elastic-compute-cloud"&gt;EC2 (Elastic Compute Cloud)&lt;a class="anchor" href="#ec2-elastic-compute-cloud"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Amazon EC2 (Elastic Compute Cloud) &lt;a href="https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/concepts.html"&gt;🔗&lt;/a&gt; is AWS&amp;rsquo;s service for renting virtual servers in the cloud. Before managed compute services like Lambda existed, every application needed a server — EC2 is that server, virtualized and billed by the second. Understanding EC2 gives you the mental model for what higher-level services like Lambda are actually abstracting away: OS management, patching, capacity planning, and runtime configuration.&lt;/p&gt;
&lt;p&gt;For the DVA-C02 exam, EC2 is foundational context rather than the primary focus. That said, several EC2 concepts — security groups, IAM roles on instances, and purchasing options — appear regularly in scenario questions.&lt;/p&gt;</description></item><item><title>6. Lambda</title><link>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/lambda/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/lambda/</guid><description>&lt;h2 id="aws-lambda"&gt;AWS Lambda&lt;a class="anchor" href="#aws-lambda"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;Modern applications often need to run small, discrete pieces of logic in response to events — a user uploads a file, a message arrives in a queue, an HTTP request hits an API. Traditionally, this meant provisioning and maintaining servers to host that logic, even when it was idle. AWS Lambda eliminates that overhead entirely: you upload your code, define what triggers it, and AWS handles everything else — infrastructure, scaling, patching, and availability. You pay only for the compute time your code actually consumes, billed in 1ms increments. This model is called &lt;strong&gt;serverless compute&lt;/strong&gt;, and Lambda is its cornerstone on AWS. &lt;a href="https://docs.aws.amazon.com/lambda/latest/dg/welcome.html"&gt;🔗&lt;/a&gt;&lt;/p&gt;</description></item><item><title>7. ASG</title><link>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/asg/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/asg/</guid><description>&lt;h2 id="auto-scaling-groups-asg"&gt;Auto Scaling Groups (ASG)&lt;a class="anchor" href="#auto-scaling-groups-asg"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;An Auto Scaling Group is an EC2 fleet management service that automatically adjusts the number of running instances based on demand, health, or a schedule. The core problem it solves is twofold: you don&amp;rsquo;t want to over-provision (wasting money on idle capacity), and you don&amp;rsquo;t want to under-provision (degrading user experience under load). ASG handles both by adding instances when demand rises and terminating them when it drops — all without manual intervention. &lt;a href="https://docs.aws.amazon.com/autoscaling/ec2/userguide/what-is-amazon-ec2-auto-scaling.html"&gt;🔗&lt;/a&gt;&lt;/p&gt;</description></item><item><title>8. ELB</title><link>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/elb/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://tofl.github.io/docs/3-core-compute-ec2-lambda-asg-elb/elb/</guid><description>&lt;h2 id="elastic-load-balancing-elb"&gt;Elastic Load Balancing (ELB)&lt;a class="anchor" href="#elastic-load-balancing-elb"&gt;#&lt;/a&gt;&lt;/h2&gt;
&lt;p&gt;When you run multiple EC2 instances (or Lambda functions, containers, or IP targets) to serve user traffic, you need something to sit in front of them and distribute incoming requests evenly, route them intelligently, and stop sending traffic to unhealthy targets. That is exactly what Elastic Load Balancing does. ELB is a managed service — AWS handles provisioning, scaling, and availability of the load balancer itself, so you only configure behavior. &lt;a href="https://docs.aws.amazon.com/elasticloadbalancing/latest/userguide/what-is-load-balancing.html"&gt;🔗&lt;/a&gt;&lt;/p&gt;</description></item></channel></rss>