DevOps & Cloud (AWS, AZURE, GCP) Tech Free Learning
16K subscribers
1.33K photos
14 videos
501 files
1.28K links
https://projects.prodevopsguytech.com // https://blog.prodevopsguytech.com

• We post Daily Trending DevOps/Cloud content
• All DevOps related Code & Scripts uploaded
• DevOps/Cloud Job Related Posts
• Real-time Interview questions & preparation guides
Download Telegram
🐬 𝗗𝗼 𝘆𝗼𝘂 𝘂𝘀𝗲 𝗱𝗼𝗰𝗸𝗲𝗿? 𝗱𝗼 𝘆𝗼𝘂 𝗸𝗻𝗼𝘄 𝗮𝗯𝗼𝘂𝘁 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗹𝗶𝗳𝗲𝘁𝗶𝗺𝗲𝘀?

🗳 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 are designed to run individual applications or services in an isolated environment, so they can keep running until you decide to stop them.

𝗧𝘆𝗽𝗲𝘀 𝗼𝗳 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀 𝗯𝗮𝘀𝗲𝗱 𝗼𝗻 𝘁𝗵𝗲𝗶𝗿 𝗹𝗶𝗳𝗲𝘁𝗶𝗺𝗲𝘀:

𝟏. 𝐒𝐡𝐨𝐫𝐭-𝐥𝐢𝐯𝐞𝐝 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 :-
These containers are designed to perform a specific task or job and exit.
➡️ 𝐄𝐱𝐚𝐦𝐩𝐥𝐞 :- A 𝐃𝐨𝐜𝐤𝐞𝐫 container that runs a simple 𝐏𝐲𝐭𝐡𝐨𝐧 𝐬𝐜𝐫𝐢𝐩𝐭 and then exits.

𝟐. 𝐋𝐨𝐧𝐠-𝐫𝐮𝐧𝐧𝐢𝐧𝐠 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 :-
These containers are designed to run continuously for extended periods, hosting services or your applications. Examples include web servers, databases, or other services that need to remain operational as long as the application is running.
➡️ 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: A 𝐃𝐨𝐜𝐤𝐞𝐫 container running a basic 𝐍𝐠𝐢𝐧𝐱 𝐰𝐞𝐛 𝐬𝐞𝐫𝐯𝐞𝐫.

𝟑. 𝐈𝐧𝐭𝐞𝐫𝐚𝐜𝐭𝐢𝐯𝐞 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 :-
Containers can also be used interactively for debugging or testing purposes. In this case, the container may run as long as the user keeps the interactive session open.
➡️ 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: An interactive 𝐃𝐨𝐜𝐤𝐞𝐫 container for running a 𝐁𝐚𝐬𝐡 𝐬𝐡𝐞𝐥𝐥.

𝟒. 𝐎𝐫𝐜𝐡𝐞𝐬𝐭𝐫𝐚𝐭𝐞𝐝 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 :-
𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬 orchestrated 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 may be continuously monitored and automatically restarted if they fail or crash.
In these cases, the containers can run for a long time as they are automatically managed by the orchestrator unless interrupted externally.

𝟓. 𝐃𝐚𝐞𝐦𝐨𝐧 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬 :-
The last on this list are 𝐃𝐚𝐞𝐦𝐨𝐧 𝐂𝐨𝐧𝐭𝐚𝐢𝐧𝐞𝐫𝐬. Docker containers can be run as background daemons, serving a specific purpose and running as long as the system is active or until manually stopped.
➡️ 𝐄𝐱𝐚𝐦𝐩𝐥𝐞: A simple 𝐃𝐨𝐜𝐤𝐞𝐫 container running a monitoring tool like htop as a daemon.


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
𝗗𝗲𝘃𝗢𝗽𝘀 𝗥𝗼𝗮𝗱𝗺𝗮𝗽 𝟮𝟬𝟮𝟰 🚀


🔵 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
🟩 Ansible 🆓 Videos 🔴

🔗Link : https://drive.google.com/drive/folders/1p35HHSamOyL1Rta8hK5--4k1mPWYAXaV?usp=sharing


❤️ Follow for more: @prodevopsguy
Please open Telegram to view this post
VIEW IN TELEGRAM
🟩 🌐 Git/GitHub Free Videos:- 🟩

🔥 ➡️https://drive.google.com/drive/folders/1vhSsxz9oAtSh136JVo3gryaDPJAYWteF?usp=sharing

❤️ Follow for more: @prodevopsguy
Please open Telegram to view this post
VIEW IN TELEGRAM
➡️🐧 Linux Free Videos 🟩 :

