Wondering how to release Dedicated Hosts in EC2? We can help you with this!
As a part of our AWS Support Services, we often receive similar requests from our AWS customers.
Today, let’s see the steps followed by our Support Techs to help our customers to release Dedicated Hosts in EC2.
Release Dedicated Hosts in EC2
Before releasing the host we need to stop all the running instances within the host. We can continue to use these instances by migrating the instances to another Dedicated host in our account.
Now let see the methods to release the dedicated host:
- Using AWS console.
- Using AWS CLI.
- By using Powershell.
Using AWS console
Steps to release a dedicated host using AWS console:
- Log in to the AWS management console and then open the Amazon EC2 console.
2. Select the option Dedicated Hosts and then select the Dedicated Host to release.
3. Select Actions, Release host.
4. Click Release to confirm.
Using AWS CLI
We can use the release-hosts AWS CLI command to release a Dedicated host:
aws ec2 release-hosts --host-ids h-098a7654b1234clep
Using Powershell
We can use the Remove-EC2Hosts AWS Tools for Windows PowerShell command to release a Dedicated host:
PS C:\> Remove-EC2Hosts -HostId h-012a3456b7890cdef
Note: These above steps apply only to On-Demand Dedicated Hosts.
We can’t reuse the same host or host ID again and no longer charged On-Demand billing rates for it after releasing the Dedicated Host.
It can take some time for them to stop counting towards our limit If we have recently released Dedicated Hosts. At this time we might experience LimitExceeded errors when trying to allocate new Dedicated Hosts. So try allocating new hosts again after a few minutes, If this is the case.
The instances that were stopped are still available for use and are listed on the Instances page. They retain their host tenancy setting.
[Need help with more AWS queries? We’d be happy to assist]
Conclusion
To sum up, today we discussed the steps followed by our Support Engineers to help our customers to release Dedicated Hosts in EC2.
0 Comments