Permissions required for Application Signals
This section explains the permissions necessary for you to enable, manage, and operate Application Signals.
Permissions to enable and manage Application Signals
To manage Application Signals, you must be signed on with the required permissions. To view the contents of the CloudWatchApplicationSignalsFullAccess policy, see CloudWatchApplicationSignalsFullAccess.
To enable Application Signals on Amazon EC2, or custom architectures, see Enable Application Signals on Amazon EC2. To enable and manage Application Signals on Amazon EKS using the Amazon CloudWatch Observability EKS add-on, you need the following permissions.
Important
These permissions include iam:PassRole with Resource "*”
and eks:CreateAddon with Resource “*”. These are powerful
permissions and you should use caution in granting them.
The Application Signals dashboard shows the AWS Service Catalog AppRegistry applications that your SLOs are associated with. To see these applications in the SLO pages, you must have the following permissions:
Operating Application Signals
Service operators who are using Application Signals to monitor services and SLOs must be signed on to an account with read only permissions. To view the contents of the CloudWatchApplicationSignalsReadOnlyAccess policy, see CloudWatchApplicationSignalsReadOnlyAccess.
To see which AWS Service Catalog AppRegistry Applications that your SLOs are associated within the Application Signals dashboard, you must have the following permissions:
To check if Application Signals on Amazon EKS using the Amazon CloudWatch Observability EKS add-on is enabled, you need to have the following permissions:
