- Newest
- Most votes
- Most comments
Hello, I got a response from support, if this is a brand new account this is happening because you don't have a billing history, only after this has been established will you be auto-approved for ELB creation.
My advice is to start using the service for other portions of your application so that there is some activity on the account which results in a bill, or continue to wait for support to respond. In my case I bumped up my support plan and opened a new ticket with a higher criticality so they would respond in 12 hours.
answered a year ago
Hello,
Sorry to hear about this delay in support.
I've passed these sentiments to our team within your support cases. Please keep an eye there for updated correspondence. We appreciate your patience as our team works to help provide you with next steps.
You can access your open cases, here: http://go.aws/support-center.
— Ann D.
This error message is common for new AWS accounts and can occur for several reasons. Based on your description, here are the likely causes and potential solutions:
Possible causes:
- Account Activation: Even though your account appears fully activated, some AWS services may take up to 24 hours after activation to become fully available.
- API Throttling: AWS might temporarily restrict your ability to create certain resources (like load balancers) for new accounts to prevent service abuse.
- Service Quota Limits: While unlikely for a new account, there could be region-specific limitations.
- Transient Service Issues: There might be temporary internal problems with the Elastic Load Balancing service.
Steps you can try:
- Wait and Retry: Sometimes these issues resolve themselves after 24-48 hours for new accounts.
- Try a Different Region: Attempt to create the load balancer in a different AWS region to see if the issue is region-specific.
- Check for Unused Resources: Ensure you don't have any hidden load balancer resources in other regions.
- Continue with Support Case: Since you've already opened a case with AWS Support, they should eventually help resolve this. Unfortunately, response times for Basic Support can vary, especially for account-specific issues.
This appears to be a known issue with new AWS accounts. The fact that you previously experienced a similar problem with CloudFront that was resolved after contacting support suggests this is likely an account-specific restriction that needs manual intervention from AWS.
In the meantime, you can continue working with other AWS services that are functioning correctly while waiting for your support case to be addressed.
Sources
Load balancer creation error | AWS re:Post
Getting this AWS account currently does not support creating load balancers. For more information, please contact AWS Support. | AWS re:Post
AWS Free tier account -Not sure why create load balancer gives | AWS re:Post.
Account Activation: The account has been active for over a week. CloudFront was initially blocked as well, but that was resolved by AWS Support, which confirms the account is fully activated.
API Throttling / Abuse Prevention: I’ve only tried to create one ALB (no high-frequency calls or automated retries), so throttling isn’t relevant here.
Service Quota Limits: The service quotas page shows default limits available for Elastic Load Balancing, and I’m well below any limit.
Transient Service Issues: The issue persists consistently across days and sessions, in both Console and CLI, so it’s definitely not transient.
To reiterate, this seems to be a new-account restriction specific to ALB creation, similar to what happened with CloudFront earlier, that issue required AWS Support intervention to fix.
Unfortunately, Support hasn’t responded to my open case for several days now, even though the stated SLA for basic support is 24 hours.
It would be great if someone from the AWS team could review or escalate this case, as I’ve already confirmed that all standard activation and configuration steps are complete.
I'm experiencing the same issue here.
- Account activation: account was created about 3 weeks ago.
- API Throttling / Abuse Prevention: first time creating and NLB, tried in CLI and console, and both returned the same error.
- Service quota limite: first resource creation, so I'm well below any limite.
- Transiente service issue: this error is occurring for days. Support did not respond to this issue. Does anyone get a conclusion on how to solve this?
answered 8 months ago
I’m experiencing a similar issue, and I haven’t received a response from support since last week. I’ve also tested this in different regions, but the problem persists. I would greatly appreciate any guidance or assistance in resolving this matter, as it’s affecting my use of AWS services!
answered a year ago
For an immediate resolution, we can switch to different AWS region and try creating the ALB, it works. Thanks
answered a year ago

I am having the same issue as well terrible service. and ofc I don´t want to pay for a service when it is an error in ther platform
Did you manage to resolve this issue? I'm experiencing the same thing currently on a new account, pretty frustrating.
Also interested. Been battling this since last week in us-east-2. No response from AWS support either.
I have a similar problem. I submitted a support request(176184821200206), but it’s been about 10 days with no response. The issue was fixed automatically at one point (I’m not sure how), but it came back later. I’ve updated my support request and am still waiting for a reply. It’s quite disappointing to have to wait this long, even with the Basic Support Plan. It seems like the Basic Support Plan isn’t working as expected.
I'm having the same problem. No solutions up to now.