AWS - Shared, Dedicated Instances & Dedicated Host Differences - EC2 Tenancy Models

AWS – Shared, Dedicated Instances & Dedicated Host Differences – EC2 Tenancy Models


shared and dedicated hosting

This video tutorial explains you the difference between:
– Shared Instances,
– Dedicated Instances and
– Instances on Dedicated Hosts.

Don’t remain confused anymore. Happy learning.

ERRATA below —

5:05 – Instances from other customers or shared instances (from you) can’t sit on this physical host

7:48 – You need to pay for the full physical host, as you are blocking the full host.

~~~~~~~~~~~~~~~~~~~~~~~~~~~
UPDATE May 2017:

There is a change which happened in May 2017 as I am able to find out. Please refer following links to read further:

(LAST PAGE of PDF)

In May 2017, AWS declared that your application could be HIPAA complied even when you run it on Shared instances (you don’t necessarily need Dedicated instances anymore for HIPAA compliance). Post this, the other restriction has been dropped. Now, shared instances in your account can run on the host where your dedicated instance is running.

Earlier the isolation was from 2 things:
1. Instances of other AWS account
2. Instances which are not dedicated instances.

———————————————————–

I would request to look at our playlists to learn systematically for AWS Certifications —
Solutions Architect –
&&&
SysOps Administrator –

++++++++++++++++++++++++++++++++++++++++

I have answered lot of AWS Interview questions in LIVE sessions here —

Connect with me on LinkedIn to read interesting AWS updates & Practical Scenario Questions —

Don’t miss any updates, please follow my FB page
&
Twitter –

And for AWS exercises & case-studies, you can refer our blog —

++++++++++++++++++++++++++++++++++++++++

48 thoughts on “AWS – Shared, Dedicated Instances & Dedicated Host Differences – EC2 Tenancy Models

  1. Really nice video. The difference between dedicated hosts and dedicated instances is explained very well.
    Dedicated instance means on instance restart its host can change. however, at any point in time, the host will have instances from the same AWS account.
    Dedicated host means that on instance restart its host will always remain the change. This is useful if you have hardware (CPU, MAC) bound licenses wherein you need the same host machine to apply the license.

  2. Excellent explanation!! however, I need one clarification. Does instance store-backed volumes get recovered for dedicated host upon stop and start or recovery is not supported for instance store even for dedicated host?

  3. This is amazing, all your videos on this channel are very informative sir, please keep going in this way, best of luck to you and your team❤️

  4. Well explained …thanks..Just for my confirmation…
    In Dedicated Instance the underlying hardware is fixed for that particular AWS account/customer but other Ec2 instances from the same account which is not dedicated i.e., shared can be hosted on the same underlying hardware.. is this understanding correct .. please confirm

  5. In case of dedicated Instance, If I stopped and start again the EC2 may launch in different Host.. right? So in that case If I have 2 Dedicated Instances and I just stopped 1 Instance and start again, I might have 2 Instance in 2 different Host and In these 2 host no one can launch their instances.. right? So, here we are blocking the host environments although we are not using in full capacity…Please clarify

  6. based on what u said, something does not add up for Dedicated Instances.

    Let's say if I have created a dedicated instance on H-105. I will not have any other customers creating any dedicated instance inside H-105. this would be reserved for me.

    Even though this dedicated instance is capable of created more instances I decide not to create any other dedicated instance and just go with 1 dedicated instance. Isnt Amazon losing on money and isnt the extra memory and CPU being un-used here? why would Amazon do that?

  7. There isn't much difference bw dedicated instance and dedicated host.
    We pay full block price for both.
    Only advantage of dedicated host is licence part.
    Is that right?
    Please correct me if i m wrong

  8. Thanks for the clear differentiation. However my understanding is that in the Dedicated instance scenario in the above example where its being launched in H-105 i believe other non-dedicated instances of the same customer/AWS account can run along with the Dedicated instance. Your statement mentions that H-105 can only run other Dedicated instances alone. Please confirm if my understanding is correct.

  9. Thanks for these amazing videos. I am new to cloud development and I had a basic question about dedicated hosts. Is it possible to have two different EC2 instances one of Windows type and another of Linux type on the same dedicated host?

  10. dedicated instances is not correctly explained.
    Dedicated Instances are Amazon EC2 instances that run in a VPC on hardware that's dedicated to a single customer. Your Dedicated instances are physically isolated at the host hardware level from instances that belong to other AWS accounts. Dedicated instances may share hardware with other instances from the same AWS account that are not Dedicated instances.
    reference – https://aws.amazon.com/ec2/pricing/dedicated-instances/

  11. If I only have 1 instances and I reboot then it may go to other host or other hardware . But If I have 5 instances and 4 are running so I am blocking a host as a dedicated instances and I I reboot one instances then what will happen ? It will move to other hardware or it will be on the same hardware ?

  12. thanks for clear explanation . one quick question , based on explanation , dedicated instance indirectly running dedicated host But only change that when dedicated instance reboot ,aws may choose different host machine .. Indirectly you are paying for dedicated host only difference is that during dedicated instance it may come on different host machine

  13. What will happen to dedicated instances stop/start and reboot & dedicated host stop/start and reboot.
    Will the instances resides in the same hosts even after reboot? am not getting this alone. Please clarify. Thanks

  14. I have read from AWS documentation that Dedicated instances may share hardware with other instances from the same AWS account that are not Dedicated instances.does it means dedicated instance can share hardware with different tendency models from the same AWS account?
    If different tendency models from the same AWS account can share the same hardware then does this case apply on the dedicated host as well?

  15. If I've instance A, B & C on dedicated instances, and I want to stop and start instance B only, then will happens? is that going to be same underlying hardware else it's going to move remaining instances to new hardware..?

  16. So, if I understand well, when a dedicated instance is allocated it can cause a lot of waste of resources. If I don't have any other on-demand instance running using the resources remaining, it will still not using by anyone. Do you have an ideia about how AWS deal with this possible waste?

  17. So dedicated host at 4:50 is the only host in the machine/hardware And no other host from another customer account will rest on that machine/hardware. Start stop will be same instance, but not same machine/hardware. AND 6:20 dedicated instance, will be same instance along with machine/hardware. Got it! For compliance purposes mostly….

Leave a Reply

Your email address will not be published. Required fields are marked *