chore: increase vm.max_map_count to (hopefully) mitigate OOM errors (a…

…ws#16752)

The vm.max_map_count on our CodeBuild instances is fairly low (65530) compared
to our max threads (1125977). Based on a NodeJS issue troubleshooting thread
(nodejs/help#2809), trying to see if increasing this
value stabilizes our builds.


----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*

buildspec-pr.yaml

@@ -12,6 +12,10 @@ phases:
 
       # Install yarn if it wasn't already present in the image
       - yarn --version || npm -g install yarn
+
+      # Packing the mono-libraries (monocdk & aws-cdk-lib) can cause
+      # memory errors. Increasing this value allows our build to more consistently succeed
+      - (command -v sysctl || yum install -y procps-ng) && /sbin/sysctl -w vm.max_map_count=2251954
   build:
     commands:
       - /bin/bash ./build.sh --extract

buildspec.yaml

@@ -12,6 +12,10 @@ phases:
 
       # Install yarn if it wasn't already present in the image
       - yarn --version || npm -g install yarn
+
+      # Packing the mono-libraries (monocdk & aws-cdk-lib) can cause
+      # memory errors. Increasing this value allows our build to more consistently succeed
+      - /sbin/sysctl -w vm.max_map_count=2251954
   build:
     commands:
       - 'if ${BUMP_CANDIDATE:-false}; then /bin/bash ./scripts/bump-candidate.sh; fi'