Skip to content
This repository has been archived by the owner on Feb 4, 2022. It is now read-only.

lizzy does not have permissions to create stack with SQS Queue enabled #188

Open
zmeda opened this issue Oct 7, 2016 · 1 comment
Open

Comments

@zmeda
Copy link
Contributor

zmeda commented Oct 7, 2016

In a yaml file we are using:

Resources:
  LifecycleHook:
    Type: AWS::AutoScaling::LifecycleHook
    Properties:
      AutoScalingGroupName: { "Ref": "AppServer" } # senza call the autoscaling group resource "AppServer" for some     reason
      LifecycleTransition: "autoscaling:EC2_INSTANCE_TERMINATING"
      NotificationTargetARN: { "Fn::GetAtt": ["ShutdownNotificationQueue", "Arn"] }
      RoleARN: { "Fn::GetAtt": ["ShutdownNotificationRole",  "Arn"] }

  ShutdownNotificationRole:
    Type: AWS::IAM::Role
    Properties:
        AssumeRolePolicyDocument: >
          {
            "Version": "2012-10-17",
            "Statement": [
              {
                "Effect": "Allow",
                "Principal": {
                  "Service": "autoscaling.amazonaws.com"
                },
                "Action": "sts:AssumeRole"
              }
            ]
          }
        ManagedPolicyArns: ["arn:aws:iam::aws:policy/service-role/AutoScalingNotificationAccessRole"]

  ShutdownNotificationQueue:
    Type: AWS::SQS::Queue
    Properties:
      ReceiveMessageWaitTimeSeconds: 20
      VisibilityTimeout: 10

And security role of lizzy (by default) does not have permission to use SQS.

zmeda added a commit to zmeda/lizzy that referenced this issue Oct 7, 2016
@lasomethingsomething
Copy link

Hi @jmcs and @rafaelcaricio: What are your thoughts on @zmeda's issue? Something to address, something to invite a contribution to fix, already fixed, or other?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants