What's wrong with Amazon Web Services?
My first post.. I cannot seem to get an answer from the AWS forum, so let me ask here to see any other hackers have the answer.<p>I am a new Amazon Web Services user, so maybe I'm missing something, but the quality of AWS seems really bad. I'm only able to start one machine instance and one persistent volume (i.e., Amazon EBS). According to the documentation, I should be able to start 20 instances and create 20 EBS volumes. Is this because amazon.com is overloaded with Michael Jackson traffic (amazon.com gets priority over AWS infrastructure)?<p>According to http://status.aws.amazon.com, all AWS services are healthy, yet I'm seeing these problems.<p>I can only create one EBS volume:
[root@domU-12-31-39-03-74-C6 ~]# ec2-describe-volumes 
    VOLUME  vol-d29d73bb    10      snap-f4f8319d   us-east-1b      available       2009-06-26T05:57:26+0000 
[root@domU-12-31-39-03-74-C6 ~]# ec2-create-volume -s 1 -z us-east-1b 
    Client.VolumeLimitExceeded: Maximum number of volumes, 1, already exist.<p>I can only create one AMI instance:
Launching 1 instance(s) of ami-0459bc6d
    Zone us-east-1a
    Instance type m1.small
AWS.rb:226:in `do_query': HTTP Error: 400 - Bad Request, AWS Error: InstanceLimitExceeded - 1 instance(s) are already running. (AWS::ServiceError)<p>But I have only one instance running, it won't even let me create a second one:
$ ec2-describe-instances
    RESERVATION     r-09b2cd60      832169661172    default
    INSTANCE        i-7bf0d312      ami-0459bc6d    ...<p>What gives? Is this a temporary problem? AWS is the first IaaS I tried to use, so I'm wondering to all of these IaaS (AWS, slicehost, etc.) all have these kind of problems on a regular basis?