12

I am trying to create new ELB environment with existing VPC. But I am unable to create environment with following errors:

ERROR Creating security group named: sg-5xxxxxxx failed Reason: Resource creation cancelled

ERROR Creating EIP:xx.xxx.xxx.xxx failed. Reason: Resource creation cancelled.

ERROR Stack named 'awseb-e-webxxxxxx-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBEIP, AWSEBSecurityGroup, AWSEBRDSDBSubnetGroup].

Note :I still didn't cross the Elastic Ip's limit. When i configure subnet for RDS in two regions they were automatically reset to single region only while creating evironment

Any suggestions will be helpful

Improve this question
4
  • 2
    Additional logs : ERROR Failed to pull logs for environment instances. Reason: Service:AmazonCloudFormation, Code:ValidationError, Message:Resource AWSEBAutoScalingGroup does not exist for stack awseb-e-websxxxx-stack, Class:com.amazon.aws.mac.connectors.awsservice.cloudformation.exceptions.CfnStackResourceNotFoundException ERROR Service:AmazonCloudFormation, Message:Resource AWSEBAutoScalingGroup does not exist for stack awseb-e-webscxxxx-stack Commented Jun 13, 2018 at 12:33
  • 1
    I have the exact same problem right now. Limit is not reached either. Can you post an update if you find an answer elsewhere? Commented Jun 13, 2018 at 14:39
  • 1
    @gyc you found the solution? Commented Nov 22, 2018 at 10:43
  • I switched projects so I don't remember at all sorry. Commented Nov 22, 2018 at 10:55

1 Answer 1

Reset to default
9

I was also having issues adding database via elastic beanstalk ui after initially creating an application using the command line interface. Turns out I had messed up my IAM (AWS Services > Security, Identity, Compliance > IAM) roles setup when I first created the account. This account was missing the role AWSServiceRoleForRDS. Once I created one, I was able to successfully configure a database for the new application.

Improve this answer
Sign up to request clarification or add additional context in comments.

1 Comment

I am the using the root account for this operation which has full access and yes AWSServiceRoleForRDS is already added

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.