Link: https://drive.usercontent.google.com/download?id=1MSo7Iwv0Xwe5bjg5fTcmjnxatULfhfLA&export=download&authuser=0


❤️ Follow for more: @prodevopsguy // Follow for DevOps DOCs: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
🔣 Developing applications in Kubernetes is complex and hard.

Managing resources , updating configurations and integrating with CI/CD takes up a lot of time and effort.

This is where the helm comes in. Helm simplifies the process of developing applications , automating the distribution of the application. Consider it similar to a package manager , the apt or yum of kubernetes.

🟡 Some of its use cases
- Versioning of application releases and rollbacks if necessary.
- Customize configurations and charts for different environments.
- Centralized package management.
- Simplify deploying and using applications in a standardized manner.


❤️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥 DevOps Project-11: Deploy Two-Tier Architecture on AWS using Terraform

🔗 Project Link: HERE
🔗 Detailed Blog Link: HERE

🔄 Project Overview :-
In the world of cloud computing, infrastructure as code (IaC) plays a pivotal role in automating the deployment and management of resources. This blog post provides a step-by-step guide on creating a Two-Tier architecture on AWS using Terraform. We’ll explore the essential services involved, ensuring high availability, security, and scalability for hosting a static website.

Also, we are adopting a modular approach with enhanced security measures. The infrastructure is organized into dedicated modules, ensuring a scalable, maintainable, and secure deployment.

❤️‍🔥 Share with friends and colleagues ❤️‍🔥

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


📱 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!
Please open Telegram to view this post
VIEW IN TELEGRAM
DevOps and Cloud Engineering is not just about learning tools. ☄️

🔣 Learn basic working blocks for the long run:

1️⃣. How does networking work?
➡️ Keywords: TCP/IP, DNS, HTTP/S, VPN, Load Balancers, Firewalls, Network Protocols, Subnetting

2️⃣. How to pick the right database?
➡️ Keywords: SQL vs. NoSQL, ACID Properties, Scalability, Data Modeling

3️⃣. Principles of secure system design
➡️ Keywords: Encryption, Authentication, Authorization, OWASP Top 10, Security Policies, Risk Assessment, Compliance Standards (like GDPR, HIPAA).

4️⃣. What are the different kinds of storage?
➡️ Keywords: Block Storage, Object Storage, File Storage, NAS, SAN, Cloud Storage (AWS S3, Azure Blob), SSD vs. HDD.

5️⃣. What are different kinds of DR (Disaster Recovery) strategies?
➡️ Keywords: Backup and Restore, Pilot Light, Warm Standby, Multi-site, RTO (Recovery Time Objective), RPO (Recovery Point Objective).

6️⃣. Common approaches for data replication
➡️ Keywords: Master-Slave, Peer-to-Peer, Synchronous vs. Asynchronous, Data Consistency, Replication Topologies, Log Shipping.

7️⃣. When to implement caching mechanisms?
➡️ Keywords: In-memory Caches (Redis, Memcached), CDN, Cache Invalidation, Write-through vs. Write-back Cache, Cache Hit Ratio.

Tools and frameworks will change. Fundamentals remain intact.

Without fundamentals, you are incomplete.



✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
What is Ansible →
➡️ Ansible is DevOps tool and it is similar like chef means it is a Configuration management tool let’s Begins with a Story → suppose you have a big organisation which have 100’s of servers Now a task is came to install git on that 100’s of servers …man responsible for doing this is System Administrator who is doing this manually which takes a lot of time…

guys!!!! we have that tool and that is Ansible→ A Configuration Management Tool…..
➡️ But !! But !! But !! First you need to connect all the nodes to ansible server which is done manually after that you will be able to automate the things…..
➡️ configuration management →It is a method through which we automate admin tasks.
➡️ It automates the task which the system administrator doing manually

Configuration management tool is of 2 types →
➡️ Pull based → In Pull Based it periodically check for the update from the main server to the nodes if update available it automatically install on the nodes connected with the server → chef and puppet is a pull based config tool.

➡️ Push based → In push based nodes is not going to the main server for the update the update is pushed to the nodes automatically for example the update of apps is pushed to your phone play store now it’s your choice whether you update or not → push based tool is Ansible when you need control in your hands so you take control of your own server for updating.

