DevOps & Cloud (AWS, AZURE, GCP) Tech Free Learning

100 Terms & Services which every DevOps ♾ Engineer should be aware of: 1. Continuous Integration (CI): Automates code integration. 2. Continuous Deployment (CD): Automated code deployment. 3. Version Control System (VCS): Manages code versions. 4. Git: Distributed version control. 5. Jenkins: Automation server for CI/CD. 6. Build Automation: Automates code compilation. 7. Artifact: Build output package. 8. Maven: Build and project management. 9. Gradle: Build automation tool. 10. Containerization: Application packaging and isolation. 11. Docker: Containerization platform. 12. Kubernetes: Container orchestration. 13. Orchestration: Automated coordination of components. 14. Microservices: Architectural design approach. 15. Infrastructure as Code (IaC): Manage infrastructure programmatically. 16. Terraform: IaC provisioning tool. 17. Ansible: IaC automation tool. 18. Chef: IaC automation tool. 19. Puppet: IaC automation tool. 20. Configuration Management: Automates infrastructure configurations. 21. Monitoring: Observing system behavior. 22. Alerting: Notifies on issues. 23. Logging: Recording system events. 24. ELK Stack: Log management tools. 25. Prometheus: Monitoring and alerting toolkit. 26. Grafana: Visualization platform. 27. Application Performance Monitoring (APM): Monitors app performance. 28. Load Balancing: Distributes traffic evenly. 29. Reverse Proxy: Forwards client requests. 30. NGINX: Web server and reverse proxy. 31. Apache: Web server and reverse proxy. 32. Serverless Architecture: Code execution without servers. 33. AWS Lambda: Serverless compute service. 34. Azure Functions: Serverless compute service. 35. Google Cloud Functions: Serverless compute service. 36. Infrastructure Orchestration: Automates infrastructure deployment. 37. AWS CloudFormation: IaC for AWS. 38. Azure Resource Manager (ARM): IaC for Azure. 39. Google Cloud Deployment Manager: IaC for GCP. 40. Continuous Testing: Automated testing at all stages. 41. Unit Testing: Tests individual components. 42. Integration Testing: Tests component interactions. 43. System Testing: Tests entire system. 44. Performance Testing: Evaluates system speed. 45. Security Testing: Identifies vulnerabilities. 46. DevSecOps: Integrates security in DevOps. 47. Code Review: Inspection for quality. 48. Static Code Analysis: Examines code without execution. 49. Dynamic Code Analysis: Analyzes running code. 50. Dependency Management: Handles code dependencies. 51. Artifact Repository: Stores and manages artifacts. 52. Nexus: Repository manager. 53. JFrog Artifactory: Repository manager. 54. Continuous Monitoring: Real-time system observation. 55. Incident Response: Manages system incidents. 56. Site Reliability Engineering (SRE): Ensures system reliability. 57. Collaboration Tools: Facilitates team communication. 58. Slack: Team messaging platform. 59. Microsoft Teams: Collaboration platform. 60. ChatOps: Collaborative development through chat. ✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 New Article Alert! 🚀 Dive into The Ultimate Guide to DevOps Tools and Official Documentation 📘! Whether you're starting your DevOps journey or sharpening your skills, this guide covers essential DevOps tools with official documentation links, best practices, and pro tips for: ➡️ Source Control: Git, GitHub, GitLab ➡️ CI/CD: Jenkins, GitHub Actions, GitLab CI/CD, CircleCI ➡️ Configuration Management: Ansible, Chef, Puppet ➡️ Containerization: Docker, Kubernetes ➡️ IaC: Terraform, AWS CloudFormation, Azure Resource Manager ➡️ Monitoring: Prometheus, Grafana, ELK Stack Ready to level up your DevOps game? 🖥 Check out the full article here: The Ultimate Guide to DevOps Tools and Official Documentation

