SpiritSofts

• 45 hours of Instructor Training Classes
• Lifetime Access to Recorded Sessions
• Real World use cases and Scenarios
• 24/7 Support
• Practical Approach
• Expert & Certified Trainers

Creating Servers in AWS | Linux Basics & Administration – Week 1

As a beginner, you will understand how a server environment works and how to administer operating systems. As per standard practice used in real projects, we will be using Linux as our standard operating system to complete the course. During the first week, we will discuss creating servers in the AWS environment along with some other basics in AWS Cloud. This will be followed by Linux basics and administration topics.

Topics Covered:

• Create an account in AWS
• Understanding Regions and Availability Zones in AWS
• Installing required software’s in Desktop
• Setting up access to AWS cloud using SSH Keys
• Create servers in EC2 Service
• Understand Linux Command Line
• Getting Server Information using Linux Commands
• File and Directory management
• Using VI/VIM Editor
• Linux cli utilities for downloading software
• Linux Administration Topics
• User Management
• Package Management
• Service Management
• Disk Management
• Network Management
• File Permissions

Installation | Creation of EC2 | RDS | Shell Scripting | Jenkins – Week 2

As a DevOps Engineer, you will collaborate with software engineering teams to deploy and operate systems, while helping to automate and streamline operations and processes. During this week, we will understand the application architectures and set up those applications practically in AWS EC2 instances manually. We will also proceed to set up our applications in an automated way using Shell Scripting. To invoke shell scripts, we will use Jenkins as an automation tool, and we will cover a few basic topics related to Jenkins.

Topics Covered:

• Understand different components of an application
• Understand the architecture of an application
• Installing and Configuring Web Server, Application Server and Database Servers
• Integration of Web, Application and Database servers to work as a stack
• Understanding the latest generation spring boot applications versus legacy applications
• Creation of servers in EC2 instances in and setup web and application servers
• Creation of RDS instances in AWS for application stack
• Setup Security Group firewalls to limit the database to be accessed by only Application Server.
• Introduction to Shell Scripting
• Printing messages with Shell Scripting
• Variables and Functions in Shell Scripting
• Getting Inputs from user in Shell Scripting
• Conditions and Loops in Shell Scripting
• Develop shell scripts to install all web, app and db related configs with shell scripting
• Installation of Jenkins
• Triggering the shell scripts on remote nodes using Jenkins

DevOps Machinery VCS Ansible GIT – Week 3

DevOps has several components that must work in unison for a team to meet its objectives. A key element that serves as the center of the DevOps “machinery” is configuration management. During this week, we will enhance our automation with the configuration management tool, Ansible. We will configure and set up WEB, APP, and DB components on servers, discussing Ansible in greater depth along with integration of the source code management tool GIT. We will also track all changes made to the code.

Topics Covered:

• Introduction to VCS
• Difference between CVCS(SVN) and DVCS(GIT)
• Architecture of GIT
• Using existing GIT Repositories
• Installing GitLab Server and Create Users and delegate Repositories
• Installation of Ansible and Configuring Ansible.
• Ansible Inventory file
• YAML syntax for Ansible Playbooks
• Understanding Playbooks, Plays, Task and Modules
• Different ways of defining variables with Ansible
• Conditions and Loops in Ansible
• How TAGS are used in Ansible
• Setup Application using Ansible and update code in Git Repositories
• Run the ansible playbooks with Jenkins for automation
• Ansible Vault
• Roles in Ansible
• Ansible pull and Galaxy

Elastic Beanstalk IAM ELK Cloud Watch – Week 4

As companies seek to improve their application development processes by transitioning from waterfall to DevOps, they also recognize that DevOps alone cannot save them. The delay in making capital purchases of hardware and software slows the development process, even if it’s made agile. Developers end up waiting for capital resources to be put in place before the applications can be deployed. Thus, DevOps won’t have much value without the cloud, and the cloud won’t have much value without DevOps. The centralized nature of cloud computing provides DevOps automation with a standard and centralized platform for testing, deployment, and production. During this week, we will set up our project with multiple environments and use Elastic Beanstalk service to replicate the same thing in the AWS Cloud. We will also discuss restricting users to use particular services in AWS using IAM and managing servers with AWS Systems Manager, which is an alternative to Ansible in the cloud. Additionally, we will talk about basic monitoring and log monitoring using ELK.

