CloudWatch RUM now supports JavaScript source maps for easier error debugging

Amazon CloudWatch RUM, which helps developers monitor real user interactions and diagnose front-end performance issues in web applications, now supports JavaScript source maps, enabling developers to convert minified JavaScript errors in the stack trace into readable formats for faster error resolution. With this feature, front-end developers and DevOps teams can now view searchable, human-readable JS errors and quickly identify the exact location of errors in their original source code.

JavaScript errors can be difficult to debug when they are minified in the stack trace, making it hard to pinpoint the source of an issue. Now, if an error occurs in a production environment, RUM leverages customer uploaded source maps to trace it back to the original code. The added ability to search unminified stack traces in RUM events helps developers analyze trends and correlate issues across multiple sessions, enabling faster detection and prioritization of recurring errors. To unminify errors in JavaScript stack traces, customers need to enable it in the App Monitor configuration and provide the S3 URI of the bucket or folder that holds the source maps via the console or RUM APIs.

These enhancements are available in all regions where CloudWatch RUM is available. Customer pay cost of storage of their source maps to Amazon S3 and for the API calls to upload and retrieve source maps as per AWS public pricing found here.

See documentation to know more about the feature, or see user guide to learn how to get started with CloudWatch RUM.