-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
aws-synthetics: NodeJS puppeteer Runtime Versions 5.2 & 6.2 & Python Selenium 2.1 #29135
Comments
FYI, there's a PR created but doesn't seem to be prioritized yet. |
Yeah, I'll bump this to p1. |
Closes #29135 ### Reason for this change Surface latest runtime versions in CDK. Older runtimes are being deprecated March 19, 2024 > To ensure uninterrupted canary runs and continued monitoring, AWS recommends customers to update their canaries to the latest Synthetics Runtimes versions: syn-nodejs-puppeteer-6.2 or higher for NodeJS-18, syn-nodejs-puppeteer-5.2 or higher for NodeJS-16, and syn-python-selenium-2.1 or higher for Python [2]. Canaries updated with latest Synthetics runtimes will continue running without interruption and receive future Lambda security updates. ### Description of changes - feat(synthetics): add 5.2, 6.1, 6.2 nodejs runtimes, deprecate 3.x runtimes - feat(synthetics): add syn-python-selenium-2.1 runtime - test(synthetics): update integration tests to cover latest runtimes ### Description of how you validated changes Attempted to run integration tests, but I don't have appropriate account setup ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Closes #29135 ### Reason for this change Surface latest runtime versions in CDK. Older runtimes are being deprecated March 19, 2024 > To ensure uninterrupted canary runs and continued monitoring, AWS recommends customers to update their canaries to the latest Synthetics Runtimes versions: syn-nodejs-puppeteer-6.2 or higher for NodeJS-18, syn-nodejs-puppeteer-5.2 or higher for NodeJS-16, and syn-python-selenium-2.1 or higher for Python [2]. Canaries updated with latest Synthetics runtimes will continue running without interruption and receive future Lambda security updates. ### Description of changes - feat(synthetics): add 5.2, 6.1, 6.2 nodejs runtimes, deprecate 3.x runtimes - feat(synthetics): add syn-python-selenium-2.1 runtime - test(synthetics): update integration tests to cover latest runtimes ### Description of how you validated changes Attempted to run integration tests, but I don't have appropriate account setup ### Checklist - [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md) ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@pahud : we're having the same issue again, this time with |
Describe the feature
On February 6, AWS announced the release of NodeJS puppeteer runtimes 6.2 & 5.2, and python selenium runtime 2.1, and announced that all non-deprecated older versions will be deprecated on March 8th. Today, we got an email from AWS saying that new lambda runtimes will be deployed on March 19th and that the changes will not be backwards compatible with current puppeteer versions so we have to upgrade our runtimes
![Screenshot 2024-02-16 at 1 53 45 PM](https://private-user-images.githubusercontent.com/22524855/305405967-7ac73ecf-9874-4d0d-95c0-19935281f062.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkxNzMxOTAsIm5iZiI6MTczOTE3Mjg5MCwicGF0aCI6Ii8yMjUyNDg1NS8zMDU0MDU5NjctN2FjNzNlY2YtOTg3NC00ZDBkLTk1YzAtMTk5MzUyODFmMDYyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTAlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjEwVDA3MzQ1MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWU4MDk5MmZlYWZmYmRlNjE1ZDdlZGJhZTM1MWEyYWZkMDJmNzA0YTA2ZGIxMTI3MzVlZjkyNTg4OWQ0ZTUwYjQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.28SlWkGatAMyNDy6kUUEnKh_0h441ZeNEqPNUJGtMQY)
Those versions do not exist in the latest CDK version, so we need them to be added so that we can update our runtimes, test and deploy to production before the cutoff time
Use Case
AWS will upgrade the lambda runtimes to a non-compatible version with the current puppeteer runtimes, which will break our synthetic canaries.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.128
Environment details (OS name and version, etc.)
MacOS 14
The text was updated successfully, but these errors were encountered: