By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Account got suspended, changed credit card, instance does not start anymore

0

We had a problem with our credit card the account was disabled for 3 due payments. We added a new credit card, payed the 3 bills and the account came back after a few minutes. When we were changing the credit card, we got a message requiring us to change our tax address to Brazil. We have been using the sa-east-1a servers for years though.

The problem is that our instance does not start anymore. We did not change anything in the config we have been using for many years. It just says: Failed to start the instance [INSTANCE-ID] The requested configuration is currently not supported. Please check the documentation for supported configurations.

It gives no clues on what configurations might be invalid. EDIT: This is a 32-bit instance, but it has always been and we can't really upgrade without having the instance running.

From what we can tell, there is no availability problems. c3.large is available in sa-east-1a and I was even able to create a new c3.large instance with the new AMI image. I have tried many things.

  • Changing the instance config (nothing worked, tried all I could)
  • Making copy volumes and attaching to the new c3.large (no boot system found)
  • Making a new image from the current broken instance (does not install)
  • Using old images from the same instance (also do not install)

This has quickly become a nightmare. We can't work.

Topics
Management & GovernanceComputeCloud Financial Management
Tags
AWS ConfigAmazon EC2AWS Billing
Language
English
Tuca
asked 8 months ago256 views
1 Answer
0

You mention you're running c3.large - that isn't listed as a valid instance type https://aws.amazon.com/ec2/instance-types/#Compute_Optimized

When you say you've been using this instance for years, how many years? Is it so many years that it could have been running on EC2 Classic? EC2 Classic was retired on 23rd August, which sounds very much like the time around which your instance problems started.

Refer to the Updating Instance Types table at the foot of https://aws.amazon.com/blogs/aws/ec2-classic-is-retiring-heres-how-to-prepare/ where it advises migrating C3 instance types to C5.

profile picture
EXPERT
Steve_M
answered 8 months ago
  • Tuca
    8 months ago

    Thanks for your answer. Yes we were probably using EC2 classic (or maybe not, since we already have a VPC and everything was working yesterday), but c3.large still shows as available for my region (south america). I even created a new c3.large instance and it is running right now with a copy of my old volumes attached. It does not have a 32-bit option anymore though (and the old instance is i386). My problems started today, after the account was suspended. Up until yesterday it was working without problems. My guess is that it is not allowing me to run 32 bit instances anymore after the account was revived. EDIT: The c5 does not support 32-bit, which makes it not an option.

  • Steve_M EXPERT
    8 months ago

    That must be a coincidence about EC2 Classic being retired around the same time as your problem happened, especially as AWS says that no EC2 Classic instances have been running for a year. And yes, I can see c3.large is an option for provisioning in the EC2 Console if "all generations" is selected.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content