Topics Covered:

• Understand the importance of multiple environments for an application
• Setup multiple environment application
• Use ansible to configure and customize these environments in an automated way
• Use Jenkins to deploy the new application based on environments
• Introduction to AWS Elastic Beanstalk Service
• Setup DEV and PROD environments in Elastic Beanstalk
• Introduction to IAM
• IAM Users and Groups
• IAM Roles and Policies
• Making Custom Roles and Policies
• Introduction to AWS Systems Manager
• Deploy the application with AWS Systems Manager
• Use AWS Systems Manager as Configuration Management tool
• Setup monitoring using NewRelic
• Setup Log Monitoring using ELK, Using Elasticsearch service from AWS
• Introduction to Cloud Watch
• Monitor Performance with CloudWatch of your instances
• Using CloudWatch as an alternative to log monitoring

CI/CD Maven and Gradle Python SonarQube GitLab tool Jenkins – Week 5

Continuous Integration and Continuous Delivery (CI/CD) are critical components of successful DevOps practices. To establish and optimize the CI/CD development model and reap the benefits, companies need to build an effective pipeline that automates their build, integration, and testing processes. At a high level, the pipeline includes compiling, packaging, and running basic tests before a code base merge. After the code is in the main branch of the version control software, additional tests are run to ensure the apps work with real configuration and services. Performance and security tests are also conducted. From there, code is deployed to staging and then to production.

In this week, we will cover the tools that help to establish and optimize the CI/CD pipeline for successful DevOps. We will discuss GIT branching strategies, build tools like Maven and Gradle, functional testing using Selenium and Python code, Code Quality testing using SonarQube, Nexus artifact manager, and GitLab tool. The main focus will be on using Jenkins Pipeline code and Seed Jobs in Jenkins for complete automation to deliver code to production in a smooth manner.

Topics Covered:

• Understanding CICD
• Best Practices of CICD
• Understanding different jobs in Jenkins
• Introduction to Jenkins Pipelines and Groovy
• Doing Jenkins automation with Seed Jobs
• Understanding GIT branching strategy
• Introduction to Maven Projects
• Understanding different Maven life cycle phases and customize them as per requirements
• Introduction to Gradle Projects and understand how to build binaries with Gradle
• Introduction Code Quality Analysis using SonarQube
• Setup SonarQube and test the development code and publish reports
• Using Selenium code for UI testing
• Writing Python scripts for API testing
• Introduction to Artifact Managers
• Setup Nexus and understand different types of repositories
• Creating repositories and limiting access to particular users to upload and download artifacts
• Setup Jenkins pipeline to include all the tools and ensure build happens automatically
• Introduction to Multibranch Pipelines
• Setup automated pipelines using Multibranch
• Deep Dive into Jenkins and all management options

Devops CI/CD Techniques | Simple Storage Server (S3) – Week 6

Continuous Integration and Continuous Delivery (CI/CD) techniques promote collaboration, increase agility, and expedite high-quality product delivery. Cloud technologies have made integrating a CI/CD pipeline easier than ever before. DevOps automation is increasingly becoming cloud-centric, with most public and private cloud computing providers offering systemic support for DevOps, including continuous integration and continuous development tools. This integration significantly reduces the costs associated with on-premises DevOps automation technology and offers centralized governance and control for a sound DevOps process. Many developers find that governance keeps them out of trouble, and it’s easier to control centrally via the cloud than attempting to bring departments under control. In the previous week, we discussed pipeline setups using different tools, and in this week, we will replace them with AWS services. Specifically, we will use S3 buckets as an artifact repository, Code Commit as our GIT repository, CodeBuild instead of Jenkins Builds, Code Deploy instead of Ansible, and Code Pipeline instead of Jenkins Pipelines.

Topics Covered:

• Introduction to Simple Storage Server (S3)
• Creating buckets using Console
• Uploading and downloading data to S3
• Building static websites using S3
• Enable version control on S3
• Getting Started with Code Commit
• Working with Repositories
• Working with Commits
• Working with Branches
• Migrate to AWS CodeCommit
• Authentication and Access Control
• Getting Started with CodeBuild
• Run AWS CodeBuild Directly
• Use AWS CodePipeline with AWS CodeBuild
• Use AWS CodeBuild with Jenkins
• Working with Build Projects and Builds
• Getting started with CodeDeploy
• Application Specification Files
• Working with the AWS CodeDeploy Agent
  DevOps Training
