📌 Differences Between AWS EC2 Instance: Start, Stop, and Restart Operation 📌

Many of us who use AWS often stop, start, or restart instances. However, only some realize differences in how these operations work.

🔄 Instance Reboot:
A reboot is equivalent to a restart operation on a traditional physical machine. It keeps the instance on the same host machine unless the host is unhealthy or has other problems. The instance keeps the same public and private IP addresses, and any data on the instance store volumes and Elastic Block Store (EBS) volumes remains intact.

❓How does it work
When a reboot command is initiated, the hypervisor sends a signal to the guest operating system to perform a soft reboot, which is a more graceful way to restart the system. The operating system will stop all running processes, flush any cached data to disk, and restart.

🛑 Instance Shutdown (Stop):
Stopping an instance is like shutting down a physical machine. The instance is powered down and no longer running, so you're not billed for additional instance hours. The instance retains its instance ID, but all data in the instance store volumes is lost. The public IP address is released when the instance is stopped (unless associated with an Elastic IP), but the private IP address remains associated. When the instance is started again, it might be run on a different host machine.

❓How does it work
When a stop command is initiated, the hypervisor sends a signal to the guest operating system to perform a soft shutdown, which is a more graceful way to shut down the system. All the processes will be stopped, and any cached data will be written to disk. After that, the hypervisor will deallocate the previously allocated resources to the instance.

😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

𝐂𝐥𝐨𝐮𝐝 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 𝐓𝐨𝐨𝐥𝐬 𝐂𝐡𝐞𝐚𝐭 𝐒𝐡𝐞𝐞𝐭❗️

The cloud has revolutionized the way we manage and scale our infrastructure, but ensuring its reliability and performance is paramount. That's where cloud monitoring tools come into play.

Here's a cheat sheet to help you navigate the world of cloud monitoring:

🔍 𝐖𝐡𝐚𝐭 𝐭𝐨 𝐌𝐨𝐧𝐢𝐭𝐨𝐫:
🔣Resource Utilization: Keep tabs on CPU, memory, disk, and network usage.
🔣Latency: Monitor response times to ensure optimal user experiences.
🔣Error Rates: Track error occurrences to address issues promptly.
🔣Traffic: Understand your traffic patterns and spikes.
🔣Security: Detects and respond to potential security threats.

⚙️ 𝐏𝐨𝐩𝐮𝐥𝐚𝐫 𝐂𝐥𝐨𝐮𝐝 𝐌𝐨𝐧𝐢𝐭𝐨𝐫𝐢𝐧𝐠 𝐓𝐨𝐨𝐥𝐬:
🔣Amazon CloudWatch: Ideal for AWS users, offering comprehensive monitoring and alerting.
🔣Google Cloud Monitoring: Seamlessly integrated with GCP for real-time insights.
🔣Azure Monitor: Microsoft's solution for monitoring Azure resources.
🔣Prometheus: An open-source option with a robust alerting system.

📈 𝐊𝐞𝐲 𝐌𝐞𝐭𝐫𝐢𝐜𝐬 𝐭𝐨 𝐖𝐚𝐭𝐜𝐡:
🔣CPU Usage: Indicates the load on your virtual machines.
🔣Memory Utilization: Monitors available memory and identifies bottlenecks.
🔣Network Throughput: Tracks data transfer rates.
🔣Response Times: Measures how quickly your services respond.
🔣Error Rates: Identifies issues impacting user experiences.

🚨 𝐀𝐥𝐞𝐫𝐭𝐢𝐧𝐠 𝐚𝐧𝐝 𝐀𝐮𝐭𝐨𝐦𝐚𝐭𝐢𝐨𝐧:
Set up alerts for critical metrics to proactively address issues.
Leverage automation to scale resources up or down based on demand.


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🟡 𝗬𝗼𝘂 𝗠𝗨𝗦𝗧 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 🐧𝗟𝗶𝗻𝘂𝘅 𝗳𝗶𝗹𝗲 𝘀𝘆𝘀𝘁𝗲𝗺

Linux's file system is tree-like. The base is "/", with everything else branching off.

➡️ Core Directories:

