instance re-launch after termination

0

Hi,

I've got a r5a.large instance, which is not in use. when I'm trying to terminate the instance, different instance is being launced automatically. I read that it might be connected to EC2 Auto-Scaling (https://repost.aws/questions/QUE3qVZUzERzeFOzwMMe44gQ/a-new-ec-2-instance-is-created-after-termination-of-the-only-instance), but nothing appears in my console when I'm trying to follow instructions (cannot delete ant auto-scaling group, because I don't have one) (https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-process-shutdown.html).

please, help me terminate all EC2s.

Thanks, Adi

已提問 2 年前檢視次數 273 次
6 個答案
0

Hi All,

Thanks for your answers. unfortunately, in the "Auto Scaling Groups" page, I have no option as mentioned in the documentation (see first pic below)- only the option to create new auto scaling group, and I don't have any load balancers (second pic below). I also checked my spot instances, and made sure that I don't have any requests (third pic).

What else could it be? Thanks Again, Adi

Enter image description here Enter image description here Enter image description here

已回答 2 年前
0

Check the tags on your instance, are there any that start with aws:? Those would be created by an AWS service and might show what service is maintaining the capacity.

Alternatively, around the time the replacement instance is launched, look in CloudTrail and filter by:

  • EventName: RunInstances
  • EventName: CreateFleet

These are generally the 2 API calls used to create new EC2 instances, and it should say which service is making the API call

AWS
已回答 2 年前
  • Hi,

    Thanks for your answer. please check next post, with an additional information.

    Adi

0

Hi Shahad_C,

The Tags tab can be found above: Enter image description here

Moreover, it seems that the usage operation is RunIntances.

what should I do next?

已回答 2 年前
  • @rePost-User-9776128 - open the RunInstances call and check what the source is (is the call being made by another AWS service? By a script in your account?). That should tell you what the source of the launch is. Since it looks like this may be spot, there could be a persistent spot request as virshu mentioned

0

Hi

As you mentioned the autoscaling is causing that ,

Try to disable autoscaling attached to your load balancer

This is feasible in console ec2 > load balancer

已回答 2 年前
profile pictureAWS
專家
已審閱 2 年前
0

You can look at this document - https://docs.aws.amazon.com/autoscaling/ec2/userguide/as-enable-disable-scaling-policy.html

Look at the section "To disable a scaling policy (console)"

profile pictureAWS
專家
已回答 2 年前
0

Other than autoscaling, it could be a spot instance. If you have active spot request, it will launch another instance as well.

profile picture
virshu
已回答 2 年前

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南