I received an email from amazon aws
EC2 has detected degradation of the underlying hardware hosting your
Amazon EC2 instance (instance-ID: i-xxxxxxxx) associated with your AWS
account (AWS Account ID: xxxxxx) in the us-west-1 region. Due to this
degradation your instance could already be unreachable. We will stop
your instance after 2021-05-28 04:00:00 UTC. Please take appropriate
action before this time.
the instance itself is working fine at the moment but this email doesn't sound friendly.
what am i supposed to do this point. we are using docker and node on this instance.
Stopping the instance then starting the instance should migrate the VM off the degraded hardware. Note that you shouldn't "reboot" or "restart" it. You need to full stop, then start it.
https://aws.amazon.com/premiumsupport/knowledge-center/ec2-linux-degraded-hardware/
Related
I got the mail from Amazon regarding my EC2 as follows:
EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: xxxxxxxx) associated with your AWS account (AWS Account ID: xxxxxx) in the ap-south-1 region. Due to this degradation your instance could already be unreachable. We will stop your instance after 2020-12-29 22:00:00 UTC. Please take appropriate action before this time.
The affected instances are listed below:
xxxxxxx
So what would I do now to keep my data safe ?
AWS provides guides on what to do when an instance is about to be retired:
What do I need to know when my Amazon EC2 instance is scheduled for retirement?
The easiest way would be to stop/start the instance:
You are required to stop and then start the instance at your preferred time before the instance retirement date. Stopping and starting the instance moves the instance to another healthy host.
However, exact details depend on your instance type (e.g. EBS based or instance store based), thus please read the guide in the link provided to understand your options which are mostly determined on your actual EC2 instance setup.
On the personal health dashboard in the AWS Console, I've got this notification
EC2 persistent instance retirement scheduled
yesterday which says that one of my ec2 instances is scheduled to retire on 13th March 2019. The status was 'upcoming' while the start and end times both were set to 14-Mar-2019.
The content of the notification starts with:
Hello,
EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: i-xxxxxxxxxx) associated with your AWS account (AWS Account ID: xxxxxxxxxx) in the xxxx region. Due to this degradation your instance could already be unreachable. We will stop your instance after 2019-03-13 00:00 UTC.
....
I've got yet another notification today for the same instance and with the same subject line but the status has been changed to 'ongoing' and the start time is 27-Feb-2019 while the end time is 14-Mar-2019.
I was planning to do a start-stop of the instance next week but does the second notification tell me to do is ASAP?
Yes, it is better to do stop/start ASAP. Even in your message it says:
Due to this degradation your instance could already be unreachable
What is AWS EC2 Bundle Tasks?
Could any one please help me to understand what it is?
And any one help in showing a sample demo of it by steps or screenshot?
In the old days, before Amazon Elastic Block Store (Amazon EBS), Amazon EC2 instances were booted from Instance Store.
Instance Store is a disk that is directly connected to the host computer, which means that when an instance is turned off, the contents of the disk is lost (because the disk will be assigned to the next user who uses a Virtual Machine on that host).
This also meant that instances could not be stopped and started again, because the boot disk is lost.
These days, Amazon EBS provides network-attached storage, which persists even when an instance is stopped (and, if desired, even after an instance is terminated).
According to this article, Bundle Tasks is/was a process designed to get a Windows instance ready for booting from Instance Store:
See: Bundle Tasks in Amazon | Zeeshan Ali Shah's Blog
There is little reason to use this process these days.
I have a EC2 instance which my KOPS cluster is running. I observed that when the instance is stopped and started another day, the cluster starts itself automatically.
Does it mean that when EC2 instance is stopped, it goes into a state like 'Hibernate' Or KOPS has its own mechanism - like disaster recovery - and resilience when the host machine is down and up ?
Instances are just a normal part of the AWS infrastructure. When EBS is used for storage, data is not lost when instance is stopped, hence when you restart your instances they are brought up with the same state stored on EBS drives. This is not an explicit "hibernation" mechanism, nor is it a particularly specific feature of kops, it's just a regular data retention of data stored on AWS EBS.
I am running amazon AWS ECS container which creates one single instance of EC2. I made sure that it is 1 instance when I created ECS.
My issue is that I have another instance running in EC2 and amazon has sent me an email that I am using double of the free quota and will be charged.
But I am not sure why this second EC2 instance is coming from.
I have terminated it many times but it is recreated. When I terminate it, this is the prompt i receive which advises me that it is created from EBS but there is no app in EBS
On an EBS-backed instance, the default action is for the root EBS volume to be deleted when the instance is terminated.
Storage on any local drives will be lost.
This name of the instance is.
ECS Instance - amazon-ecs-cli-setup-ecs-cricketscorer
Please help.
check if you have any Auto Scaling Groups that you do not recognize. It is most probably being created because of it. If not, change your account password and deactivate/delete your existing AccessKeys.