History of Ansible →
➡️ Michael Dehan developed Ansible in Feb 2012
➡️ Red Hat acquired the Ansible tool in 2015.
➡️ Ansible is available for RHEL, Debian, cent OS, Oracle Linux.
➡️ It is developed in Python background and also in Windows PowerShell.
➡️ You Can use this tool whether your server are in on premises or in the cloud.
➡️ It converted your code into infrastructure means you can say that it is a little bit called an Infrastructure building tool.


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
𝐋𝐢𝐬𝐭 𝐨𝐟 𝐟𝐫𝐞𝐞 𝐜𝐨𝐮𝐫𝐬𝐞𝐬 𝐭𝐨 𝐭𝐫𝐚𝐧𝐬𝐟𝐨𝐫𝐦 𝐘𝐨𝐮𝐫 𝐒𝐤𝐢𝐥𝐥𝐬: 𝐃𝐢𝐯𝐞 𝐢𝐧𝐭𝐨 𝐭𝐡𝐞 𝐖𝐨𝐫𝐥𝐝 𝐨𝐟 𝐃𝐞𝐯𝐎𝐩𝐬 & 𝐁𝐚𝐜𝐤𝐞𝐧𝐝 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞𝐬𝐞 𝐦𝐮𝐬𝐭 𝐭𝐫𝐲 𝐅𝐫𝐞𝐞 𝐂𝐨𝐮𝐫𝐬𝐞𝐬

🔢. 𝐏𝐲𝐭𝐡𝐨𝐧:
A scripting language used for automation in DevOps.
🔗 https://lnkd.in/gTEsX2VC

🔢. 𝐆𝐢𝐭:
Distributes version control system handles everything from small to very large projects with speed and efficiency.
🔗 https://lnkd.in/gFTyTWCC

🔢. 𝐂𝐥𝐨𝐮𝐝:
Its fair to say the rapid increament of startUps is revolutionised by the cloud technology.
🔗 https://lnkd.in/gf6_8RNG

🔢. 𝐌𝐢𝐜𝐫𝐨𝐬𝐞𝐫𝐯𝐢𝐜𝐞𝐬:
An approach of making a loosely coupled application.
🔗 https://lnkd.in/gYqdHCdF

🔢. 𝐒𝐞𝐫𝐯𝐞𝐫𝐥𝐞𝐬𝐬:
Allows developers to build and run applications without worrying about servers.
🔗 https://lnkd.in/g8knM8uE

🔢. 𝐋𝐢𝐧𝐮𝐱:
Probably the most famous primitive yet secure OS to use
🔗 https://lnkd.in/ghmZybpz

🔢. 𝐃𝐞𝐯𝐎𝐩𝐬:
An exploding domain to learn (It is an ecosystem that takes care of continuous integration, delivery, deployment and monitoring)
🔗 https://lnkd.in/g6ryYv8N

🔢. 𝐃𝐨𝐜𝐤𝐞𝐫:
Packages application along with dependencies and libraries required to run the application.
🔗 https://lnkd.in/ggaqmu8p

🔢. 𝐊𝐮𝐛𝐞𝐫𝐧𝐞𝐭𝐞𝐬, 𝐎𝐩𝐞𝐧𝐒𝐡𝐢𝐟𝐭:
Manages the deployment of an application and have autoscaling and autohealing capabilities.
🔗 https://lnkd.in/gsKYTciW

🔢🔢. 𝐌𝐲𝐒𝐐𝐋:
Relational Database Management System
🔗 https://lnkd.in/gbmjQcsD


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
1707116300601.gif
1.4 MB
🟡 𝗬𝗼𝘂 𝗠𝗨𝗦𝗧 𝗟𝗲𝗮𝗿𝗻 𝘁𝗵𝗲 🐧𝗟𝗶𝗻𝘂𝘅 𝗳𝗶𝗹𝗲 𝘀𝘆𝘀𝘁𝗲𝗺

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 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!
Please open Telegram to view this post
VIEW IN TELEGRAM
1711255043413.gif
2.3 MB
👾 CICD vs. CICD? You might be saying it wrong...

While CICD gets thrown around a lot, it actually refers to two separate practices that work together in the software development lifecycle: Continuous Integration (CI) and Continuous Delivery/Deployment (CD).

Here's a quick breakdown:

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 (𝗖𝗜): Automates the process of merging code changes from developers into a shared mainline frequently. This means every push triggers builds, tests, and catches bugs early on.

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆/𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁 (𝗖𝗗): Takes CI a step further. It automates the entire delivery pipeline, allowing you to release new features or bug fixes to production environments quickly and reliably. CD can include manual approval gates before deployment, while Continuous Deployment (CD) automates deployments entirely.

Here's the key difference:

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗹𝗶𝘃𝗲𝗿𝘆: Gives you a "deploy button" - the code is ready to be pushed to production with a manual go-ahead.

➡️𝗖𝗼𝗻𝘁𝗶𝗻𝘂𝗼𝘂𝘀 𝗗𝗲𝗽𝗹𝗼𝘆𝗺𝗲𝗻𝘁: Takes it a step further. If all automated tests pass in CD, the code is automatically deployed to production without human intervention.


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
💥 May the spirit of Holi bring you happiness. The warmth of Holi brings you joy, and the joy of Holi brings you hope. We wish you a joyous Holi! 💥

May this Holi be filled with fun, joy and love. Happy Holi 2024!


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
🌐 GitOps Workflow - Simplified Visual Guide

➡️ GitOps brought a shift in how software and infrastructure are managed with Git as the central hub for managing and automating the entire lifecycle of applications and infrastructure.

➡️ It's built on the principles of version control, collaboration, and continuous integration and deployment (CI/CD).


✔️ 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
🔔 DevOps AWS (Freshers) Job opportunity

➡️Job Title: DevOps AWS (Freshers)
➡️Location: Hyderabad
➡️Company: RJAY technologies Pvt Ltd
➡️Job Type: Full-time

➡️Job Description:
We are seeking a highly motivated and enthusiastic individual to join our team as an AWS DevOps Engineer.


➡️ Required Skills:
AWS, Docker, kubernetes, Ansible,Linux,Shells Scripting, Python, Jenkins, CI/CD, Git/GitHub


✉️ To apply, please submit your resume to sreeja.k@rjaytechnologies.com


✈️ 𝐅𝐨𝐥𝐥𝐨𝐰 @prodevopsguy 𝐟𝐨𝐫 𝐦𝐨𝐫𝐞 𝐬𝐮𝐜𝐡 𝐜𝐨𝐧𝐭𝐞𝐧𝐭 𝐚𝐫𝐨𝐮𝐧𝐝 𝐜𝐥𝐨𝐮𝐝 & 𝐃𝐞𝐯𝐎𝐩𝐬!!! // 𝐉𝐨𝐢𝐧 𝐟𝐨𝐫 𝐃𝐞𝐯𝐎𝐩𝐬 𝐃𝐎𝐂𝐬: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM
🔥 AWS DEVOPS REAL-TIME DEPLOYMENT

Development → Pre-PROD → Production

🔗 Detailed Project Explanation with Screenshots : https://harshhaa.hashnode.dev/aws-devops-real-time-deployment-dev-pre-prod-production

🔗Project Source code: https://github.com/NotHarshhaa/AWS-DevOps_Real-Time_Deployment


🎄 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!!
Please open Telegram to view this post
VIEW IN TELEGRAM
☁️ 𝗔𝗪𝗦 𝗵𝗮𝘀 𝗼𝘃𝗲𝗿 𝟮𝟬𝟬 𝗳𝘂𝗹𝗹𝘆 𝗳𝗲𝗮𝘁𝘂𝗿𝗲𝗱 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀.
𝗠𝗼𝘀𝘁 𝗶𝗺𝗽𝗼𝗿𝘁𝗮𝗻𝘁 𝗔𝗪𝗦 𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 𝘆𝗼𝘂 𝘀𝗵𝗼𝘂𝗹𝗱 𝗹𝗲𝗮𝗿𝗻 𝘁𝗼 𝗯𝗲 𝗮 𝗗𝗲𝘃𝗢𝗽𝘀 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿.

✔️Amazon EC2
✔️AWS IAM
✔️AWS CloudFormation
✔️AWS CloudWatch
✔️AWS CodePipeline
✔️AWS CodeBuild
✔️AWS CodeDeploy
✔️Amazon ECS
✔️AWS Lambda
✔️AWS Elastic Beanstalk
✔️Amazon DynamoDB


😎 𝗙𝗼𝗹𝗹𝗼𝘄 @prodevopsguy 𝗳𝗼𝗿 𝗺𝗼𝗿𝗲 𝘀𝘂𝗰𝗵 𝗰𝗼𝗻𝘁𝗲𝗻𝘁 𝗮𝗿𝗼𝘂𝗻𝗱 𝗰𝗹𝗼𝘂𝗱 & 𝗗𝗲𝘃𝗢𝗽𝘀!!! // Join for DevOps DOCs: @devopsdocs
Please open Telegram to view this post
VIEW IN TELEGRAM