/bin 🛠: Essential binaries, e.g., bash, ls, grep.
/boot 🚀: Boot items like kernel & bootloader.
/dev 🔌: Device files for connected hardware.
/etc 📜: System configuration files.
/home 🏡: User home directories.
/lib 📚: Shared libraries for programs.
/media 💿: Mounts for removable media.
/mnt 🧲: Temporary mounts.
/opt 📦: Optional software.
/proc 📊: System, process, memory info.
/root 👑: Root user's home.
/sbin 🔧: System admin tools, e.g., init.
/srv 🌐: Data for services.
/tmp 🌡: Temporary files.
/usr 🖥: User software.
/var 🔄: Variable data, logs, temp files.

🐧 Linux Commands:

cd 🚶: Navigate.
ls 📋: List contents.
mkdir 📁: Create folder.
rmdir 🗑: Delete folder.
cp 📤: Copy.
mv 🚚: Move.
rm ❌: Delete.

⚠️ Note: Directories like /bin are crucial. Don't modify!

🔵 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

💥 𝗔 𝘁𝗲𝘀𝘁 𝗰𝗿𝗶𝗰𝗸𝗲𝘁 𝗺𝗮𝘁𝗰𝗵 𝗶𝘀 𝘃𝗶𝗲𝘄𝗲𝗱 𝗯𝘆 𝗼𝘃𝗲𝗿 𝟯𝟬 𝗰𝗿𝗼𝗿𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝘄𝗶𝘁𝗵𝗶𝗻 𝟱 𝗱𝗮𝘆𝘀 𝗼𝗻 𝗷𝗶𝗼 𝗰𝗶𝗻𝗲𝗺𝗮 𝗶𝘀 𝗵𝘂𝗴𝗲, let's see how it handles such traffic.

JioCinema uses two different cloud providers that include Amazon Web Services (AWS) and Google Cloud Platform (GCP).

🔣𝙇𝙤𝙖𝙙 𝙗𝙖𝙡𝙖𝙣𝙘𝙚𝙧:
JioCinema uses load balancers to distribute the user traffic among multiple backend servers that ensures efficiency and no server is overloaded.

🔣𝘼𝙪𝙩𝙤𝙨𝙘𝙖𝙡𝙞𝙣𝙜 𝙜𝙧𝙤𝙪𝙥𝙨:
These are implemented in such a way that if the current servers are being overloaded then new servers can be created automatically using autoscaling groups.

🔣𝘾𝙤𝙣𝙩𝙚𝙣𝙩 𝘿𝙚𝙡𝙞𝙫𝙚𝙧𝙮 𝙉𝙚𝙩𝙬𝙤𝙧𝙠 (𝘾𝘿𝙉𝙨):
JioCinema uses CDNs to distribute content to its users. CDNs are distributed systems of servers that cache and deliver content to users from the closest possible edge locations. This helps to reduce latency and improves user experience.

🔣𝙈𝙞𝙘𝙧𝙤𝙨𝙚𝙧𝙫𝙞𝙘𝙚 𝙖𝙧𝙘𝙝𝙞𝙩𝙚𝙘𝙩𝙪𝙧𝙚:
This approach breaks down the application into smaller and manageable components and becomes easier for scalability and maintenance.
Any specific component can be scaled up or down without affecting other components.

𝙋𝙎: In this post I have only discussed how JioCinema handles such loads efficiently irrespective of how it is coded and what protocols they are using.


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

📣 How do you manage different versions of 𝗧𝗲𝗿𝗿𝗮𝗳𝗼𝗿𝗺? Manually? There is a better way! 😎

𝗧𝗳𝘀𝘄𝗶𝘁𝗰𝗵 is a useful tool for managing Terraform versions, particularly when working with multiple projects that require different versions due to syntax changes, provider updates, or other dependencies. Here are some reasons why tfswitch is beneficial:

👉 𝗣𝗿𝗼𝗷𝗲𝗰𝘁 𝗖𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗶𝗹𝗶𝘁𝘆: Different Terraform projects may require specific versions to ensure compatibility with the project's syntax, providers, or dependencies. Tfswitch enables you to switch effortlessly between these versions, ensuring that you are always using the correct Terraform version for a particular project.

👉 𝗔𝘃𝗼𝗶𝗱 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝗖𝗼𝗻𝗳𝗹𝗶𝗰𝘁𝘀: When working on multiple projects simultaneously, conflicts may arise if each project relies on a different Terraform version. Tfswitch helps prevent version conflicts by allowing you to set the appropriate version for each project independently.

👉 𝗘𝗮𝘀𝘆 𝗨𝗽𝗴𝗿𝗮𝗱𝗲𝘀: Tfswitch simplifies the process of upgrading to newer Terraform versions. With a single command, you can switch to the latest release, ensuring that you benefit from the latest features, bug fixes, and improvements.

👉 𝗦𝗲𝗮𝗺𝗹𝗲𝘀𝘀 𝗪𝗼𝗿𝗸𝗳𝗹𝗼𝘄 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻: Tfswitch can be integrated into your shell profile, allowing for automatic version detection and alias support for frequently used versions. This streamlines the process of working with Terraform and reduces the need for manual version switching.

👉 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝗟𝗼𝗰𝗸𝗶𝗻𝗴: Tfswitch allows you to lock a project to a specific Terraform version by creating a .tfswitchrc file in your project's root directory. This ensures consistency when collaborating on projects and helps avoid potential issues caused by version conflicts.

Tfswitch is available only for Linux and MacOS.

😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🔥 Basic Kubectl commands which are essential for a DevOps engineer to manage within a Kubernetes cluster.

💠 Pods:
⏩ Create a Pod: kubectl create -f pod.yaml
⏩ Get Pods: kubectl get pods
⏩ Describe Pod: kubectl describe pod <pod_name>
⏩ Logs: kubectl logs <pod_name>
⏩ Exec into Pod: kubectl exec -it <pod_name> -- <command>
⏩ Delete Pod: kubectl delete pod <pod_name>

💠 Deployments:
⏩ Create a Deployment: kubectl create -f deployment.yaml
⏩ Get Deployments: kubectl get deployments
⏩ Describe Deployment: kubectl describe deployment <deployment_name>
⏩ Scale Deployment: kubectl scale --replicas=3 deployment/<deployment_name>
⏩ Rollout Status: kubectl rollout status deployment/<deployment_name>
⏩ Rollout History: kubectl rollout history deployment/<deployment_name>

💠 Services:
⏩ Create a Service: kubectl create -f service.yaml
⏩ Get Services: kubectl get services
⏩ Describe Service: kubectl describe service <service_name>
⏩ Delete Service: kubectl delete service <service_name>

💠 ConfigMaps:
⏩ Create a ConfigMap: kubectl create configmap <configmap_name> --from-file=<file_path>
⏩ Get ConfigMaps: kubectl get configmaps
⏩ Describe ConfigMap: kubectl describe configmap <configmap_name>
⏩ Delete ConfigMap: kubectl delete configmap <configmap_name>

💠 Secrets:
⏩ Create a Secret: kubectl create secret generic <secret_name> --from-literal=<key>=<value>
⏩ Get Secrets: kubectl get secrets
⏩ Describe Secret: kubectl describe secret <secret_name>
⏩ Delete Secret: kubectl delete secret <secret_name>

💠 Nodes:
⏩ Get Nodes: kubectl get nodes
⏩ Describe Node: kubectl describe node <node_name>

💠 Namespaces:
⏩ Get Namespaces: kubectl get namespaces
⏩ Describe Namespace: kubectl describe namespace <namespace_name>

💠 PersistentVolumes (PV) and PersistentVolumeClaims (PVC):
⏩ Get PVs/PVCs: kubectl get pv / kubectl get pvc
⏩ Describe PV/PVC: kubectl describe pv <pv_name> / kubectl describe pvc <pvc_name>
⏩ Delete PV/PVC: kubectl delete pv <pv_name> / kubectl delete pvc <pvc_name>


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🌐 Mastering Git commands is essential for efficient collaboration and version control in software development. 🛠

Whether you're a beginner or seasoned developer, understanding Git basics is a must!


🎄 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🔥 PROVISION EKS (Amazon Elastic Kubernetes Service) CLUSTER ON AWS USING TERRAFORM 🔥

➡️ In This guide we clearly explained with screenshots and commands how to do it.

🔗 Link: https://github.com/NotHarshhaa/AWS-EKS_Terraform

This provides a comprehensive guide on provisioning an Amazon Elastic Kubernetes Service (EKS) cluster on AWS using Terraform.

☄️ Go check it guys and share with your Friends & Colleagues🔥

#Terraform #AWS #eks #awsdevops


✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

➡️ 𝐖𝐡𝐚𝐭 𝐢𝐬 𝐃𝐨𝐜𝐤𝐞𝐫𝐟𝐢𝐥𝐞?

A Dockerfile is essentially a set of instructions that Docker follows to build a Docker image. These instructions specify what operating system to use, what software packages to install, what files to copy into the container, what environment variables to set, and what commands to run when the container starts.

➡️𝐖𝐡𝐲 𝐔𝐬𝐞 𝐚 𝐃𝐨𝐜𝐤𝐞𝐫𝐟𝐢𝐥𝐞?

🔹Reproducibility: With a Dockerfile, you can ensure that your application environment is consistent across different environments, such as development, testing, and production. This reproducibility eliminates the "it works on my machine" problem.

🔹Version Control: Dockerfiles are text files that can be version controlled using tools like Git. This means you can track changes to your Docker environment over time and easily roll back to previous versions if needed.

🔹Automation: Dockerfiles enable automation of the containerization process. Once you have defined your Dockerfile, you can use it to build your Docker image with a single command, streamlining the deployment process.

🔹Scalability: Dockerfiles allow you to define the components of your application stack in a modular way. This makes it easy to scale your application by adding or removing containers as needed.

🔹Collaboration: Dockerfiles make it easy to share your application environment with collaborators. By sharing your Dockerfile, others can quickly spin up the same environment on their own machines.


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

💬 Ansible is an open-source automation tool used for configuration management, app deployment, and automation. It allows DevOps engineers to automate repetitive tasks such as provisioning infrastructure, deploying applications, and managing configurations across a large number of servers.

Key features of Ansible:
1️⃣. Agentless architecture
2️⃣. Declarative language
3️⃣. Idempotency
4️⃣. Orchestration capabilities
5️⃣. Extensibility


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

☄️ Troubleshoot Application Failures with #Kubernetes! ‼️

⚠️ Troubleshooting #Kubernetes requires a systematic approach to identify and resolve issues. By leveraging Kubernetes’ built-in tools and commands, you can diagnose most common problems. Remember to start with simple checks and progressively move to more detailed investigations to efficiently troubleshoot application failures in Kubernetes.

1. Check Pod Status: To assess the health and status of your pods within a specific namespace, use the kubectl get pods command.
-> kubectl get pods -n <namespace>

2. Review Pod Logs: To review the logs of a specific pod, which can be invaluable for troubleshooting, use the kubectl logs command.
-> kubectl logs <pod-name> -n <namespace>

3. Use kubectl describe: For a comprehensive overview of a pod’s configuration and events, kubectl describe is invaluable.
-> kubectl describe pod <pod-name> -n <namespace>

4. Check for Resource Constraints: Resource constraints can cause pods to fail to start or run properly. Use kubectl describe nodes to identify resource allocation and availability.
-> kubectl describe nodes

5. Examine Liveness and Readiness Probes: Liveness and readiness probes determine the health of a pod. Misconfigurations can cause pods to be killed or not receive traffic. Define probes in your pod or deployment YAML.

6. Debugging with kubectl exec: kubectl exec lets you execute commands inside a container, which can be useful for debugging.
-> kubectl exec -it <pod-name> -- /bin/sh

7. Inspect Kubernetes Events: Kubernetes events provide insight into what’s happening in the cluster. Use kubectl get events to retrieve events.
-> kubectl get events --sort-by='.metadata.creationTimestamp' -n <namespace>

8. Verify Service and Ingress Configurations: Services and Ingresses are key to exposing Kubernetes applications. Misconfigurations can lead to inaccessible services. Use kubectl get to inspect these resources.
-> kubectl get svc,ingress -n <namespace>

9. Analyze Network Policies: Network Policies define how pods communicate with each other and the outside world. Use kubectl get to list active network policies.
-> kubectl get networkpolicy -n <namespace>

10. Check for ImagePullBackOff Errors: ImagePullBackOff indicates Kubernetes is unable to pull a container image. Inspect the pod or describe it to see the error details.
-> kubectl describe pod <pod-name> -n <namespace>

11. Utilize Kubernetes Dashboard: The Kubernetes Dashboard provides a web-based UI for managing cluster resources. Install or access it to visually inspect resources, view logs, and manage workloads.


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

☄️ Top 79 Linux commands that are commonly used in DevOps: ♾

1. ls: List directory contents
2. cd: Change directory
3. pwd: Print working directory
4. mkdir: Create a directory
5. touch: Create a file
6. cp: Copy files and directories
7. mv: Move or rename files and directories
8. rm: Remove files and directories
9. find: Search for files and directories
10. grep: Search for patterns in files
11. cat: Concatenate and display files
12. less: View file contents page by page
13.head: Display the first lines of a file
14. tail: Display the last lines of a file
15. vi/vim: Text editor
16. nano: Text editor
17. tar: Archive and compress files
18. gzip: Compress files
19. gunzip: Decompress files
20. wget: Download files from the web
21. curl: Transfer data to or from a server
22. ssh: Secure shell remote login
23. scp: Securely copy files between hosts
24. chmod: Change file permissions
25. chown: Change file ownership
26. chgrp: Change group ownership
27. ps: Display running processes
28. top: Monitor system resources and processes
29. kill: Terminate processes
30. df: Display disk space usage
31. du: Estimate file and directory space usage
32. free: Display memory usage
33. uname: Print system information
34. ifconfig: Configure network interfaces
35. ping: Test network connectivity
36. netstat: Network statistics
37. iptables: Firewall administration
38. systemctl: Manage system services
39. journalctl: Query the system journal
40. crontab: Schedule cron jobs
41. useradd: Create a user account
42. passwd: Change user password
43. su: Switch user
44. sudo: Execute a command as another user
45. usermod: Modify user account
46. groupadd: Create a group
47. groupmod: Modify a group
48. id: Print user and group information
49. ssh-keygen: Generate SSH key pairs
50. rsync: Synchronize files and directories
51. diff: Compare files line by line
52. patch: Apply a patch to files
53. tar: Extract files from an archive
54. curl: Perform HTTP requests
55. nc: Netcat - networking utility
56. wget: Download files from the web
57. whois: Lookup domain registration details
58. dig: DNS lookup utility
59. sed: Stream editor for text manipulation
60. awk: Pattern scanning and processing language
61. sort: Sort lines in a text file
62. cut: Extract sections from lines of files
63. wc: Word, line, character, and byte count
64. tee: Redirect output to multiple files or commands
65. history: Command history
66. source: Execute commands from a file in the current shell
67. alias: Create command aliases
68. ln: Create links between files
69. uname: Print system information
70. lsof: List open files and processes
71. mkfs: Create a file system
72. mount: Mount a file system
73. umount: Unmount a file system
74. ssh-agent: Manage SSH keys in memory
75. grep: Search for patterns in files
76. tr: Translate characters
77. cut: Select portions of lines from files
78. paste: Merge lines of files
79. uniq: Report or omit repeated lines


✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy & @devopsdocs 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

👉Continuous deployment as sumes that every product change or update is deployed automatically to production without any manual supervision from a DevOps engineer.

💡 Continuous Delivery:
- Automates the release process.
- Ensures readiness for deployment at any time.
- Allows manual deployment when needed.

💡 Continuous Deployment:
- Automates deployment of every successful code change.
- Directly deploys to production without human intervention.
- Requires high confidence in automated testing.


✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs

🔥Most Useful DevOps/Cloud GitHub Repositories to Learning and Become a DevOps Engineer ♾


1️⃣. DevOps Realtime Projects (Beginner to Experienced): Link

2️⃣. Into The DevOps of Every tools: Link

3️⃣. DevOps Setup-Installations Guides: Link

4️⃣. Roadmap to learn Kubernetes so easy: Link

5️⃣. List of Best DevOps Tools with Detailed: Link

6️⃣. End to End CI/CD Pipeline Deployment on AWS EKS: Link

7️⃣. Becoming a Kubernetes Administrator Learning path: Link

8️⃣. Azure All-in-one Guide: Link

9️⃣. Terraform: Deploy an EKS Cluster-Like a Boss!: Link

1️⃣0️⃣. All In one Buddle of Kubernetes: Link

1️⃣1️⃣. Kubernetes Dashboard with integrated Health checks: Link

1️⃣2️⃣. AWS Billing Alert terraform module: Link


♥️Credits: @NotHarshhaa ✅

❤️ Follow for more: @prodevopsguy

📌 https://harshhaa.hashnode.dev/series/aws-for-beginners

