Solved AWS No machine types found. It might be necessary to choose another region or account

Status
Not open for further replies.

Pabs

Free User
Joined
Mar 31, 2022
Messages
6
Reaction score
3
My first problem is that I was not able to pick a machine type in US-EAST-1 it would give me this error "No machine types found. It might be necessary to choose another region or account.” so I tried a few times and picked other locations. To see what is going on. They locked my account because I kept picking different regions on the 3cx website. It looks like there are a lot of activities that happen in the background. This what caused the service limits on my aws account. My question is does 3cx service not work with N.Virginia US-EAST-1 because that is the only location that will not work for me. But that is the closes location to me. I follow the link below and follow all the steps correctly. I am just trying to get this working on N.Virginia US-EAST-1.

https://www.3cx.com/community/threads/no-machine-types-found.88004/
 
@Pabs
Hi, based on your description I can understand that after you put your credentials to the portal and you get to the next step this is when you get this error. Can you confirm this ?
Because by the time you get this, this means that based on the validation that happens with your Access Key ID and Secret access key, you cant spin up a machine there.
Now forget the portal, if you go to your AWS account, is this region enabled and you account has the following rights ? Check here :
https://www.3cx.com/docs/cloud-pbx-amazon-aws/

“Attach existing policies directly”. In “Filter policies” search for “ec2full”, select “AmazonEC2FullAccess” and “ServiceQuotasFullAccess”, and then click “Next”.

Can you spin up a Debian 10 instance on this region ?
 
@Pabs
Hi, based on your description I can understand that after you put your credentials to the portal and you get to the next step this is when you get this error. Can you confirm this ?
Because by the time you get this, this means that based on the validation that happens with your Access Key ID and Secret access key, you cant spin up a machine there.
Now forget the portal, if you go to your AWS account, is this region enabled and you account has the following rights ? Check here :
https://www.3cx.com/docs/cloud-pbx-amazon-aws/

“Attach existing policies directly”. In “Filter policies” search for “ec2full”, select “AmazonEC2FullAccess” and “ServiceQuotasFullAccess”, and then click “Next”.

Can you spin up a Debian 10 instance on this region ?
Thank you I will look into again as soon as I get my aws account back. Because Ive tried too many times changing regions to see if I was able to select an a ec2 at other rgions which coused a red flag. my aws account is temporarily disable by aws. The one I noticed was the "ServiceQuotasFullAccess" The one I missed. Maybe this is the reason why its not working. I am able to make a ec2 on east 1 with debian and SSH to it with no problems.
 
  • Like
Reactions: NikosT_3CX
Thank you I will look into again as soon as I get my aws account back. Because Ive tried too many times changing regions to see if I was able to select an a ec2 at other rgions which coused a red flag. my aws account is temporarily disable by aws. The one I noticed was the "ServiceQuotasFullAccess" The one I missed. Maybe this is the reason why its not working. I am able to make a ec2 on east 1 with debian and SSH to it with no problems.
check it out when you get your account back and let us know please.
But I dont believe your account is blocked because you changed regions in the Deployment Wizard, this cant block it because it just makes API Validations to regions based on your credentials, nothing more.
Its like being logged in to AWS and changing regions to check whats happening.
 
  • Like
Reactions: Jesse Factoria
check it out when you get your account back and let us know please.
But I dont believe your account is blocked because you changed regions in the Deployment Wizard, this cant block it because it just makes API Validations to regions based on your credentials, nothing more.
Its like being logged in to AWS and changing regions to check whats happening.
The "API Validations to regions based on your credentials" That put my account into suspension. I even got this email from aws before it got suspension. Each time I did this it sent aws an additional validation.


Dear AWS Customer,

Thank you for using Amazon Web Services!

You recently requested an AWS Service that required additional validation. Your request has now been validated for AWS Europe (Ireland) region(s). If you are still experiencing difficulty, please contact us at

Thank you for your patience.

—The Amazon Web Services Team

This message was produced and distributed by Amazon Web Services, Inc. and affiliates, 410 Terry Ave. North, Seattle, WA 98109-5210.
 
@Pabs please note that this is not possible.
I would recommend to check this further with AWS Support Team and they will be able to clear things more for you and your account.
 
@Pabs please note that this is not possible.
I would recommend to check this further with AWS Support Team and they will be able to clear things more for you and your account.
Thanks I am stilling waiting on amazon to get my account back. I am about to try it again with a new aws account.
 
  • Like
Reactions: NikosT_3CX
Hey everyone. I just want to update. I just ended up making a new AWS account because of 3cx api calls AWS locked my account. Few weeks later they gave my account back. I cleaned the whole account all the AWS services. I nuked the account. Still was not able to get my main AWS account to work with US-East-1. Just in other regions. I made a new AWS account and it worked.
 
  • Like
Reactions: NickD_3CX
Status
Not open for further replies.

Forum statistics

Threads
111,974
Messages
590,081
Members
164,899
Latest member
mazet