▶️ The Only Linux Command List You'll Need to Bookmark: ➡️Daily Heroes: • ps aux | grep {process} - Find that sneaky process • lsof -i :{port} - Who's hogging that port? • df -h - The classic "we're out of space" checker • netstat -tulpn - Network connection detective • kubectl get pods | grep -i error - K8s trouble finder ➡️Log Warriors: • tail -f /var/log/* - Real-time log watcher • journalctl -fu service-name - SystemD log stalker • grep -r "error" . - The error hunter • zcat access.log.gz | grep "500" - Compressed log ninja • less +F - The better tail command ➡️Container Whisperers: • docker ps --format '{{.Names}} {{.Status}}' - Clean status check • docker stats --no-stream - Quick resource check • crictl logs {container} - Raw container stories • docker exec -it - The container backdoor • podman top - Process peek inside containers ➡️System Detectives: • htop - System resource storyteller • iostat -xz 1 - Disk performance poet • free -h - Memory mystery solver • vmstat 1 - System vital signs • dmesg -T | tail - Kernel's recent gossip ➡️Network Ninjas: • curl -v - HTTP conversation debugger • dig +short - Quick DNS lookup • ss -tunlp - Socket statistics simplified • iptables -L - Firewall rule reader • traceroute - Path finder ➡️File Jugglers: • find . -name "*.yaml" -type f - YAML hunter • rsync -avz - Better file copier • tar -xvf - The unzipper (yes, we all google this) • ln -s - Symlink wizard • chmod +x - Make it executable ➡️Performance Profilers: • strace -p {pid} - System call spy • tcpdump -i any - Network packet sniffer • sar -n DEV 1 - Network stats watch • uptime - Load average at a glance • top -c - Classic process viewer ➡️Git Essentials: • git log --oneline - History simplified • git reset --hard HEAD^ - The "oops" eraser • git stash - The work hider • git diff --cached - What's staged? • git blame - The "who did this?" resolver ➡️Quick Fixes: • sudo !! - Run last command with sudo • ctrl+r - Command history search • history | grep - Command time machine • alias - Command shortcut maker • watch - Command repeater 📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

▶️ Bloated vs. Optimized Docker 🐬 Image Let’s talk Docker images – nobody likes them big and slow, right? I had an image that was 879MB (way too big!), and I got it down to 150MB. Here’s how I did it: [🔢] Multi-Stage Builds – Think of this like packing only what you need. You build everything in one stage, then copy over just the essentials to the final image. This keeps things simple and small. [🔢] Use Slim Base Images – I switched to node:14-slim, which has everything you need to run the app but without the extra stuff. It made a big difference. [🔢] Clean Up as You Go – I removed any files or packages I didn’t need after installing. Less clutter = smaller image! [🔢] Skip Dev Dependencies – For production, you only need what’s required to run the app, not to build it. So, I left out the development tools. [🔢] Try Alpine Images – If you’re looking to save even more, Alpine images are tiny. They need a bit more setup, but they’re worth it if you want to go super light.

Making Docker images smaller isn’t hard, and it’s worth it.

Faster builds, quicker deployments, and less storage needed. Give it a try!

📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

📢 Interview Prep Alert! A friend recently faced an interview with questions around microservices, Kubernetes, and DevOps practices. Sharing these questions to help everyone gearing up for similar roles! 🚀 Good luck on your journey, and let’s keep growing together! 🌟 🔹 Experience Level: 2+ years ➡️Questions Asked: ➡️ General Questions: - 📝 Describe your recent project and your roles & responsibilities. ➡️ AWS: 1. What are the components in ECS? 2. How to connect a Lambda function to the outside world? 3. How many Lambda functions can execute within a single account? 4. Scenario: An app is in a public subnet, and the database is in a private subnet. How does data flow between them? 5. What are API Gateways? ➡️ Terraform: 1. If resources already exist in the cloud, how do you configure them with Terraform? ➡️ Docker: 1. What are custom images in Docker? 2. Differences between CMD, RUN, and ENTRYPOINT. 3. Difference between ADD and COPY. 4. What are targets in Docker-Compose? ➡️Kubernetes: 1. How many microservices have you worked on? 2. How do microservices communicate with each other? 3. Types of network policies used for pod security. 4. How to handle sensitive data in microservices and retrieve it securely. 5. Scenario: Access a microservice via xyz.com with path-based routing. What configurations are needed? 6. What is pod affinity? 7. Difference between Deployment and StatefulSet. 8. Why use StatefulSets for databases instead of Deployments? 9. How does a Pod get assigned to a node? Hope this helps – let’s ace those interviews! 💪🔥 📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

📣 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. 🔵 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚨 kubectl Command: Behind the scenes! When you perform kubectl apply, Kubernetes executes a series of steps to manage the desired state of the resources defined in the provided configuration files. Here’s on what happens: 1️⃣. User issues the kubectl apply -f request. 2️⃣. The kubectl tool sends an API request to the Kubernetes API server to create or update the resource. 3️⃣. The server validates the user’s request. If all looks good, the server will write the new or modified resource into etcd. 4️⃣. The kube-controller-manager is a daemon that continually watches the kube-apiserver. 5️⃣. It will be notified of the new deployment and proceeds to create new pods to achieve the desired state through another call to the kube-apiserver. 6️⃣. Then we have kube-scheduler which is responsible for scheduling Kubernetes pods on worker nodes. 7️⃣. The kube-scheduler is then notified about the new pods that have been created and proceeds to determine which nodes are valid placements for the same. The scheduler’s primary task is to identify the create request and choose the best node for a pod that satisfies the requirements. 8️⃣. Finally, Kubelet is an agent component that runs on every node in the cluster that gets notified if a pod has been assigned to it. The assigned node then coordinates with the container runtime on the node to start the appropriate containers. ❤️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 DevOps Project - 31 🚀 🔗 Project Link: HERE ⏩ Building Scalable, Secure, and High-Performance Web Applications with AWS 3-Tier Architecture! 📈 In this project, I dive into setting up a robust 3-tier architecture on AWS designed to boost scalability, ensure high security, and optimize performance for modern web applications. 🛠 Project Highlights: ➡️ AWS VPC, Subnets, Security Groups for enhanced security ➡️ Auto Scaling and Load Balancing for scalability ➡️ Optimized performance with caching and database optimizations ❤️‍🔥 Share with friends and learning aspirants ❤️‍🔥

📣 Note: Fork this Repository 🧑‍💻 for upcoming future projects, Every week releases new Project.

📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 Ansible Commands Every DevOps Engineer Should Know 🚀 Ansible is a powerful tool for automation and configuration management. Here's a handy list of essential Ansible commands that will boost your productivity: 1. Check Ansible Version

   ansible --version
   

2. Ping All Hosts

   ansible all -m ping
   

3. Run a Command on All Hosts

   ansible all -a "uptime"
   

4. Use a Specific Inventory File

   ansible all -i /path/to/inventory -m ping
   

5. Run a Playbook

   ansible-playbook playbook.yml
   

6. Check Syntax of a Playbook

   ansible-playbook playbook.yml --syntax-check
   

7. List Hosts in Inventory

   ansible-inventory --list -i /path/to/inventory
   

8. Test a Playbook with Dry Run

   ansible-playbook playbook.yml --check
   

9. Encrypt a File with Ansible Vault

   ansible-vault encrypt filename.yml
   

10. Decrypt a File with Ansible Vault

    ansible-vault decrypt filename.yml
    

11. View Encrypted File with Ansible Vault

    ansible-vault view filename.yml
    

12. Edit an Encrypted File with Ansible Vault

    ansible-vault edit filename.yml
    

13. Create a New Vault Password File

    ansible-vault create vault-password-file
    

14. Run a Playbook with a Vault Password File

    ansible-playbook playbook.yml --vault-password-file /path/to/vault-password-file
    

15. Gather Facts About Hosts

    ansible all -m setup
    

16. Display All Modules

    ansible-doc -l
    

17. Get Documentation for a Specific Module

    ansible-doc <module_name>
    

18. Check the Status of a Service

    ansible all -m service -a "name=httpd state=started"
    

19. Copy a File to Hosts

    ansible all -m copy -a "src=/path/to/source dest=/path/to/destination"
    

20. Run a Task as a Different User

    ansible all -m command -a "ls -alh /home/user" -u username
    

Stay efficient and keep automating! 🛠✨ 🎄 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

▶️ How can you stand out as a DevOps Engineer? ⚡️Learn the skills that others avoid: ⚡️ Learn chaos engineering - Break things purposely in production - Implement resilience testing - Master failure injection ⚡️ Learn advanced observability - Go beyond basic monitoring - Implement distributed tracing - Master log correlation ⚡️ Learn GitOps workflows - Implement declarative deployments - Master reconciliation loops - Build operator patterns ⚡️ Learn platform engineering - Create internal developer platforms - Build self-service capabilities - Automate everything ⚡️ Learn cost optimization - Master FinOps practices - Implement spot instance strategies - Optimize resource usage ⚡️ Learn advanced Kubernetes - Custom controller development - Operator patterns - Multi-cluster management ⚡️ Learn infrastructure testing - Infrastructure unit tests - Integration testing for IaC - Compliance as Code ⚡️Most fall short here. ⚡️What else would you add? - SRE practices (SLOs, error budgets) - Advanced security scanning - Custom tooling development - API gateway patterns - Service mesh implementation - Advanced metrics collection - Automated documentation - Disaster recovery automation - Performance engineering - Backup/restore strategies

The key is focusing on the complex areas others avoid. Anyone can learn basic CI/CD, but mastering advanced patterns sets you apart.

📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 DevOps Automation with Shell Scripting! 🚀 🖥 Dive into the full article here: https://dev.to/prodevopsguytech/devops-automation-with-shell-scripting-1p69 Looking to automate routine DevOps tasks and boost your efficiency? Shell scripting is an essential tool for every DevOps engineer. Check out this comprehensive guide to learn: 🔹 Key Concepts in Shell Scripting 🔹 Automation Use Cases like monitoring, deployments, backups, and log management 🔹 Advanced Techniques to enhance your scripts 🔹 Best Practices for reliability and readability ❤️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

😀😀 10 DevOps Real time Scenarios. 😀😀 🚀 Issues as well as their resolutions: 🚀 🔢. Continuous Integration Pipeline Failure and its Resolution. 🔗 https://lnkd.in/g9nBb79u 🔢. Application experiences performance degradation and becomes slow during high-traffic periods and its resolution. 🔗 https://lnkd.in/g9nBb79u 🔢. Deployments are error-prone and inconsistent across different environments and its resolution. 🔗 https://lnkd.in/gE6FYcBz 🔢. The application goes down in production due to an unforeseen issue and its resolution. 🔗 https://lnkd.in/gE6FYcBz 🔢. A security vulnerability is discovered in a component of the application stack and its resolution. 🔗 https://lnkd.in/gPtZ9_Ge 🔢. Production environments start to deviate from their desired configurations over time and its resolution. 🔗 https://lnkd.in/gPtZ9_Ge 🔢. A critical service experiences an outage, impacting users and business operations and its resolution. 🔗 https://lnkd.in/gvTtGYC7 🔢. Communication breakdowns between development and operations teams lead to misunderstandings and delays and its resolution. 🔗 https://lnkd.in/gvTtGYC7 🔢. A major release causes unexpected issues in the production environment. 🔗 https://lnkd.in/gYbFKPrv 🔢🔢. Cloud resource costs are increasing beyond budgeted limits. 🔗 https://lnkd.in/gYbFKPrv 🎄 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!

☁️ AWS Cloud All End-to-End Content 2024 ⚡️ ➡️ This Includes: - All AWS Content - AWS Realtime scenarios - All AWS Exercises with solutions - No More AWS PDFs needed - Easy to Learn from anywhere - Detailed Explanation guide - All AWS services for DevOps Engineer 🖥 Link : https://github.com/NotHarshhaa/into-the-devops/tree/master/topics/aws 📱 Follow me on GitHub : https://www.github.com/NotHarshhaa 📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

Basic 📱 Git Flow in DevOps ♾ CI-CD! 1️⃣. Developer Creates Feature Branch: The developer creates a new feature branch and is used to work on a new feature or a specific task. 2️⃣. Developer Writes Code: The developer writes the necessary code for the feature in their local development environment. 3️⃣. Developer Commits Changes: Once the developer is satisfied with the changes, they commit the changes to the feature branch in the local Git repository. 4️⃣. Developer Creates Pull Request: The developer pushes the committed changes by creating a pull request to merge the feature branch into the main branch. 5️⃣. Code Review by Team: The pull request initiates a code review process where team members review the changes. 6️⃣. Approval of Pull Request: After addressing any feedback and making necessary adjustments, the pull request is approved by the reviewers. 7️⃣. Merge to Main Branch: The approved pull request is merged into the main branch of the Git repository. 8️⃣. Triggers CI/CD Pipeline: This automation ensures that the changes are continuously integrated and deployed. 9️⃣. Then we follow the procedure for building and testing the code, deploying to staging env. Once the tests in the staging environment pass, a manual approval is required to deploy the changes to the production environment. Once the code is deployed to production env, the prod env is monitored using Prometheus to track the performance and health of the application. The collected metrics are visualized using Grafana. Finally alerts are configured. ❤️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

🚀 Learn AWS DevOps from Zero! 🚀 🖥 Check it out here and kickstart your AWS DevOps journey: https://dev.to/prodevopsguytech/learn-aws-devops-from-zero-a-complete-beginners-guide-1gl2 Are you ready to start your journey into AWS DevOps? Whether you're a beginner or looking to strengthen your DevOps skills, this guide has you covered! 🌐 🔸 What’s Inside? - Core DevOps principles - Step-by-step setup on AWS - Comprehensive breakdown of essential AWS tools (CodeCommit, CodeBuild, CodeDeploy, CodePipeline) - CI/CD, IaC, security best practices, and more! 📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs

ahhh Fuck mee hard baby 💧💧💧💧💧

Will start uploading porn ❤️❤️ 💧