2

I've deployed a nodejs worker. However whenever I try to start it, it gets red and this error is showned: ERROR Instance: i-6eef007a Module: AWSEBAutoScalingGroup ConfigSet: null Command failed on instance. Return code: 1 Output: Error occurred during build: Command 01-start-sqsd failed .

I don't know if it's related, sometimes I get this error on the screen: IamInstanceProfile: The environment does not have an IAM instance profile associated with it. To improve deployment speed please associate an IAM instance profile with the environment.

I've already given permission to SQS and set key and secret. I don't know what else to do.

Log attached.

Thank you very much.

otaviosoares
  • 566
  • 7
  • 17

1 Answers1

6

You need to have an IAM role with the appropriate permissions to create an Elastic Beanstalk worker environment.

The IAM role should have the following permissions:

{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Sid": "QueueAccess",
      "Action": [
        "sqs:ChangeMessageVisibility",
        "sqs:DeleteMessage",
        "sqs:ReceiveMessage"
      ],
      "Effect": "Allow",
      "Resource": "*"
    },
    {
      "Sid": "MetricsAccess",
      "Action": [
        "cloudwatch:PutMetricData"
      ],
      "Effect": "Allow",
      "Resource": "*"
    }
  ]
}

Detailed documentation: http://docs.aws.amazon.com/elasticbeanstalk/latest/dg/AWSHowTo.iam.roles.aeb.html#AWSHowTo.iam.policies.actions.worker

For debugging you can ssh to the instance and look at /var/log/aws-sqsd/default.log to see the logs. If you want to avoid ssh'ing to the instance you can also snapshot logs from the AWS Console as shown here.

You can read more about worker role environments here.

Rohit Banga
  • 18,458
  • 31
  • 113
  • 191
  • I came across this answer when searching for a similar issue I'm having. I did verify that I have these permissions allowed on the ec2-role which EB created for me. They're included in the `AWSElasticBeanstalkWorkerTier` AWS managed Policy attached to the role. – Jon Worek Apr 17 '23 at 18:06