"errorCode": "AccessDenied",
"errorMessage": "User: arn:aws:sts::XXXXXXXXXXXX:assumed-role/buildkite-5-11-0-test-Autoscaling-CV-ExecutionRole-X4NRVJKLN5LX/buildkite-5-11-0-test-Autoscal-AutoscalingFunction-eAfNzknpQWKz is not authorized to perform: autoscaling:DescribeScalingActivities because no identity-based policy allows the autoscaling:DescribeScalingActivities action",
Not sure how it affects the functionality of the agent; it doesn't seem to complain about anything else.
The problem for us though, is the frequency of AccessDenied's into CloudTrail is triggering alerts. Unless we can suppress these (looking into it), we will not be able to upgrade our agents to use versions which utilise versions of the agent scaler which contain this bug.
Attempts by the autoscaling function to call autoscaling:DescribeScalingActivities result in an AccessDenied error.
Cloudwatch Logs of the autoscaling function where this problem is seen:
This also ends up in CloudTrail
autoscaling:DescribeScalingActivities appears to be where this is called.
Perhaps this section is missing permissions.
Not sure how it affects the functionality of the agent; it doesn't seem to complain about anything else.
The problem for us though, is the frequency of AccessDenied's into CloudTrail is triggering alerts. Unless we can suppress these (looking into it), we will not be able to upgrade our agents to use versions which utilise versions of the agent scaler which contain this bug.
Parameters used to create the stack:
Thanks, Kwong.