Runtime versions using Node.js and Puppeteer

Lambda runtime Node.js 18.x

Puppeteer-core version 21.9.0

Chromium version 121.0.6167.139

Updated versions of the bundled libraries in Puppeteer and Chromium— The Puppeteer and Chromium dependencies are updated to new versions.

Lambda runtime Node.js 18.x

Puppeteer-core version 19.7.0

Chromium version 111.0.5563.146

Updated versions of the bundled libraries in Chromium

Ephemeral storage monitoring— This runtime adds ephemeral storage monitoring in customer accounts.

Bug fixes

Lambda runtime Node.js 16.x

Puppeteer-core version 19.7.0

Chromium version 111.0.5563.146

Updated versions of the bundled libraries in Chromium

Bug fixes

Lambda runtime Node.js 18.x

Puppeteer-core version 19.7.0

Chromium version 111.0.5563.146

Stability improvements— Added auto-retry logic for handling intermittent Puppeteer launch errors.

Dependency upgrades— Upgrades for some third-party dependency packages.

Canaries without Amazon S3 permissions— Bug fixes, such that canaries that don't have any Amazon S3 permissions can still run. These canaries with no Amazon S3 permissions won't be able to upload screenshots or other artifacts to Amazon S3. For more information about permissions for canaries, see Required roles and permissions for canaries.

Lambda runtime Node.js 18.x

Puppeteer-core version 19.7.0

Chromium version 111.0.5563.146

Dependency upgrade— The Node.js dependency is upgraded to 18.x.

Intercept mode support— Puppeteer cooperative intercept mode support was added to the Synthetics canary runtime library.

Tracing behavior change— Changed default tracing behavior to trace only fetch and xhr requests, and not trace resource requests. You can enable the tracing of resource requests by configuring the traceResourceRequests option.

Duration metric refined— The Duration metric now excludes the operation time the canary uses to upload artifacts, take screenshots, and generate CloudWatch metrics. Duration metric values are reported to CloudWatch, and you can also see them in the Synthetics console.

Bug fix— Clean up core dump generated when Chromium crashes during a canary run.

Lambda runtime Node.js 16.x

Puppeteer-core version 19.7.0

Chromium version 111.0.5563.146

Bug fix— This runtime fixes a bug in syn-nodejs-puppeteer-5.0 where the HAR files created by the canaries were missing request headers.

Lambda runtime Node.js 16.x

Puppeteer-core version 19.7.0

Chromium version 111.0.5563.146

Dependency upgrade— The Puppeteer-core version is updated to 19.7.0. The Chromium version is upgraded to 111.0.5563.146.

Lambda runtime Node.js 16.x

Puppeteer-core version 5.5.0

Chromium version 92.0.4512

Dependency upgrade— The Node.js dependency is updated to 16.x.

Lambda runtime Node.js 14.x

Puppeteer-core version 5.5.0

Chromium version 92.0.4512

Dependency upgrades— Upgrades some third-party dependency packages.

Lambda runtime Node.js 14.x

Puppeteer-core version 5.5.0

Chromium version 92.0.4512

Profile cleanup— Chromium profiles are now cleaned up after each canary run.

Bug fixes— Previously, visual monitoring canaries would sometimes stop working properly after a run with no screenshots. This is now fixed.

Lambda runtime Node.js 14.x

Puppeteer-core version 5.5.0

Chromium version 92.0.4512

Logging enhancement— The canary will upload logs to Amazon S3 even if it times out or crashes.

Lambda layer size reduced— The size of the Lambda layer used for canaries is reduced by 34%.

Bug fixes— Japanese, Simplified Chinese, and Traditional Chinese fonts will render properly.

Lambda runtime Node.js 14.x

Puppeteer-core version 5.5.0

Chromium version 92.0.4512

More precise timestamps— The start time and stop time of canary runs are now precise to the millisecond.

Lambda runtime Node.js 14.x

Puppeteer-core version 5.5.0

Chromium version 92.0.4512

Updated dependencies— The only new features in this runtime are the updated dependencies.

Lambda runtime Node.js 12.x

Puppeteer-core version 5.5.0

Chromium version 88.0.4298.0

Custom handler function— You can now use a custom handler function for your canary scripts. Previous runtimes required the script entry point to include .handler.

You can also put canary scripts in any folder and pass the folder name as part of the handler. For example, MyFolder/MyScriptFile.functionname can be used as an entry point.

Expanded HAR file information— You can now see bad, pending, and incomplete requests in the HAR files produced by canaries.

Lambda runtime Node.js 12.x

Puppeteer-core version 5.5.0

Chromium version 88.0.4298.0

More options for artifact encryption— For canaries using this runtime or later, instead of using an Amazon managed key to encrypt artifacts that the canary stores in Amazon S3, you can choose to use an Amazon KMS customer managed key or an Amazon S3-managed key. For more information, see Encrypting canary artifacts.

Lambda runtime Node.js 12.x

Puppeteer-core version 5.5.0

Chromium version 88.0.4298.0

visual monitoring with screenshots— Canaries using this runtime or later can compare a screenshot taken during a run with a baseline version of the same screenshot. If the screenshots are more different than a specified percentage threshold, the canary fails. For more information, see Visual monitoring or Visual monitoring blueprint.

New functions regarding sensitive data You can prevent sensitive data from appearing in canary logs and reports. For more information, see SyntheticsLogHelper class.

Deprecated function The RequestResponseLogHelper class is deprecated in favor of other new configuration options. For more information, see RequestResponseLogHelper class.

Lambda runtime Node.js 12.x

Puppeteer-core version 5.5.0

Chromium version 88.0.4298.0

Ability to configure CloudWatch metrics— With this runtime, you can disable the metrics that you do not require. Otherwise, canaries publish various CloudWatch metrics for each canary run.

Screenshot linking— You can link a screenshot to a canary step after the step has completed. To do this, you take the screenshot by using the takeScreenshot method, using the name of the step that you want to associate the screenshot with. For example, you might want to perform a step, add a wait time, and then take the screenshot.

Heartbeat monitor blueprint can monitor multiple URLs— You can use the heartbeat monitoring blueprint in the CloudWatch console to monitor multiple URLs and see the status, duration, associated screenshots, and failure reason for each URL in the step summary of the canary run report.

Lambda runtime Node.js 12.x

Puppeteer-core version 5.5.0

Chromium version 88.0.4298.0

Upgraded dependencies— This version uses Puppeteer version 5.5.0, Node.js 12.x, and Chromium 88.0.4298.0.

Cross-Region bucket access— You can now specify an S3 bucket in another Region as the bucket where your canary stores its log files, screenshots, and HAR files.

New functions available— This version adds library functions to retrieve the canary name and the Synthetics runtime version.

For more information, see Synthetics class.

Lambda runtime Node.js 10.x

Puppeteer-core version 3.3.0

Chromium version 83.0.4103.0

Monitor your canaries as HTTP steps— You can now test multiple APIs in a single canary. Each API is tested as a separate HTTP step, and CloudWatch Synthetics monitors the status of each step using step metrics and the CloudWatch Synthetics step report. CloudWatch Synthetics creates SuccessPercent and Duration metrics for each HTTP step.

This functionality is implemented by the executeHttpStep(stepName, requestOptions, callback, stepConfig) function. For more information, see executeHttpStep(stepName, requestOptions, [callback], [stepConfig]).

The API canary blueprint is updated to use this new feature.

HTTP request reporting— You can now view detailed HTTP requests reports which capture details such as request/response headers, response body, status code, error and performance timings, TCP connection time, TLS handshake time, first byte time, and content transfer time. All HTTP requests which use the HTTP/HTTPS module under the hood are captured here. Headers and response body are not captured by default but can be enabled by setting configuration options.

Global and step-level configuration— You can set CloudWatch Synthetics configurations at the global level, which are applied to all steps of canaries. You can also override these configurations at the step level by passing configuration key/value pairs to enable or disable certain options.

For more information, see SyntheticsConfiguration class.

Continue on step failure configuration— You can choose to continue canary execution when a step fails. For the executeHttpStep function, this is turned on by default. You can set this option once at global level or set it differently per-step.

Lambda runtime Node.js 10.x

Puppeteer-core version 3.3.0

