I created a spot instance request with my custom AMI (based on Amazon Linux AMI, EBS backed.) When my request was fulfilled, I have another spot instance request created by itself with amzn-ami-pv-2015.09.0.x86_64-ebs (ami-50978202) as AMI with the same bid pricing as the one I created. I didn't really pay attention at the time and since my bid was low ($0.005 per hour) and I only used it for a couple of hours, so I didn't pay attention to it that much.
When I terminated the instance and cancel the request (both the one I created and the one that creates itself,) a new spot instance request with ami-50978202 keeps creating itself no matter how many times I keep canceling it and terminate the instance that was fulfilled. I thought it was because I still have the custom AMI on my account so I tried copying the AMI to another region, but the spot instance creating itself doesn't happen in that region, so I'm quite lost with what's happening here. Any help would be appreciated.
I had the same issue, cancelling the spot instance would just have it recreate.
At the time of speaking though (2011-12-11) there's an option within EC2 -> Spot Requests which looks like a blue speech bubble. Click on that and use the new version.
From there I've been able to cancel the spot request. I just lodged a support ticket asking for a refund for time not used.
This isn't going to solve your problem but I can confirm that I'm having the exact same issue and I haven't been able to get Amazon to fix the problem all week. It started when I used their new spot instance request system on November 7th. I'm assuming that the system has a bug in it that causes the spot request (not just the instance) to recreate itself. I haven't had problems like this before when creating a spot request. Amazon also thought that I was using an Auto scaling group but I've never set that up either.
The problem is now, trying to get Amazon to respond to this problem. I've opened multiple tickets. They have only responded one time in a week. At least they gave me a $12 refund for the time used by the spot instances so far. :-(
If you didn't create an ASG (as Zoran mentioned) you probably created a persistent spot request:
If the request is a persistent request, the request is opened again after your Spot instance is terminated.
Simply cancel the open spot request if you don't want it.
I confirm the answer of #Naypam is the correct one.
I had exactly the same behaviour than #user1274757, #Naypam and #deltaray:
created a persistent spot request.
upon cancelation of the "Spot request" from the AWS Web Console by selecting the spot request and pressing the "Cancel" Button:
The Spot request is cancelled,
a fews minutes later, a new Spot Request is automatically recreated with a new "Request ID" and a new creation timestamp.
This is most probably a bug on the AWS Console.
The work around is the following:
On the Web AWS Console, select "Instance > Spot Request"
Select the "New Spot Request Console" by clicking the blue bubble on the top-right toolbar and clicking on the "try it out" link that appears.
Select the spot request
Selection Actions > Cancel Spot Request.
The Spot Request is then really cancelled.
I Have open a case with Amazon and i invite you to do the same.
Related
Is there any solution or way, which can help me to get live/real-time logs?
I have 100s of Spot instances that come and go frequently, So we need to configure a setup that captures the logs despite this spot life cycle, which means whenever new spot instance launches we will get the respective instance to log immediately.
please help/suggested the way.
I would like to use AWS EC2 spot requests for machine learning that I do in spots.
If you don't configure any settings for spot requests, they will be set to "fleet" and an EC2 instance will be created that cannot be paused (it can only be terminated).
If you know how to create an instance with a spot request that can be paused, please let me know.
Spot instances launched in a fleet can’t be paused or stopped. To stop a Spot instance, it must be launched by a Spot instance request for a single instance, you can create such requests using Launch Instance wizard, you may follow steps at this link. Make sure to select "Persistent request" in the wizard.
This request will launch a Spot instance that can be Stopped but still can’t be Paused. Hibernate/Pause option is only available as a behavior at the event of interruption and can't be requested by the user.
I'm trying to stay within the limits of my free tier, however, I notice I am being charged ~$1.50 a day for something, I don't know what.
I've terminated all my instances, yet the bill keeps ticking up every day.
I've also deleted all my security groups, route-tables, nat-gateway, subnets and vpc, everything I can think of. Something is still there creating charges though.
How can I get a list of all the objects still hanging around?
You can add a support request to AWS, there are very responsive to the requests. I had a student account on AWS and some Fargate charges were added to my account. I opened a case and submitted a ticket in the support centre. They responded quickly with the reason why my charges were occurring and also gave me $20 USD credit for that month. Also, you can check if Termination protection is enabled in any of your stack in CloudFormation. It stops your instances from being deleted.
you can contact aws support centre for more info. after deleting all instances and other services wait for 24-48 hour. it will be reflected in billing after that much amount of time.
you can go inside cloud formation and delete all stack if any one is there and check for all region.
also if you created load balancer delete it manually it will be not deleted with EC2 instances.
I have been struggling with this since last 2 days - A. Trying to create AWS Spot Instance with Deep Learning AMI for Linux (free).
B. Upon launching EC2 Instance it says Spot Instance request successfully created but it fails to create the instance.
C. Using Spot Fleet role, and later have been trying to change it to provide Admin access to this role through Policies.
However, the instance is never created and in the History tab I see Event Type = fleetRequestChange goes from Submitted, active, cancelled_terminating within a minute and later cancelled.
I have been reading through its documentation but don't see a reason for it to fail. Verified the Region and AMI as well. Tried changing bid price and with default recommended option as well. But nothing seems to work.
This is the link I'm referring - AWS setup for Deep Learning
Please skip the initial portion of getting credits and you can directly jump to EC2 instance configuration setup.
Kindly help! I am unable to proceed for the past 2 days.
Thank you!
It worked perfectly fine for me.
Launched the Deep Learning AMI (ami-df77b6a7) in the Oregon region
Spot pricing as documented in the article you referenced
I could ssh into the instance after it launched
One thing you could check... Click the Limits link in your EC2 console to confirm that you can launch this type of instance.
Mine said:
Running On-Demand g2.2xlarge instances: 5
I have an instance that I have never actually launched myself that tends to start each time once I terminate it. This is annoying, as I would need to pay for it and customer service does not reply. Had anyone got a similar question before?
With the aid of help of the Amazon Support the problem was resolved. It appears that is you have an instance constantly appearing after being terminated and you have no active Autoscale groups, you should cancel it via the new Spot console (beta, the one you access via "Try it out" button), as most likely it is the fleet instance. I'll leave it here in case it is helpful to the others having the same issue.