-
Notifications
You must be signed in to change notification settings - Fork 82
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
Update CodeBuild images to Linux2 standard5.0 (node16 to node18) + Update Docker images to use AmazonLinux:2023 (node18 and Python3.9) #889
Conversation
At the moment it throws errors in the CICD pipeline because of DDK cli |
@dlpzx - thoughts on also specifying |
@noah-paige yes! Definitely, I did not want to interfere with the work of the DDK pipelines but I will do now. I also realized that we might be using deprecated versions of node in ECS. I'll review |
I am currently testing the changes in AWS |
I deployed the changes before the last update and CICD Pipeline went through. I will pull latest changes and test again for CICD pipeline completing successfully, and pipeline creation still works Will also check local deployment still works |
Do not approve yet because there are some issues with using Linux5. In order to use node18 in the Docker images, we also need to upgrade the images used in the docker files. The new Amazon Linux 2023 is a bit different from Linux2, it is more minimalistic and does not include all packages, plus it replaces |
Tested in AWS
Tested locally
Note: we need to update the GitHub pages and specify Python 3.9 as minimum |
Deployed locally - images are built properly Left 2 nit comments, otherwise LGTM |
…907) ### Feature or Bugfix <!-- please choose --> - Bugfix ### Detail - Fix docker image used on VPC Facing Deployments to successfully build frontend + userguide images to host in ECS ### Relates - #889 ### Security Please answer the questions below briefly where applicable, or write `N/A`. Based on [OWASP 10](https://owasp.org/Top10/en/). - Does this PR introduce or modify any input fields or queries - this includes fetching data from storage outside the application (e.g. a database, an S3 bucket)? N/A - Is the input sanitized? N/A - What precautions are you taking before deserializing the data you consume? N/A - Is injection prevented by parametrizing queries? N/A - Have you ensured no `eval` or similar functions are used? Yes - Does this PR introduce any functionality or component that requires authorization? No - How have you ensured it respects the existing AuthN/AuthZ mechanisms? N/A - Are you logging failed auth attempts? N/A - Are you using or adding any cryptographic features? N/A - Do you use a standard proven implementations? Yes - Are the used keys controlled by the customer? Where are they stored? N/A - Are you introducing any new policies/roles/users? No - Have you used the least-privilege principle? How? N/A By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Feature or Bugfix
Detail
The purpose of this PR is to upgrade any compute resource that uses node16 to node18.
Relates
#782
Security
Please answer the questions below briefly where applicable, or write
N/A
. Based onOWASP 10. N/A
fetching data from storage outside the application (e.g. a database, an S3 bucket)?
eval
or similar functions are used?By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.