- AWS : Virtual Private Network (VPC)
- AWS : Resiliency
- AWS : DynamoDB
- AWS : Business Objectives
- Aws : Infrastructure Deployment
- AWS : Monitor, React, and Recover
|EC2 Container Service|
|Internet of Things||Description|
|S3||AWS developed object store that can store an unlimited amount of data.|
|Elastic file system|
|DynamoDB||AWS developed non-relational database|
|DynamoDB Global Tables||Multi-Region DynamoDB Tables.|
|CloudFormation||For deploying yaml/json template.|
|Region||A Region is a geographical area, each region consists of 2 (or more) Availability Zones.|
|Availability Zone||An Availability Zone (AZ) is simply a Data center.|
|Edge Location||Edge Locations are CDN (Content Delivery Network) End Points for CloudFront. They are used for caching content.|
There are many more Edge Locations than Regions. Currently there are over 150 Edge Locations.
|Networking & Content Delivery telemetry||Description|
|VPC||Virtual Private Cloud.|
VPC can be considered as virtual Data center.
We have VPC in all different regions, where we deploy our assets.
We can have multiple VPC per region and connect one VPC up to another.
|Route53||Amazon DNS service and it works on port 53.|
|Cloud Front||Is used to be in storage section but is moving to networking and content delivery. Cloud front will consists of different edge locations that will cache the assets like videos or large media files.|
|Direct Connect||As a way of connecting up your office or your physical data centers to AWS directly using a dedicated line or dedicated telephone line instead of going through internet. The reason of using the Direct Connect:|
– Very reliable internet connection
|Active/Active||A system that is running actively in multiple instances, typically in a distributed manner where complete functionality is available in more than one area.|
|Snapshot||A complete copy of a dataset at a specific point in time.|
|Server-based Services||Services that are existing applications that AWS provides as “managed services” and run on individual server instances.|
|Compute Services||AWS services that provide generic compute capacity.|
|Baseline||Measurement of conditions at the start of your project used to make planning decisions|
|Cloud||Servers and resources that are accessed over the internet|
|Cloud Computing||Storing and accessing data and applications over the Internet instead of a local or networked computer’s hard drive|
|High Performance Computing (a.k.a. supercomputing)||Supercomputing harnesses the computing power of multiple computers and aggregates them to tackle complex problems in business and academia|
|Infrastructure as Code||The process of provisioning and managing your cloud resources by writing a template file that is both human readable, and machine consumable|
|On-premises||Hardware and software that is contained within the physical confines of a business or their assigned section of a data center|
|Serverless||Compute model where the developer doesn’t need to be concerned with the server because the cloud provider takes care of it|
AWS regions are geographically separate and are also managed separately. When you use the AWS management console, CLI or SDKs, you must be conscious of which region your resources are in as well as which region you are issuing commands to.
Most AWS services are region specific. A few are “global” services meaning that there is no need to specify a region for these services. Global services still make use of the worldwide AWS infrastructure, but they are centrally managed. Route53 and IAM are examples of global AWS services.
The region where we are currently working in it is represented at the top right corner of the AWS console.
Running in how many regions makes your application the least expensive to run? One, because running in multi-region has associated costs.
Availability Zone (AZ)
Many AWS services are able to make use of multiple AZs if you configure them to do so. When services are configured to use multiple AZs, they are considered to be highly available. Even if an entire AZ (complete datacenter) went down, your service would continue to run with minimal interruption.
Either we have a checkbox to run the service in availability zone or we have select subnet.
we really don’t need to worry about latency as, even though they are separate datacenters, the network connections between them are very fast. Also, it’s important to keep in mind that some AWS services do not use all AZs without extra configuration.