More Related Content
Similar to AWS compute Services
![Devfest Harare 2025 Slides [GDG Harare] - Combined Slide Deck](https://cdn.slidesharecdn.com/ss_thumbnails/ilovepdfmerged12-251029161756-3b829161-thumbnail.jpg?width=640&height=640&fit=bounds)
AWS compute Services
- 1. Compute Services EC2 Autoscaling Elastic load balancer ElasticBeanstalk AWS Lambda Nagesh Ramamoorthy
- 2. EC2 • EC2 Features •Amazon Machine Images • Instances • Monitoring • Networking and Security • Storage • Placement Groups • T2 instances • Status Checks
- 3. EC2 Features • Virtualcomputing environments, known as instances • Preconfigured templates for your instances, known as Amazon Machine Images (AMIs), that package the bits you need for your server (including the operating system and additional software) • Various configurations of CPU, memory, storage, and networking capacity for your instances, known as instance types • Secure login information for your instances using key pairs (AWS stores the public key, and you store the private key in a secure place) • Storage volumes for temporary data that's deleted when you stop or terminate your instance, known as instance store volumes • Metadata, known as tags, that you can create and assign to your Amazon EC2 resources
- 4. EC2 features (Contd..) •Persistent storage volumes for your data using Amazon Elastic Block Store (Amazon EBS), known as Amazon EBS volumes • Multiple physical locations for your resources, such as instances and Amazon EBS volumes, known as regions and Availability Zones • A firewall that enables you to specify the protocols, ports, and source IP ranges that can reach your instances using security groups • Static IPv4 addresses for dynamic cloud computing, known as Elastic IP addresses • Virtual networks you can create that are logically isolated from the rest of the AWS cloud, and that you can optionally connect to your own network, known as virtual private clouds (VPCs)
- 5. Amazon Machine Images ( AMI) AnAMI provides the information required to launch an instance, which is a virtual server in the cloud. You must specify a source AMI when you launch an instance An AMI includes the following: A template for the root volume for the instance (for ex, an operating system, an application server, and applications) Launch permissions that control which AWS accounts can use the AMI to launch instances A block device mapping that specifies the volumes to attach to the instance when it's launched
- 6. AMI Life cycle After you create and register an AMI, you can use it to launch new instances You can also launch instances from an AMI if the AMI owner grants you launch permissions. You can copy an AMI within the same region or to different regions. When you no longer require an AMI, you can deregister it.
- 7. AMI Types • Region(see Regions and Availability Zones) • Operating system • Architecture (32-bit or 64-bit) • Launch Permissions • Storage for the Root Device You can select an AMI to use based on the following characteristics:
- 8. Launch Permissions Theowner of an AMI determines its availability by specifying launch permissions. • Launch permissions fall into the following categories: • The owner grants launch permissions to all AWS accounts Public • The owner grants launch permissions to specific AWS accounts Explicit • The owner has implicit launch permissions for an AMI. Implicit
- 9. EC2 Root Device Volume When youlaunch an instance, the root device volume contains the image used to boot the instance. You can choose between AMIs backed by Amazon EC2 instance store and AMIs backed by Amazon EBS. AWS recommend that you use AMIs backed by Amazon EBS, because they launch faster and use persistent storage.
- 10. Instance Store BackedInstances: • Instances that use instance stores for the root device automatically have one or more instance store volumes available, with one volume serving as the root device volume • The data in instance stores is deleted when the instance is terminated or if it fails (such as if an underlying drive has issues). • Instance store-backed instances do not support the Stop action • After an instance store-backed instance fails or terminates, it cannot be restored. • If you plan to use Amazon EC2 instance store-backed instances o distribute the data on your instance stores across multiple Availability Zones o back up critical data on your instance store volumes to persistent storage on a regular basis
- 11. EBS Backed Instances: •Instances that use Amazon EBS for the root device automatically have an Amazon EBS volume attached • An Amazon EBS-backed instance can be stopped and later restarted without affecting data stored in the attached volumes. • There are various instance and volume-related tasks you can do when an Amazon EBS-backed instance is in a stopped state. For example, you can modify the properties of the instance, you can change the size of your instance or update the kernel it is using, or you can attach your root volume to a different running instance for debugging or any other purpose
- 12. Instance Types When you launchan instance, the instance type that you specify determines the hardware of the host computer used for your instance. Each instance type offers different compute, memory, and storage capabilities and are grouped in instance families based on these capabilities Amazon EC2 dedicates some resources of the host computer, such as CPU, memory, and instance storage, to a particular instance. Amazon EC2 shares other resources of the host computer, such as the network and the disk subsystem, among instances.
- 13. Available Instance Types General Purpose :T2 , M5 Compute Optimised : C5 Memory Optimized : R4, X1 Storage Optimised: D2, H1, I3 Accelerated Computing: F1, G3, P3
- 14.
- 15. Instance Purchasing Options On-DemandInstances – Pay, by the second, for the instances that you launch. Reserved Instances – Purchase, at a significant discount, instances that are always available, for a term from one to three years Scheduled Instances – Purchase instances that are always available on the specified recurring schedule, for a one-year term. Spot Instances – Request unused EC2 instances, which can lower your Amazon EC2 costs significantly. Dedicated Hosts – Pay for a physical host that is fully dedicated to running your instances, and bring your existing per-socket, per-core, or per-VM software licenses to reduce costs. Dedicated Instances – Pay, by the hour, for instances that run on single-tenant hardware.
- 16. Security Groups A security groupacts as a virtual firewall that controls the traffic for one or more instances. When you launch an instance, you associate one or more security groups with the instance. You add rules to each security group that allow traffic to or from its associated instances When you specify a security group as the source or destination for a rule, the rule affects all instances associated with the security group
- 17. SG Rules • Foreach rule, you specify the following: o Protocol: The protocol to allow. The most common protocols are 6 (TCP) 17 (UDP), and 1 (ICMP). o Port range : For TCP, UDP, or a custom protocol, the range of ports to allow. You can specify a single port number (for example, 22), or range of port numbers o Source or destination: The source (inbound rules) or destination (outbound rules) for the traffic. o (Optional) Description: You can add a description for the rule; for example, to help you identify it later.
- 18. SG Rules Characteristics Bydefault, security groups allow all outbound traffic. You can't change the outbound rules for an EC2-Classic security group. Security group rules are always permissive; you can't create rules that deny access. Security groups are stateful — if you send a request from your instance, the response traffic for that request is allowed to flow in regardless of inbound security group rules. You can add and remove rules at any time. Your changes are automatically applied to the instances associated with the security group after a short period When you associate multiple security groups with an instance, the rules from each security group are effectively aggregated to create one set of rules to determine whether to allow access
- 19. Instance IP addressing Every instance is assigned with IP addresses and IPv4 DNS hostnames by AWS using DHCP Amazon EC2 and Amazon VPC support both the IPv4 and IPv6 addressing protocols By default, Amazon EC2 and Amazon VPC use the IPv4 addressing protocol; you can't disable this behavior. Types Of IP addresses available for EC2: o Private IP4 addresses o Public V4 addresses o Elastic IP addresses o IPV6 addresses
- 20. Private IPV4 addresses A privateIPv4 address is an IP address that's not reachable over the Internet. You can use private IPv4 addresses for communication between instances in the same network When you launch an instance, AWS allocate a primary private IPv4 address for the instance from the subnet Each instance is also given an internal DNS hostname that resolves to the primary private IPv4 address A private IPv4 address remains associated with the network interface when the instance is stopped and restarted, and is released when the instance is terminated
- 21. Public IPV4 addresses A publicIP address is an IPv4 address that's reachable from the Internet. You can use public addresses for communication between your instances and the Internet. Each instance that receives a public IP address is also given an external DNS hostname A public IP address is assigned to your instance from Amazon's pool of public IPv4 addresses, and is not associated with your AWS account You cannot manually associate or disassociate a public IP address from your instance
- 22. Public IP Behavior •You can control whether your instance in a VPC receives a public IP address by doing the following: • Modifying the public IP addressing attribute of your subnet • Enabling or disabling the public IP addressing feature during launch, which overrides the subnet's public IP addressing attribute • In certain cases, AWS release the public IP address from your instance, or assign it a new one: • when an instance is stopped or terminated. Your stopped instance receives a new public IP address when it's restarted. • when you associate an Elastic IP address with your instance, or when you associate an Elastic IP address with the primary network interface (eth0) of your instance in a VPC.
- 23. Elastic IP addresses AnElastic IP address is a static IPv4 address designed for dynamic cloud computing An Elastic IP address is associated with your AWS account. With an Elastic IP address, you can mask the failure of an instance or software by rapidly remapping the address to another instance in your account An Elastic IP address is a public IPv4 address, which is reachable from the internet By default, all AWS accounts are limited to five (5) Elastic IP addresses per region, because public (IPv4) internet addresses are a scarce public resource
- 24. Elastic IP characteristics Touse an Elastic IP address, you first allocate one to your account, and then associate it with your instance or a network interface You can disassociate an Elastic IP address from a resource, and reassociate it with a different resource A disassociated Elastic IP address remains allocated to your account until you explicitly release it AWS impose a small hourly charge if an Elastic IP address is not associated with a running instance, or if it is associated with a stopped instance or an unattached network interface While your instance is running, you are not charged for one Elastic IP address associated with the instance, but you are charged for any additional Elastic IP addresses associated with the instance An Elastic IP address is for use in a specific region only
- 25. c5.large Instance family Instance generation Instancesize Instance naming
- 26. T2 Instances • T2instances are designed to provide a baseline level of CPU performance with the ability to burst to a higher level when required by your workload • There are two types of T2 instance offerings : 1 . T2 standard and 2. T2 Unlimited. • T2 Standard is the default configuration; if you do not enable T2 Unlimited, your T2 instance launches as Standard. • The baseline performance and ability to burst are governed by CPU credits • A T2 Standard instance receives two types of CPU credits: earned credits and launch credits • When a T2 Standard instance is in a running state, it continuously earns a set rate of earned credits per hour • At start, it has not yet earned credits for a good startup experience; therefore, to provide a good startup experience, it receives launch credits at start • The number of accrued launch credits and accrued earned credits is tracked by the CloudWatch metric CPUCreditBalance. • One CPU credit is equal to one vCPU running at 100% utilization for one minute. • T2 Standard instances get 30 launch credits per vCPU at launch or start. For example, a t2.micro has one vCPU and gets 30 launch credits, while a t2.xlarge has four vCPUs and gets 120 launch credits
- 27. CPU Credit Balance •If a T2 instance uses fewer CPU resources than is required for baseline performance , the unspent CPU credits are accrued in the CPU credit balance • If a T2 instance needs to burst above the baseline performance level, it spends the accrued credits • The number of CPU credits earned per hour is determined by the instance size • While earned credits never expire on a running instance, there is a limit to the number of earned credits an instance can accrue • Once the limit is reached, any new credits that are earned are discarded • CPU credits on a running instance do not expire. However, the CPU credit balance does not persist between instance stops and starts
- 28. T2 Unlimited • T2Unlimited is a configuration option for T2 instances that can be set at launch, or enabled at any time for a running or stopped T2 instance. • T2 Unlimited instances can burst above the baseline for as long as required • This enables you to enjoy the low T2 instance hourly price, and ensures that your instances are never held to the baseline performance. • If a T2 Unlimited instance depletes its CPU credit balance, it can spend surplus credits to burst beyond the baseline • If the average CPU utilization of an instance is at or below the baseline, the instance incurs no additional charges, Because an instance earns a maximum number of credits in a 24-hour period • However, if CPU utilization stays above the baseline, the instance cannot earn enough credits to pay down the surplus credits it has spent. • The surplus credits that are not paid down are charged at a flat additional rate per vCPU-hour • T2 Unlimited instances do not receive launch credits.
- 29. Changing Instance Type Youcan change the size of your instance to fit the right workload or take advantages of features of new generation instances. If the root device for your instance is an EBS volume, you can change the size of the instance simply by changing its instance type, which is known as resizing it. If the root device for your instance is an instance store volume, you must migrate your application to a new instance with the instance type that you need You can resize an instance only if its current instance type and the new instance type that you want are compatible with features like virtualization type , kernel type etc. We can take Instance-store backed AMI in order to migrate instaces with instance store root volumes.
- 30. Status checks • AmazonEC2 performs automated checks on every running EC2 instance to identify hardware and software issues. • This data augments the utilization metrics that Amazon CloudWatch monitors (CPU utilization, network traffic, and disk activity). • Status checks are performed every minute and each returns a pass or a fail status. If all checks pass, the overall status of the instance is OK. • If one or more checks fail, the overall status is impaired. • Status checks are built into Amazon EC2, so they cannot be disabled or deleted. • You can, however create or delete alarms that are triggered based on the result of the status checks • There are two types of status checks: system status checks and instance status checks.
- 31. System status checks •Monitor the AWS systems on which your instance runs. • These checks detect underlying problems with your instance that require AWS involvement to repair • When a system status check fails, you can choose to wait for AWS to fix the issue, or you can resolve it yourself. • For instances backed by Amazon EBS, you can stop and start the instance yourself, which in most cases migrates it to a new host computer. • For instances backed by instance store, you can terminate and replace the instance. • The following are examples of problems that can cause system status checks to fail: • Loss of network connectivity • Loss of system power • Software issues on the physical host • Hardware issues on the physical host that impact network reachability
- 32. Instance Status Checks • Monitorthe software and network configuration of your individual instance. • These checks detect problems that require your involvement to repair. • When an instance status check fails, typically you will need to address the problem yourself • The following are examples of problems that can cause instance status checks to fail: • Failed system status checks • Incorrect networking or startup configuration • Exhausted memory • Corrupted file system • Incompatible kernel
- 33. Placement Groups You canlaunch or start instances in a placement group, which determines how instances are placed on underlying hardware. When you create a placement group, you specify one of the following strategies for the group: • Cluster—clusters instances into a low-latency group in a single Availability Zone • Spread—spreads instances across underlying hardware
- 34. Cluster placement Group •A cluster placement group is a logical grouping of instances within a single Availability Zone. • Placement groups are recommended for applications that benefit from low network latency, high network throughput, or both. • launch the number of instances that you need in the placement group in a single launch request and that you use the same instance type for all instances in the placement group. • If you receive a capacity error when launching an instance in a placement group that already has running instances, stop and start all of the instances in the placement group, and try the launch again. • Restarting the instances may migrate them to hardware that has capacity for all the requested instances.
- 35. Spread Placement Group A spread placementgroup is a group of instances that are each placed on distinct underlying hardware. Spread placement groups are recommended for applications that have a small number of critical instances that should be kept separate from each other Launching instances in a spread placement group reduces the risk of simultaneous failures that might occur when instances share the same underlying hardware. Spread placement groups provide access to distinct hardware, and are therefore suitable for mixing instance types or launching instances over time. A spread placement group can span multiple Availability Zones, and you can have a maximum of seven running instances per Availability Zone per group.
- 36. Auto Scaling • Youcreate collections of EC2 instances, called Auto Scaling groups. • You can specify the minimum number of instances in each Auto Scaling group, and Auto Scaling ensures that your group never goes below this size • You can specify the maximum number of instances in each Auto Scaling group, and Auto Scaling ensures that your group never goes above this size • If you specify the desired capacity, either when you create the group or at any time thereafter, Auto Scaling ensures that your group has this many instances. • If you specify scaling policies, then Auto Scaling can launch or terminate instances as demand on your application increases or decreases.
- 37. Auto Scaling Components Groups: YourEC2 instances are organized into groups so that they can be treated as a logical unit for the purposes of scaling and management. Launch configurations: Your group uses a launch configuration as a template for its EC2 instances. When you create a launch configuration, you can specify information such as the AMI ID, instance type, key pair, security groups, and block device mapping for your instances Scaling plans: A scaling plan tells Auto Scaling when and how to scale. For example, you can base a scaling plan on the occurrence of specified conditions (dynamic scaling) or on a schedule.
- 38. Benefits of Autoscaling • Auto Scaling can detect when an instance is unhealthy, terminate it, and launch an instance to replace it. You can also configure Auto Scaling to use multiple Availability Zones. Better fault tolerance • Auto Scaling can help you ensure that your application always has the right amount of capacity to handle the current traffic demand Better availability • Auto Scaling can dynamically increase and decrease capacity as needed. Because you pay for the EC2 instances you use, you save money by launching instances when they are actually needed and terminating them when they aren't needed Better cost management
- 39. Instance Distribution Auto Scalingattempts to distribute instances evenly between the Availability Zones that are enabled for your Auto Scaling group Auto Scaling does this by attempting to launch new instances in the Availability Zone with the fewest instances. After certain actions occur, your Auto Scaling group can become unbalanced between Availability Zones. Auto Scaling compensates by rebalancing the Availability Zones. When rebalancing, Auto Scaling launches new instances before terminating the old ones, so that rebalancing does not compromise the performance or availability of your application
- 40. Auto Scaling Lifecycle TheEC2 instances in an Auto Scaling group have a path, or lifecycle, that differs from that of other EC2 instances The lifecycle starts when the Auto Scaling group launches an instance and puts it into service The lifecycle ends when you terminate the instance, or the Auto Scaling group takes the instance out of service and terminates it.
- 41. Life Cycle :Scale Out • The following scale out events direct the Auto Scaling group to launch EC2 instances and attach them to the group: • You manually increase the size of the group • You create a scaling policy to automatically increase the size of the group based on a specified increase in demand • You set up scaling by schedule to increase the size of the group at a specific time.
- 42. Life Cycle :Scale In • It is important that you create a corresponding scale in event for each scale out event that you create. • The Auto Scaling group uses its termination policy to determine which instances to terminate. • The following scale in events direct the Auto Scaling group to detach EC2 instances from the group and terminate them: • You manually decrease the size of the group • You create a scaling policy to automatically decrease the size of the group based on a specified decrease in demand. • You set up scaling by schedule to decrease the size of the group at a specific time.
- 43. Instances In Service Instancesremain in the InService state until one of the following occurs: • A scale in event occurs, and Auto Scaling chooses to terminate this instance in order to reduce the size of the Auto Scaling group. • You put the instance into a Standby state. • You detach the instance from the Auto Scaling group. • The instance fails a required number of health checks, so it is removed from the Auto Scaling group, terminated, and replaced
- 44. Attach an Instance Youcan attach a running EC2 instance that meets certain criteria to your Auto Scaling group. After the instance is attached, it is managed as part of the Auto Scaling group.
- 45. Detach an Instance Youcan detach an instance from your Auto Scaling group. After the instance is detached, you can manage it separately from the Auto Scaling group or attach it to a different Auto Scaling group.
- 46. LifeCycle Hooks :Launch You can add a lifecycle hook to your Auto Scaling group so that you can perform custom actions when instances launch or terminate. The instances start in the Pending state. If you added an autoscaling:EC2_INSTANCE_LAUNCHING lifecycle hook to your Auto Scaling group, the instances move from the Pending state to the Pending:Wait state After you complete the lifecycle action, the instances enter the Pending:Proceed state. When the instances are fully configured, they are attached to the Auto Scaling group and they enter the InService state
- 47. LifeCycle Hooks :Terminate When Auto Scaling responds to a scale in event, it terminates one or more instances. These instances are detached from the Auto Scaling group and enter the Terminating state If you added an autoscaling:EC2_INSTANCE_TERMINATING lifecycle hook to your Auto Scaling group, the instances move from the Terminating state to the Terminating:Wait state. After you complete the lifecycle action, the instances enter the Terminating:Proceed state.
- 48. Enter and ExitStandby • You can put any instance that is in an InService state into a Standby state. • This enables you to remove the instance from service, troubleshoot or make changes to it, and then put it back into service • Instances in a Standby state continue to be managed by the Auto Scaling group. However, they are not an active part of your application until you put them back into service.
- 49.
- 50. Health Checks forAuto Scaling Instances Auto Scaling determines the health status of an instance using one or more of the following: • Status checks provided by Amazon EC2 (systems status checks and instance status checks) • Health checks provided by Elastic Load Balancing. Frequently, an Auto Scaling instance that has just come into service needs to warm up before it can pass the Auto Scaling health check Auto Scaling waits until the health check grace period ends before checking the health status of the instance
- 51. Elastic Load Balancer •A load balancer accepts incoming traffic from clients and routes requests to its registered targets (such as EC2 instances) in one or more Availability Zones • The load balancer also monitors the health of its registered targets and ensures that it routes traffic only to healthy targets • You configure your load balancer to accept incoming traffic by specifying one or more listeners • A listener is a process that checks for connection requests • It is configured with a protocol and port number for connections from clients to the load balancer and a protocol and port number for connections from the load balancer to the targets
- 52. ELB types Elastic LoadBalancing supports three types of load balancers: Application Load Balancers, Network Load Balancers, and Classic Load Balancers With Application Load Balancers and Network Load Balancers, you register targets in target groups, and route traffic to the target groups. With Classic Load Balancers, you register instances with the load balancer.
- 53. Application Load Balancer • AnApplication Load Balancer functions at the seventh layer of the Open Systems Interconnection (OSI) model. • A listener checks for connection requests from clients, using the protocol and port that you configure, and forwards requests to one or more target groups, based on the rules that you define. • Each rule specifies a target group, condition, and priority. When the condition is met, the traffic is forwarded to the target group
- 54. Benefits of ApplicationLoad Balancer • Support for path-based routing. You can configure rules for your listener that forward requests based on the URL in the request • Support for host-based routing. You can configure rules for your listener that forward requests based on the host field in the HTTP header. • Support for routing requests to multiple applications on a single EC2 instance. You can register each instance or IP address with the same target group using multiple ports. • Support for registering targets by IP address, including targets outside the VPC for the load balancer. • Support for containerized applications • Support for monitoring the health of each service independently, as health checks are defined at the target group level and many CloudWatch metrics are reported at the target group level • Improved load balancer performance
- 55. Benefits of NetworkLoad Balancer • Ability to handle volatile workloads and scale to millions of requests per second • Support for static IP addresses for the load balancer. You can also assign one Elastic IP address per subnet enabled for the load balancer • Support for registering targets by IP address, including targets outside the VPC for the load balancer • Support for routing requests to multiple applications on a single EC2 instance. You can register each instance or IP address with the same target group using multiple ports • Support for containerized applications • Support for monitoring the health of each service independently, as health checks are defined at the target group level and many Amazon CloudWatch metrics are reported at the target group level
- 56.
- 57. Overview Elastic Beanstalk providesdevelopers and systems administrators an easy, fast way to deploy and manage their applications without having to worry about AWS infrastructure You simply upload your application, and Elastic Beanstalk automatically handles the details of capacity provisioning, load balancing, scaling, and application health monitoring. Elastic Beanstalk supports applications developed in Java, PHP, .NET, Node.js, Python, and Ruby, as well as different container types for each language Elastic Beanstalk automatically launches an environment and creates and configures the AWS resources needed to run your code After your environment is launched, you can then manage your environment and deploy new application versions
- 58. Elastic Beanstalk workflow To useElastic Beanstalk, you create an application, upload an application version in the form of an application source bundle (for example, a Java .war file) to Elastic Beanstalk, and then provide some information about the application
- 59.
- 60. Overview AWS Lambda isa compute service that lets you run code without provisioning or managing servers AWS Lambda executes your code only when needed and scales automatically, from a few requests per day to thousands per second You pay only for the compute time you consume - there is no charge when your code is not running AWS Lambda runs your code on a high-availability compute infrastructure and performs all of the administration of the compute resources, including server and operating system maintenance, capacity provisioning and automatic scaling, code monitoring and logging All you need to do is supply your code in one of the languages that AWS Lambda supports (currently Node.js, Java, C#, Go and Python)
- 61. AWS Lambda Use Case Youcan use AWS Lambda to run your code in response to events, such as changes to data in an Amazon S3 bucket or an Amazon DynamoDB table; to run your code in response to HTTP requests using Amazon API Gateway; or invoke your code using API calls made using AWS SDKs. With these capabilities, you can use Lambda to easily build data processing triggers for AWS services like Amazon S3 and Amazon DynamoDB, process streaming data stored in Kinesis, or create your own back end that operates at AWS scale, performance, and security This is in exchange for flexibility, which means you cannot log in to compute instances, or customize the operating system or language runtime