Scribd
Upload
98 views6 pages

AWS Services For Devops Engineer

This document provides an overview of several key AWS services useful for DevOps engineers, including compute (EC2), identity and access management (IAM), storage (S3, EBS), networking (VPC), deployment (Elastic Beanstalk), monitoring (CloudWatch), and database services (RDS). It describes the basic functionality of each service and how they can be used together to build cloud infrastructure and deploy applications through a DevOps workflow.

Uploaded by

sathyanarayana meda
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
98 views6 pages

AWS Services For Devops Engineer

This document provides an overview of several key AWS services useful for DevOps engineers, including compute (EC2), identity and access management (IAM), storage (S3, EBS), networking (VPC), deployment (Elastic Beanstalk), monitoring (CloudWatch), and database services (RDS). It describes the basic functionality of each service and how they can be used together to build cloud infrastructure and deploy applications through a DevOps workflow.

Uploaded by

sathyanarayana meda
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 6

AWS Services for Devops Engineer

==>EC2
EC2 stands for elastic compute cloud and is infrastructure as a
service.
2)It’s simply the virtual machine that can be rented. This should be
the first service to start learning AWS cloud or DevOps.
3)EC2 can be used as the server where you can deploy an application
with the DevOps pipeline.
4)You can also run numerous DevOps tools like Jenkins in an EC2
instance.
5)Different types of EC2 instances are available like memory-
optimized, compute-optimized, etc.

==>IAM (Identity Access and Management)


1)With IAM, you can set the permissions(policies) to access the
various AWS services.
2)Different users can be assigned different types of policies. In
DevOps, it is useful to protect the various cloud infrastructure by
setting the access to certain users, team members, or roles.
3)Apart from it, you can also define the IAM role which is helpful
when an AWS service needs to access another service on your
behalf.
4)still need to learn more after terraform

==>S3
1)simple storage services are used to store the data which can be
encrypt. It is object based storage is used to store objects(files of
folders).These can be access globally. We can store up to 5TB and
100 bucket we can create. We can store the by types (aws cli,aws
console, REST API)
2)Bucket: if you create any file folder in root level is called bucket
3)Object: if you store a file in the bucket
4)Components of object (key:name of the object,value:Data in
bytes,version_id:show uniqueness of object,metadata:data about
the data)
5)By using the version if you delete the file, we can retrieve it by
using versioning (we have enabled by manually)
6)By providing ACL so everyone accesses using HTTP URL
7)By using create replica rule in management we can share data bw
two buckets (cross region replication)
8)Create the bucket using CLI launch instance and aws configure
command and for create aws s3 mb s3://bucket_name to remove
bucket aws s3 rb s3://bucketname
9)create files in local and copy to bucket by using aws s3 cp filename
bucketname
10)to delete the file aws s3 rm s3://bucketname –recursive, bucket
delete aws s3 rb s3://buckename –force with files

==>VPC (Virtual Private Cloud) we create bcox prevention loss of


data, isolation, security
1)Its is a secure isolated private cloud which is hosted in the public
cloud, by using this we can run code, store data, host website
2)VPC Architecture Region->VPC->Privates subnets(route_table)
From region to vpc(public_subnet) we access with internet
gateway(publicsubnet) from VPC to by using
natgate_way(credentials) we access to private_subnets(route_table)
3)Subnet: range of IP in our VPC, send data from one to one. CIDR:
class less inter domain routing, while creating subnet we need
choose range of privateIP address the range is called CIDR.
(10.0.0.0/16 to 10.0.0.28 range). ROUTE_TABLE: Each subnet in vpc
has routes to control these we use route table.
4)VPC Creationname, IPv4 CIDR,create vpc==,subnetname,ipv4
CIDR 10.0.0.0/24, create.==,internet_gatewayname,
creategateway, attach vpc, attach.==,Route_tableselect route
table, action-editrotues, add 0.0.0.0/0+internet gateway, save .== ,
Subnetedit subnet_settings,auto_assign, save.
Launch instance using this vpc
5)PEERING: Establish the connection bw vpc instance on diff
networks

==>EBS (Elastic Block storage)


1)we use this for storage purpose we can create the new volume and
we can get the data of previous instance using snapshot by using this
snapshot we can get that existing data to the new instances.
2)Whenever we do the mounting then only the newly generated files
will be showing in the instance launched using snapshot.
3)We have two volumes (Default xvda, when we created new volume
shared xvdf). Change the shared(xvdf) as default and delete the
default.
4)still need to learn more after terraform

==>ELASTIC BEANSTALK
1)It is a service where we can easily deploy the application without
using devops tools
2)create a project in EBS and go to aws code pipeline start a repo and
take the repo http link and clone the repo using git with IAM https
aws pipeline code (create a iam user all admin access)
3)add some code from internet or local code to that repo folder and
git *, git commit -m “msg”, git push
4)create a pipeline using aws pipeline

==>SNS (Simple notification service)


1)In real time we use services we got build success/fail notification
using diff protocol (email, sms etc)
2) create topiccreate subscriptionpublish message

==>SQS (Simple Queue Service)


1)Create queue,name, config(optional), create queue.==, send
&receive msgs, send msg, poll msg, stop poll.

==>RDS (Relation Database Service)


1)RDS automatically manages time-consuming tasks such as
configuration, backups, and patches, you can focus on building your
application.

==>Load Balancer
1)LB is used to balance the request from users in each server without
crashing the servers. LB will rotues the traffic to healthy servers and
identifies the unhealthy servers
2)Launch instance using Windows os with pem.key and 30gb
memory and connect the instance.
3)Go to session manager in the task baradd role and user and
install IIS web server for windowsOS
4)do the same setup launching another server
5)create a LB and group the servers with same security group and
check the output
Types of Load Balancers:
a) application LB: when we need a flexible feature set for our app
with http https traffic
b) network LB: when we need high performance and static IP address
for apps, centralized certificate deployment
c) gateway LB: when you need to deploy and manage third party
virtual appliances that support GENEVE

==>Auto Scaling
1) AWS Auto Scaling monitors your applications and automatically
adjusts capacity to maintain steady, predictable performance at the
lowest possible cost. 
2) Benefit of autoscaling is that it eliminates the need to respond
manually in real-time to traffic spikes that merit new resources and
instances by automatically changing the active number of servers .
3)create auto scaling name,launch template(same as
instance),nextnextadd load balancers,nextwe can select
desired,min,max,nextcreate auto scaling.

==>EFS (Elastic File system)


1)EFS is used to store data & send the data bw two servers
2)Launch two servers with security groupcreate EFS and change
the security grouprum the command in boths servers yum install
amazon-efs-utils -ycopy the command sightly change the folder
name at the last from the attach (aws console) and run in the both
servers.
==>EKS
==>ECR
==>CLOUD FORMATION
==>CLOUD WATCH
==>LAMBDA
==>AWS ROUTE53
==>AWS DATABASE SERVICES

You might also like

pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy