Geek Answers Handbook

Aws elasticbeanstalk: cannot deploy to production via eb cli

I created a working environment for my eb application to take advantage of the "periodic tasks" using cron.yaml(located at the root of my application). This is a simple synatra application (for now) that I would like to use to send requests to the appropriate web server environment.

However, I am having problems deploying via eb cli. Below I get eb deploy.

╰─➤  eb deploy
Creating application version archive "4882".
Uploading myapp/4882.zip to S3. This may take a while.
Upload Complete.
INFO: Environment update is starting.
ERROR: Service:AmazonCloudFormation, Message:Stack named 'awseb-e-1a2b3c4d5e-stack'
aborted operation. Current state: 'UPDATE_ROLLBACK_IN_PROGRESS'
Reason: The following resource(s) failed to create: [AWSEBWorkerCronLeaderRegistry].

I looked at the CloudFormation dashboard to check for possible errors. After reading a little about what I can find regarding AWSEBWorkerCronLeaderRegistry, I found that it is most likely a table DynamoDBthat is being updated / created. However, when I look at the control panel DynamoDB, there are no tables in the table.

As always, any help, feedback or guidance is appreciated.

+4
source share
3 answers

I used Codepipeline to deploy my worker and was getting the same error. In the end, I tried to provide the AWS-CodePipeline-Service with the AmazonDynamoDBFullAccess policy and seemed to solve the problem.

+2
source

, , AmazonDynamoDBFullAccess Elastic Beanstalk ( aws-elasticbeanstalk-ec2- ).

+1

DynamoDB (, ), Beanstalk (AWSElasticBeanstalkWorkerTier). .

. http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/iam-instanceprofile.html

+1

More articles:


All Articles