You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Amplify Auth and/or Analytics module should provide out of the box integration with CloudWatch RUM since RUM provides a way to use existing Cognito Identity Pool and also has CloudFormation support to integrate with Amplify CLI.
Describe alternatives you've considered
Manually configuring RUM would require to create app monitors in console and going out of the way to provide appropriate permissions to the auth/unauth roles of the identity pool.
People would also face challenges like the one described in this issue: #9704
Additional context
No response
Is this something that you'd be interested in working on?
👋 I may be able to implement this feature request
⚠️ This feature might incur a breaking change
The text was updated successfully, but these errors were encountered:
Is this related to a new or existing framework?
No response
Is this related to a new or existing API?
Authentication, Analytics
Is this related to another service?
CloudWatch
Describe the feature you'd like to request
Provide native integration with CloudWatch RUM (Real User Monitoring)
Ref: https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/CloudWatch-RUM.html
Describe the solution you'd like
The Amplify Auth and/or Analytics module should provide out of the box integration with CloudWatch RUM since RUM provides a way to use existing Cognito Identity Pool and also has CloudFormation support to integrate with Amplify CLI.
Describe alternatives you've considered
Manually configuring RUM would require to create app monitors in console and going out of the way to provide appropriate permissions to the auth/unauth roles of the identity pool.
People would also face challenges like the one described in this issue: #9704
Additional context
No response
Is this something that you'd be interested in working on?
The text was updated successfully, but these errors were encountered: