In this module I will throw light on the AWS Global Infastructure, that is built by availibity zones or regions followed by the edge locations that serve as cached copies for faster delivery.
Availibility Zones
An Availability Zone is a single data center or a group of data centers within a Region. Availability Zones are located tens of miles apart from each other. This is close enough to have low latency (the time between when content requested and received) between Availability Zones. However, if a disaster occurs in one part of the Region, they are distant enough to reduce the chance that multiple Availability Zones are affected. This particular advantage serves as the main purpose of the defined infastructure.
The above diagram clearly explains the infastructure of availibility zones (like us-west-1a) within regions (say, N.California) and how they are related within a small distance to maintain low latency.
Planning for failure and deploying applications across multiple Availability Zones is an important part of building a resilient and highly available architecture.
Amazon CloudFront and Edge locations
An edge location is a site that Amazon CloudFront uses to store cached copies of your content closer to your customers for faster delivery. Hence along with the discussion of these caching locations comes Amazon CloudFront, a web service that speeds up distribution of static and dynamic web content, such as .html, .css, .js, and image files, to the users. When a user requests content that you're serving with CloudFront, the request is routed to the edge location that provides the lowest latency (time delay), so that content is delivered with the best possible performance.
I won't dive deep into the CloudFront business instead I will attach a diagram related to it.
Interacting with AWS Services
In AWS, everything is an API call (an API is an application programming interface). And what that means is, there are pre determined ways for you to interact with AWS services. And you can invoke or call these APIs to provision, configure, and manage your AWS resources.
For example, you can launch an EC2 instance or you can create an AWS Lambda function. Each of those would be different requests and different API calls to AWS. You can use the AWS Management Console, the AWS Command Line Interface, the AWS Software Development Kits, or various other tools like AWS CloudFormation, to create requests to send to AWS APIs to create and manage AWS resources.
The AWS Management Console
- The AWS Management Console is a web-based interface for accessing and managing AWS services.
- You can quickly access recently used services and search for other services by name, keyword, or acronym.
- The console includes wizards and automated workflows that can simplify the process of completing tasks.
The AWS Command Line Interface
- To save time when making API requests, you can use the AWS Command Line Interface (AWS CLI).
- AWS CLI enables you to control multiple AWS services directly from the command line within one tool.
- By using AWS CLI, you can automate the actions that your services and applications perform through scripts.
Software Development Kits (SDKs)
- SDKs make it easier for you to use AWS services through an API designed for your programming language or platform.
- SDKs enable you to use AWS services with your existing applications or create entirely new applications that will run on AWS.
Amazon Elastic BeanStalk
AWS Elastic Beanstalk is a service that helps you provision Amazon EC2-based environments. With AWS Elastic Beanstalk, you provide code and configuration settings, and Elastic Beanstalk deploys the resources necessary to perform the following tasks:
- Adjust capacity
- Load balancing
- Automatic scaling
- Application health monitoring
Using IAAS as AWS CloudFormation
AWS CloudFormation provisions your resources in a safe, repeatable manner, enabling you to frequently build your infrastructure and applications without having to perform manual actions. It determines the right operations to perform when managing your stack and rolls back changes automatically if it detects errors.
The next day will be describing how amazing the networking is carried out in AWS, the Subnets and Security groups oh its just awesome !!!
Top comments (0)