🔗 More DevOps Blogs : HERE

🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩🟩

Follow 🍩 Like 👍 Share 👍 Comment Your thoughts 💬

⭐️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy & @devopsdocs 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

📌 https://harshhaa.hashnode.dev/real-time-devops-project-deploy-to-kubernetes-using-jenkins-end-to-end-devops-project-cicd

🔗 More DevOps Projects : HERE

🔥🔥🔥🔥🔥🔥🔥🔥

Follow 🍩 Like 👍 Share 👍 Comment Your thoughts 💬

⭐️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy & @devopsdocs 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

🐬 Docker is a software platform that allows you to build, test, and deploy applications quickly.

𝗕𝗲𝘀𝘁 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗣𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 𝗳𝗼𝗿 𝗗𝗼𝗰𝗸𝗲𝗿
✔️ Always use a specific version for the base image for Dockerfile.
✔️Optimize your docker image by using a smaller base image.
✔️Specify the correct working directory in Dockerfile.
✔️Always use the .dockerignore fi…
✔️Copying package.json Separate from Source Code.
✔️Use non root user.
✔️Multistage build for production.
✔️Exposing port in Dockerfile.


✈️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy & @devopsdocs 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

8 FREE💲Udemy Docker Courses from Beginner to Professional 🚀

➡️ Beginners

🔵 Docker for the Absolute Beginner
➡️ https://lnkd.in/eSDNg-Xv

🟡 Docker Tutorial for Beginners practical hands on -Devops
➡️ https://lnkd.in/eTGeQ_dW

🩷 Docker Essentials
➡️ https://lnkd.in/edTFpFxY

🔴 Docker Before Compose - Learn Docker by Example
➡️ https://lnkd.in/eq3_w-7N

🟤 Learn Docker Quickly: A Hands-on approach to learning docker
➡️ https://lnkd.in/ededr6U2


➡️ Professional

🟢 Are You a PRO Series - Docker & Swarm Real Challenges
➡️ https://lnkd.in/em48h_qK

🔵 Docker Swarm Courses
➡️ https://lnkd.in/emr6AaK8

🔴 Building Application Ecosystem with Docker Compose
➡️ https://lnkd.in/eaa43R2f


📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

📣 New to DevOps? 📣

Here are the most widely used tools in the industry along with their official documentation:

➡️ Source Code Management:

1. Git: https://git-scm.com/docs
2. GitHub: https://docs.github.com/en
3. Bitbucket: https://lnkd.in/dA2PcM_w

➡️ Ticketing Tools:

1. Service Now: https://lnkd.in/d69yubJF
2. Jira: https://lnkd.in/dD_WcXFQ
3. Trello: https://trello.com/guide

➡️ Public Clouds:

1. AWS: https://lnkd.in/dMa9XpMa
2. Azure: https://lnkd.in/dBsJtZHy
3. GCP: https://lnkd.in/d3hmN-Jr

➡️ Containerization and Orchestration Tools:

1. Docker: https://docs.docker.com/
2. Kubernetes: https://lnkd.in/dZXfQEqW
3. Mesos: https://lnkd.in/dqzvzJhY

➡️ Deployment Tools:

1. Terraform: https://lnkd.in/dM46h2_D
2. Octopus: https://octopus.com/docs
3. Heroku: https://lnkd.in/dCDuwvcj

➡️ Testing Tools:

1. Selenium: https://lnkd.in/dTnFN8bT
2. Cucumber: https://lnkd.in/dpmD4A9C
3. Postman: https://lnkd.in/d3xERi6c

➡️ Build Tools:

1. Maven: https://lnkd.in/dfgBnrZj
2. Gradle: https://lnkd.in/dv6rQczZ
3. Ant: https://lnkd.in/dQgMsgef

➡️ Pipeline Tools:

1. Jenkins: https://lnkd.in/dPmA6-ff
2. TravisCI: https://lnkd.in/dxxFaK_X
3. Argo CD: https://lnkd.in/dK5eXbYi

➡️ Monitoring Tools:

1. Grafana: https://lnkd.in/dX5anVq9
2. Prometheus: https://lnkd.in/ddxjc9bV


🚀 Follow for more DevOps content, tips and tricks, and Hands-On Project Implementation.


🔵 Follow for more: @prodevopsguy