Getting this AWS account currently does not support creating load balancers. For more information, please contact AWS Support.

im having the same issue as well, 72 hours from raising the ticket and still no respons efrom AWS

This message just means that your AWS account doesn’t have enough billing history with AWS to be auto-approved for the creation of Elastic Load Balancers (ELB).

Free Accounts and Billing Support should be able to help with this. https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/billing-get-answers.html#billing-support

yeah this is really annoying setting up a new client and I have to explain delays that don't even make sense to me the classic ones work fine its v2 btw. its been 3 days

The error message you're encountering suggests there might be a temporary issue with your account's ability to create load balancers. This could be due to several reasons:

1. Service Quota Limits: You may have reached the maximum number of load balancers allowed in your account for that specific region. AWS has limits on the number of load balancers you can create, and since you mentioned creating and deleting several ALBs during testing, you might have hit this limit.

2. API Throttling: If you've been creating and deleting load balancers rapidly, AWS might temporarily restrict your ability to create new resources to prevent service abuse.

3. Transient Service Issues: There could be temporary internal problems within the Elastic Load Balancing service or the underlying network.

Here are some steps you can take to resolve this issue:

1. Wait and Retry: Sometimes these issues are transient. Wait approximately 15 minutes and try creating the load balancer again.

2. Check Service Quotas: Verify your current load balancer limits in the AWS Service Quotas console to see if you've reached your account's limit.

3. Delete Unused Resources: If you have any unused load balancers or related resources, consider deleting them to free up capacity.

4. Different Region: Try creating a load balancer in a different AWS region to determine if the issue is region-specific.

5. Contact AWS Support: If the problem persists after trying the above steps, you should contact AWS Support as suggested in the error message. They can investigate account-specific issues and potentially increase your service quotas if needed.

Remember that when creating load balancers through the AWS CLI or SDK, you need to provide valid parameters such as proper subnet IDs and ensure you have the necessary permissions to create these resources.
Sources
Troubleshoot a Classic Load Balancer: API errors - Elastic Load Balancing
Elastic Load Balancing - Version 2 examples using SDK for Python (Boto3) - AWS SDK Code Examples