Amazon ECS

Amazon ECS:
 Docker packages software into standardized units called Containers that has everything
that your software needs to run including libraries, system tools, code and runtime.
 Lets you quickly deploy your code into any application and it will run.
 It will create a file known as Docker Image that will contain all the information regarding
your current project.
 Amazon EC2 Container Registry (ECR) can store, manage and deploy container
images integrated with Amazon ECS.
 Amazon EC2 Container Service (ECS) runs and manages docker-enabled applications
across a group of Amazon EC2 instances.
 Amazon ECS Cluster is a logical group of Amazon EC2 instances that you can place
containers onto.
Types of Storages:
 S3
 EBS (Elastic Block Storage SSD Storage that gets attached to instances)
 EFS (Elastic File System)
 Glacier (Used for storing data somewhere at a low cost)
 Storage Gateway (Move local data to cloud and keep a copy of it locally)
 Snowball Edge (Data Import/Export System)
Simple Storage Service:

 Object storage service we can store data from internet but cannot install anything in it.
 Built for storing and recovering any amount of information or data from anywhere over
the internet.
 Max size of a S3 bucket is 5 TB.
AWS Codepipeline:
 It is a continuous delivery service you can use to model, visualize and automate the
steps required to release your software.
 Monitor your processes in real time.
AWS Codebuild:
 It is a fully managed continuous integration service that compiles source code, run tests
and builds artefacts.
 The teams only have to commit code continuously and codebuild will take care of
handling concurrent jobs eliminating queue times.
AWS CloudFormation:
 AWS CloudFormation gives you an easy way to model a collection of related AWS and
third-party resources, provision them quickly and consistently, and manage them
throughout their lifecycles, by treating infrastructure as code.
 A CloudFormation template describes your desired resources and their dependencies
so you can launch and configure them together as a stack.
 You can use a template to create, update, and delete an entire stack as a single unit, as
often as you need to, instead of managing resources individually.
 You can manage and provision stacks across multiple AWS accounts and AWS
Regions.
 Manages stack of AWS Resources based on the templates that you created.
AWS CloudFront:
 Amazon CloudFront is a fast content delivery network (CDN) service that securely
delivers data, videos, applications, and APIs to customers globally with low latency,
high transfer speeds, all within a developer-friendly environment.
 CloudFront offers the most advanced security capabilities, including field level
encryption and HTTPS support, seamlessly integrated with AWS Shield, AWS Web
Application Firewall and Route 53 to protect against multiple types of attacks including
network and application layer DDoS attacks.
AWS CloudWatch:
 CloudWatch is a monitoring service for AWS cloud resources and the applications you
run on AWS.
 Allows you to record metrics for EBS, EC2, ELB and S3.
 Create events to trigger Lambda functions.
 Install agents on EC2 to send monitoring data to CloudWatch.
 Set alarms to warn based on usage resources.
AWS Fargate:
 Make serverless containers so that you can worry only about your application and not
servers, all that will be handled by AWS.
AWS Application Load Balancer:
 A load balancer serves as the single point of contact for clients.
 The load balancer distributes incoming application traffic across multiple targets, such
as EC2 instances, in multiple Availability Zones.
 This increases the availability of your application. You add one or more listeners to your
load balancer.
 An Application Load Balancer functions at the application layer, the seventh layer of the
Open Systems Interconnection (OSI) model.
 After the load balancer receives a request, it evaluates the listener rules in priority order
to determine which rule to apply, and then selects a target from the target group for the
rule action.
 You can configure listener rules to route requests to different target groups based on
the content of the application traffic.
AWS Route 53:

 Route 53 is a DNS service that gives developers an efficient way to connect users to
Internet applications without any downtime.
 Highly scalable DNS Service.
 If a website needs a name, Route 53 registers the name for the website (e.g.
www.google.com)
 Route 53 helps to connect the browser with the website or web application when the
user enters the domain name.
 Route 53 checks health of resources by sending automated requests to a server.
AWS Lambda:
 It runs your backend code in response to events such as object uploads to Amazon S3
bucket, updates to DynamoDB data.
 Once you upload the code to Lambda the service handles all the capacity, scaling,
handling, administration and patching and also provides the metrics of the requests
handled.

Amazon ECS

Uploaded by

Copyright:

Available Formats

Amazon ECS

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Amazon ECS

Uploaded by

Copyright:

Available Formats

Amazon ECS:

Simple Storage Service:

AWS Route 53:

You might also like