Chromium version 83.0.4103.0

Configurable screenshot behavior— Provides the ability to turn off the capturing of screenshots by UI canaries. In canaries that use previous versions of the runtimes, UI canaries always capture screenshots before and after each step. With syn-nodejs-2.1, this is configurable. Turning off screenshots can reduce your Amazon S3 storage costs, and can help you comply with HIPAA regulations. For more information, see SyntheticsConfiguration class.

Customize the Google Chrome launch parameters You can now configure the arguments used when a canary launches a Google Chrome browser window. For more information, see launch(options).

Lambda runtime Node.js 10.x

Puppeteer-core version 3.3.0

Chromium version 83.0.4103.0

Upgraded dependencies— This runtime version uses Puppeteer-core version 3.3.0 and Chromium version 83.0.4103.0

Support for X-Ray active tracing. When a canary has tracing enabled, X-Ray traces are sent for all calls made by the canary that use the browser, the Amazon SDK, or HTTP or HTTPS modules. Canaries with tracing enabled appear on the X-Ray Trace Map, even when they don't send requests to other services or applications that have tracing enabled. For more information, see Canaries and X-Ray tracing.

Synthetics reporting— For each canary run, CloudWatch Synthetics creates a report named SyntheticsReport-PASSED.json or SyntheticsReport-FAILED.json which records data such as start time, end time, status, and failures. It also records the PASSED/FAILED status of each step of the canary script, and failures and screenshots captured for each step.

Broken link checker report— The new version of the broken link checker included in this runtime creates a report that includes the links that were checked, status code, failure reason (if any), and source and destination page screenshots.

New CloudWatch metrics— Synthetics publishes metrics named 2xx, 4xx, 5xx, and RequestFailed in the CloudWatchSynthetics namespace. These metrics show the number of 200s, 400s, 500s, and request failures in the canary runs. With this runtime version, these metrics are reported only for UI canaries, and are not reported for API canaries. They are also reported for API canaries starting with runtime version syn-nodejs-puppeteeer-2.2.

Sortable HAR files— You can now sort your HAR files by status code, request size, and duration.

Metrics timestamp— CloudWatch metrics are now reported based on the Lambda invocation time instead of the canary run end time.

Fixed the issue of canary artifact upload errors not being reported. Such errors are now surfaced as execution errors.

Fixed the issue of redirected requests (3xx) being incorrectly logged as errors.

Fixed the issue of screenshots being numbered starting from 0. They should now start with 1.

Fixed the issue of screenshots being garbled for Chinese and Japanese fonts.

Lambda runtime Node.js 10.x

Puppeteer-core version 3.3.0

Chromium version 83.0.4103.0

Upgraded dependencies— This runtime version uses Puppeteer-core version 3.3.0 and Chromium version 83.0.4103.0

Synthetics reporting— For each canary run, CloudWatch Synthetics creates a report named SyntheticsReport-PASSED.json or SyntheticsReport-FAILED.json which records data such as start time, end time, status, and failures. It also records the PASSED/FAILED status of each step of the canary script, and failures and screenshots captured for each step.

Broken link checker report— The new version of the broken link checker included in this runtime creates a report that includes the links that were checked, status code, failure reason (if any), and source and destination page screenshots.

New CloudWatch metrics— Synthetics publishes metrics named 2xx, 4xx, 5xx, and RequestFailed in the CloudWatchSynthetics namespace. These metrics show the number of 200s, 400s, 500s, and request failures in the canary runs. These metrics are reported only for UI canaries, and are not reported for API canaries.

Sortable HAR files— You can now sort your HAR files by status code, request size, and duration.

Metrics timestamp— CloudWatch metrics are now reported based on the Lambda invocation time instead of the canary run end time.

Fixed the issue of canary artifact upload errors not being reported. Such errors are now surfaced as execution errors.

Fixed the issue of redirected requests (3xx) being incorrectly logged as errors.

Fixed the issue of screenshots being numbered starting from 0. They should now start with 1.

Fixed the issue of screenshots being garbled for Chinese and Japanese fonts.

Lambda runtime Node.js 10.x

Puppeteer-core version 1.14.0

The Chromium version that matches Puppeteer-core 1.14.0