我已经为我的eb应用程序创建了一个工作环境,以便使用 cron.yaml (位于我的应用程序的根目录)来利用其定期任务"功能.这是一个简单的sinatra应用程序(目前),我想用它来向相应的Web服务器环境发出请求.
I've created a worker environment for my eb application in order to take advantage of its "periodic tasks" capabilities using cron.yaml (located in the root of my application). It's a simple sinatra app (for now) that I would like to use to use to issue requests to my corresponding web server environment.
但是,我无法通过eb cli进行部署.以下是我运行 eb deploy 的情况.
However, I'm having trouble deploying via the eb cli. Below is what happens I run 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].我环顾了CloudFormation仪表板,以检查是否存在错误.在阅读了一些有关 AWSEBWorkerCronLeaderRegistry 的信息之后,我发现更新/创建了最有可能的 DynamoDB 表.但是,当我在 DynamoDB 仪表板中查看时,没有列出任何表.
I've looked around the CloudFormation dashboard to see to check for possible errors. After reading a bit of about what I could find regarding AWSEBWorkerCronLeaderRegistry, I found it that it's most likely a DynamoDB table that gets updated/created. However, when I look in the DynamoDB dashboard, there are no tables listed.
一如既往,感谢您的帮助,反馈或指导.
As always, any help, feedback, or guidance is appreciated.
推荐答案如果您不愿意添加完整的DynamoDB访问权限(像我以前一样),那么Beanstalk现在提供了针对Worker环境权限的托管策略(AWSElasticBeanstalkWorkerTier).您可以尝试将其中之一添加到实例配置文件角色中.
If you are reluctant to add full DynamoDB access (like I was), Beanstalk now provides a Managed Policy for Worker environment permissions (AWSElasticBeanstalkWorkerTier). You can try adding one of these to your instance profile role instead.
请参见 docs.aws.amazon/elasticbeanstalk/latest/dg/iam-instanceprofile.html
更多推荐
AWS Elasticbeanstalk:无法通过eb cli部署到工作人员环境
发布评论