- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
Kindly check if the Policy is updated with the necessary permission. Please refer: https://docs.aws.amazon.com/prometheus/latest/userguide/CW-logs-config.html
Hi, I tried adding the necessary permission to the account, then creating the log group and enabling logs on the AMP console. But still no luck, I can't see any logs, just the one with the message "Permissions are set correctly to allow AWS CloudWatch Logs to write into your logs while creating a subscription" as mentioned by LilyB. Can you provide more information about it? I think AMP is lacking some documentation in several aspects and there are not much examples of people using it.
Angelo: I agree with you that any more info would be appreciated. I got the same result as you with one log entry that permissions were set in the the logs, but nothing else. I forgot to add that comment to this question, but I mentioned it in a separate question I made when I thought that I had fundamentally misunderstood the way users and permissions should be handled when it comes to AMP workspaces: https://repost.aws/questions/QUPZ1VVneVRf-U0EpB6ibX8A/should-i-create-an-administrative-user-separate-from-my-personal-iam-user-for-creating-my-amazon-managed-service-for-prometheus-workspace . I would especially like some info on how to test if AMP can write to logs, since that seems to only be done if AMP throws an error, which I can not be sure has happened.
Relevanter Inhalt
AWS OFFICIALAktualisiert vor 2 Jahren- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
Thank you for your reply. I had seen this part of the docs, but the problem was that I didn't understand which user or role I should attach that policy to. I just now tried to attach thse permissions to my personal IAM user that I used when setting up the AMP workspace, and since i got a logstream with the message "Permissions are set correctly to allow AWS CloudWatch Logs to write into your logs while creating a subscription." I guess that it worked. However, that means I should have used a generic/non-personal user to create the workspace, not my personal IAM user.