- Newest
- Most votes
- Most comments
Hi Ethan, Thanks for making the inquiry. Let's examine some potential causes, step-by-step.
First, let's make sure the metrics are published to CloudWatch. From the AWS Console, navigate to the CloudWatch service and select Metrics from the left-hand menu pane. Next, locate the metric titled /aws/sagemaker/Canvas/AppActivity. For any given Canvas profile you are monitoring, compare the TimeSinceLastActive against your expectation. If you do not see metrics for your profile, please log out of the Canvas app (or delete from the SageMaker Console) and then relaunch it. After coming back online, allow at least 30 minutes for the metric to be visible and repeat this process.
Second, please check permissions for your Lambda function. For the role associated with the Lambda, review the IAM policy. In the example yaml (provided for inspiration), the following code snippet shows the permissions the Lambda should have, at minimum.
- Effect: Allow
Action:
- 'logs:CreateLogGroup'
- 'logs:CreateLogStream'
- 'logs:PutLogEvents'
- 'cloudwatch:GetMetricData'
Resource: '*'
- Effect: Allow
Action:
- 'sagemaker:DeleteApp'
Can you please review these two items? If you are still blocked, please feel free to open a support case via AWS Console under Support Center so our engineers can deep dive with you. Thank you!
Relevant content
- asked 2 years ago
- asked 4 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Thank you for your response!
I created a new user on the same domain and its Idle metric was able to check in with cloudwatch. I also was able to confirm that the lambda was able to delete the app from the new user created only. The original user appears to be bugged so we will just end up deleting it and using the new user.