Skip to main content

What is the difference between terminating and stopping an EC2 instance?


Read this article to find out what are the differences between terminating and stopping an EC2 instance. This article is written by by well known DevOps trainer - Rajesh Kumar.

Answer

Terminate Instance

When you terminate an EC2 instance, the instance will be shutdown and the virtual machine that was provisioned for you will be permanently taken away and you will no longer be charged for instance usage. Any data that was stored locally on the instance will be lost. Any attached EBS volumes will be detached and deleted.  Read more click here
Reference:- This article was originally posted in scmGalaxy.com

Comments

  1. Fabulous information you have shared, I really like the way of your explaining. Look into this Devops Online Training for more info on Tool.

    ReplyDelete
  2. Thanks for this clear explanation — it’s exactly what I needed to finally grasp the real difference between stopping and terminating an EC2 instance! The way you broke it down into simple language, with practical implications like data persistence and cost considerations, makes it much easier to remember when each action is appropriate. I’ve definitely been caught off guard before by assuming “stop” and “terminate” were interchangeable, so this kind of breakdown is super helpful for both beginners and intermediate AWS users. I also liked that you explained how billing behaves in each case — that’s often overlooked but really important when managing cloud resources efficiently. One thing that could make it even more helpful would be a quick real-world example or a visual comparison table, but overall this is exactly the kind of AWS clarification content that saves people a lot of time and confusion. Thanks again for posting!

    ReplyDelete
  3. Thanks for explaining the difference between terminating and non‑terminating expressions — it’s a foundational concept in both math and computing. In general usage, a terminating sequence stops after a finite number of steps or digits, while a non‑terminating sequence continues indefinitely without a fixed endpoint. For example, in decimal numbers, terminating decimals have a definite end after a few digits, whereas non‑terminating decimals go on infinitely and may repeat or not repeat at all. Understanding this distinction helps when learning about number systems, algorithms, and how processes or loops behave in programming.

    ReplyDelete

Post a Comment

Popular posts from this blog

Rajesh Kumar, A DevOps Trainer

Rajesh Kumar has Total, Over 12 years of extensive experience in the Software Configuration Management domain having depth knowledge of DevOps, Continuous Integration and Delivery, Configuration Management, Build and Installer, Release Management and Application Management.Approach Test Driven DevOps Approach Continuous Integration Continuous Delivery Continuous Deployment Code Quality and Analysis Test Coverage and Matrix Technical Debt Reduction Cloud Migration in AWS Link -  http://www.RajeshKumar.XYZ Email - DevOps at RajeshKumar dot xyz Mobile - +91 7739774984

Top skilful Git Trainers in Bangalore | scmGalaxy

scmGalaxy is a leading source of Git trainers, mentors, consultants and coaches in Bangalore City. Our git trainers and mentors are highly skilful and expereinced in the area of DevOps and Automation. They provide online and classroom Git training in Bangalore. Along with Bangalore they provide Git training in Pune, Hyderabad, Mumbai, Singapore, UK ,USA, Netherlands, etc. Read more click here

DevSecOps: Paradigm shifts are messy, but someone’s got to take the lead

A perfect storm of factors brewing in the dev, ops, and security worlds have created a window of opportunity to embed security into the application delivery lifecycle, in a needle-moving kind of way. However, security teams need to be the ones driving the DevSecOps charge or that needle will barely wobble. Given how many security practitioners spend their days putting out fires, adding “DevSecOps evangelist” to their job description is more likely to elicit groans than spur the desire to innovate application security. As understandable as that may be, unless security teams can create the groundswell needed for DevSecOps to stick, then another paradigm shift in computing will occur in which security gets Read More Click Here Reference:- This article was published on BestDevOps.com