• Working with Instances
• Working with Deployment Configurations
• Working with Deployment Groups
• Working with Deployments
• AppSpec File Reference
• Concepts of CodePipeline
• Working with Pipelines
• Working with Actions
• Working with Stage Transitions
• Monitoring Pipelines

Docker Jenkins Kubernetes – Week 7

Nowadays, it is crucial to release software quickly, which requires an automated CI/CD pipeline to take code from text to binaries and deploy it. Implementing an automated pipeline has been challenging in the past, especially with legacy applications. Docker and Kubernetes solve this problem. Kubernetes has revolutionized the way we deploy and manage containerized applications. Using Helm with Kubernetes simplifies application deployment. Kubernetes is a modern DevOps tool, and the infrastructure side requires a declarative approach. DevOps tools have reduced deployment times from days to hours, and Kubernetes can bring them down to minutes. This week, we will discuss containerization technologies and the basics of Docker. Then, we will delve into Kubernetes in detail and complete all CI/CD setups with Jenkins Kubernetes integrations.

Topics Covered:

• What is Virtualization?
• What is Containerization?
• Virtualization vs Containerization
• Introduction to Docker
• Running Docker Containers
• Making Docker Images with Dockerfile and push them to Docker Registry
• Launching AWS Elastic Kubernetes Service for practice
• Get cluster details
• List all nodes associated with the cluster
• Stopping a cluster
• Deleting a cluster
• Installing & Accessing the Kubernetes dashboard
• Deploy a containerized app image in the locally setup kubernetes cluster
• List all local deployments
• Create a kubectl proxy for forwarding communication to cluster-wide private network
• Curl to verify that the app is running
• List all existing pods
• Get description of a specific pod
• View logs of the container
• Execute commands directly on the container
• Create a ephemeral volume in EBS.
• Configure Pod to store data in EBS Volumes.- Create a new service
• Add ha-proxy to configuration file as proxy to expose the application
• Expose the service outside the cluster using ha-proxy
• List all services
• Get more details of a particular service
• Get more information about a label
• Use labels to query required pods
• Create a new label to the pod
• Scale up the above deployment to 4 replicas
• Scale down the above deployment to 2 replicas
• Update the image of the application in deployments
• Check the rollout status in deployments
• Rollback an update in deployments
• Delete the service created
• Helm charts and their need in Kubernetes
• Deploy an application with helm charts

Infrastructure as Code (IaC) Terraform – Week 8

Infrastructure as Code (IaC) refers to the management of infrastructure (such as networks, virtual machines, load balancers, and connection topology) using a descriptive model that utilizes the same versioning as the DevOps team’s source code. Similar to how the same source code generates the same binary, an IaC model generates the same environment every time it is applied. IaC is a crucial DevOps practice and is utilized in conjunction with continuous delivery. Tools such as Terraform, AWS CloudFormation, Azure Resource Manager Templates, Google Cloud Deployment Manager Templates, and OpenStack Heat provide an excellent way to define server infrastructure for deploying software. The configuration to provision, modify, and rebuild an environment is captured in a way that is transparent, repeatable, and testable, giving us the confidence to tweak, change, and refactor our infrastructure easily and comfortably. In this week, we will provision all AWS services using Terraform and integrate IAC into our CICD process. We will also deliver the release in blue-green deployments without any outage to the end customer.

Topics Covered:

• Introduction to IaC
• Introduction to Terraform
• Terraform Installation
• Configuring terraform with AWS
• Create an EC2 instance with Terraform
• Variables in Terraform
• Output Attributes in Terraform
• State file
• Importance of Remote State file
• Data Sources
• Templates
• Modules in Terraform
• Best Practices of Module creation in Terraform
• Create all the resources with Terraform and launch complete infrastructure with Terraform
• Services: EC2, ALB, VPC, RDS, IAM , Beanstalk, S3, CloudWatch
• Introduction to Interpolation
• Conditionals
• Built-In Functions
• Best Practices of Terraform
• Include terraform CICD

For DevOps Interview Questions Click Here