In this session, we will look a the building blocks available on AWS for Compute, Storage and Networking. It will focus on providing and overview how what each service is used for to prepare the attendee for the 3 followup sessions where each of the 3 categories will be covered in more detail.
So we talked about ECS, Fargate, and Lambda and so the serverless operations model looks like this
1/ You can start at the very bottom with EC2 and have access to all the knobs you want to manage or you could go completely serverless with lambda and Fargate where you’re focusing just on your application.
2/ So the layers of abstractions available to you with AWS is super empowering because your teams have the choice to pick the layer of abstraction they’re most comfortable with and we will provide you the tools, services, and APIs necessary to help you build your application
As I mentioned earlier, we EC2 stands for Elastic Compute Cloud.
We have racks of EC2 servers deployed across all of our regions, with each AWS regions consisting of multiple availability zones or AZs as we call then, and each AZ is typically multiple data centers.
Within these racks, we have sometimes dozens of servers that each contain Processors, Memory, Networking and sometime local storage. As part of the EC2 stack, we have an hypervisor that partitions these resources, in to virtual machines or guests, which we call as an EC2 instance.
1/ And this is what your layers of management end up looking like. You’ve this completely managed orchestration or container management layer but you also have these software management layers just to run your application.
2/ And all you really want here is to run your containers. And Fargate enables you to do just that. So if you notice here, there is no management of instances, your infra is ready to scale as you application is.
3/ There are no 2 levels of management of scale anymore. You only define the requirement of your application in terms of a task – how should the service scale, what metrics do you care about and how many more such container or task you want Fargate to launch.
Here we’ve configured 172.31.0.0/16 as the VPC CIDR and created two public subnets (172.31.0.0/24, 172.31.1.0/24) and two private subnets (172.31.128.0/24, 172.31.129.0/24).
Here we’ve configured 172.31.0.0/16 as the VPC CIDR and created two public subnets (172.31.0.0/24, 172.31.1.0/24) and two private subnets (172.31.128.0/24, 172.31.129.0/24).
Here we’ve configured 172.31.0.0/16 as the VPC CIDR and created two public subnets (172.31.0.0/24, 172.31.1.0/24) and two private subnets (172.31.128.0/24, 172.31.129.0/24).