Job Category : Jenkins

Secondary Skills :AWS,Linux

Description:

Responsibility: To Manage, maintain and evolve Jenkins OpenSource product by playing the role of an SME in
end to end setup, upgrades, security advisories, patch updates, plugin installations, vulnerability remediations,
user support and product expansion plans.

Mandatory Skills:
Jenkins Administration, installation, upgrades and security advisory patches
AWS - ec2, s3, ALB, NLB, EBS Volumes, AMI recycling
Knowledge of Jenkins HA and DR exercises
Strong Linux Administration Knowledge
Excellent communication skills
Exposure to plugin / core jenkins vulnerability remediations is mandatory

Secondary Skills:
Exposure to SCM tools like Gitlab, Github will be added advantage
Python and Ansible will be added advantage

Load balancing refers to efficiently distributing incoming network traffic across a group of

backend servers load balancer acts as the “traffic cop” sitting in front of your servers and
routing client requests across all servers capable of fulfilling those requests in a manner that
maximizes speed and capacity utilization and ensures that no one server is overworked, which
could degrade performance. If a single server goes down, the load balancer redirects traffic to
the remaining online servers. When a new server is added to the server group, the load
balancer automatically starts to send requests to it.
https://medium.com/@vishal.sharma./setup-aws-elastic-load-balancer-651e44ff0fa0

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.

A listener checks for connection requests from clients, using the protocol and port that you
configure. The rules that you define for a listener determine how the load balancer routes
requests to its registered targets. Each rule consists of a priority, one or more actions, and one
or more conditions. When the conditions for a rule are met, then its actions are performed.
You must define a default rule for each listener, and you can optionally define additional rules.

Each target group routes requests to one or more registered targets, such as EC2 instances,
using the protocol and port number that you specify. You can register a target with multiple
target groups. You can configure health checks on a per target group basis. Health checks are
performed on all targets registered to a target group that is specified in a listener rule for your
load balancer.

Choose an Application Load Balancer when you need a flexible feature set for your web applications
with HTTP and HTTPS traffic. Operating at the request level, Application Load Balancers provide
advanced routing and visibility features targeted at application architectures, including microservices
and containers. 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. Routing is performed independently for each target
group, even when a target is registered with multiple target groups. You can configure the routing
algorithm used at the target group level. The default routing algorithm is round robin; alternatively, you
can specify the least outstanding requests routing algorithm.

You can add and remove targets from your load balancer as your needs change, without disrupting the
overall flow of requests to your application. Elastic Load Balancing scales your load balancer as traffic
to your application changes over time. Elastic Load Balancing can scale to the vast majority of
workloads automatically.

You can configure health checks, which are used to monitor the health of the registered targets so that
the load balancer can send requests only to the healthy targets.

Choose a Network Load Balancer when you need ultra-high performance, TLS offloading at scale,
centralized certificate deployment, support for UDP, and static IP addresses for your application.
Operating at the connection level, Network Load Balancers are capable of handling millions of requests
per second securely while maintaining ultra-low latencies.
After the load balancer receives a connection request, it selects a target from the target group for the
default rule. It attempts to open a TCP connection to the selected target on the port specified in the
listener configuration.

Choose a Gateway Load Balancer when you need to deploy and manage a fleet of third-party virtual
appliances that support GENEVE. These appliances enable you to improve security, compliance, and
policy controls.

Amazon Elastic Block Store (Amazon EBS) provides block level storage volumes for use with EC2
instances. EBS volumes behave like raw, unformatted block devices. You can mount these volumes as
devices on your instances. EBS volumes that are attached to an instance are exposed as storage
volumes that persist independently from the life of the instance. You can create a file system on top of
these volumes, or use them in any way you would use a block device (such as a hard drive). You can
dynamically change the configuration of a volume attached to an instance. Amazon Elastic Block Store
(Amazon EBS) provides block level storage volumes for use with EC2 instances. EBS volumes behave
like raw, unformatted block devices. You can mount these volumes as devices on your instances. EBS
volumes that are attached to an instance are exposed as storage volumes that persist independently
from the life of the instance. You can create a file system on top of these volumes, or use them in any
way you would use a block device (such as a hard drive). You can dynamically change the
configuration of a volume attached to an instance.

An Amazon Machine Image (AMI) is used to create virtual servers (Amazon Elastic Compute
Cloud or EC2 instances) in the Amazon Web Services (AWS) environment. Different types of
instances can be launched from a single AMI to support the hardware of the host computer
used for the instance.