Uncomment cryptography dependency in Python build test fixtures (aws#8735)

licjun · web-flow · commit ee86b48035ca · 2026-03-04T22:32:11.000Z
* Uncomment cryptography dependency with Lambda-compatible version

* Add cryptography to CDK asset requirements.txt
diff --git a/tests/integration/buildcmd/build_integ_base.py b/tests/integration/buildcmd/build_integ_base.py
@@ -746,7 +746,7 @@ class BuildIntegPythonBase(BuildIntegBase):
         "__init__.py",
         "main.py",
         "numpy",
-        # 'cryptography',
+        "cryptography",
     }
 
     FUNCTION_LOGICAL_ID = "Function"
diff --git a/tests/integration/buildcmd/test_build_cmd.py b/tests/integration/buildcmd/test_build_cmd.py
@@ -398,7 +398,7 @@ class TestBuildCommand_SingleFunctionBuilds(BuildIntegBase):
         "__init__.py",
         "main.py",
         "numpy",
-        # 'cryptography',
+        "cryptography",
         "requirements.txt",
     }
 
@@ -1763,7 +1763,7 @@ class TestBuildWithNestedStacksImage(NestedBuildIntegBase):
         "__init__.py",
         "main.py",
         "numpy",
-        # 'cryptography',
+        "cryptography",
         "requirements.txt",
     }
 
@@ -1937,7 +1937,7 @@ class TestBuildWithS3FunctionsOrLayers(NestedBuildIntegBase):
         "__init__.py",
         "main.py",
         "numpy",
-        # 'cryptography',
+        "cryptography",
         "requirements.txt",
     }
 
diff --git a/tests/integration/testdata/buildcmd/PyLayer/requirements.txt b/tests/integration/testdata/buildcmd/PyLayer/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PyLayerMake/requirements.txt b/tests/integration/testdata/buildcmd/PyLayerMake/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/Python/main.py b/tests/integration/testdata/buildcmd/Python/main.py
@@ -1,12 +1,11 @@
 import numpy
 
-
-# from cryptography.fernet import Fernet
+from cryptography.fernet import Fernet
 
 
 def handler(event, context):
     # Try using some of the modules to make sure they work & don't crash the process
-    # print(Fernet.generate_key())
+    print(Fernet.generate_key())
 
     return {"pi": "{0:.2f}".format(numpy.pi)}
 
diff --git a/tests/integration/testdata/buildcmd/Python/requirements.txt b/tests/integration/testdata/buildcmd/Python/requirements.txt
@@ -4,6 +4,4 @@
 numpy<1.20.3; python_version <= '3.9'
 numpy==2.1.3; python_version >= '3.10' and python_version < '3.14'
 numpy==2.3.4; python_version >= '3.14'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonContainerEnvVars/requirements.txt b/tests/integration/testdata/buildcmd/PythonContainerEnvVars/requirements.txt
@@ -0,0 +1,7 @@
+# These are some hard packages to build. Using them here helps us verify that building works on various platforms
+
+# NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
+numpy<1.20.3; python_version <= '3.9'
+numpy==2.1.3; python_version >= '3.10' and python_version < '3.14'
+numpy==2.3.4; python_version >= '3.14'
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonImage/requirements.txt b/tests/integration/testdata/buildcmd/PythonImage/requirements.txt
@@ -4,6 +4,4 @@
 numpy<1.20.3; python_version < '3.10'
 numpy==2.1.3; python_version >= '3.10' and python_version < '3.14'
 numpy==2.3.4; python_version >= '3.14'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonImagesWithSharedCode/requirements.txt b/tests/integration/testdata/buildcmd/PythonImagesWithSharedCode/requirements.txt
@@ -4,6 +4,4 @@
 numpy<1.20.3; python_version < '3.10'
 numpy==2.1.3; python_version >= '3.10' and python_version < '3.14'
 numpy==2.3.4; python_version >= '3.14'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonPEP600/requirements.txt b/tests/integration/testdata/buildcmd/PythonPEP600/requirements.txt
@@ -7,3 +7,4 @@ numpy==2.3.4; python_version >= '3.14'
 greenlet==3.1.1; python_version < '3.14'
 greenlet==3.2.4; python_version >= '3.14'
 sqlalchemy==2.0.36
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonParentPackages/src/fnone/requirements.txt b/tests/integration/testdata/buildcmd/PythonParentPackages/src/fnone/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version <= '3.9'
 numpy==2.1.3; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonParentPackages/src/fntwo/requirements.txt b/tests/integration/testdata/buildcmd/PythonParentPackages/src/fntwo/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version <= '3.9'
 numpy==2.1.3; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/PythonPyProject/main.py b/tests/integration/testdata/buildcmd/PythonPyProject/main.py
@@ -1,12 +1,11 @@
 import numpy
 
-
-# from cryptography.fernet import Fernet
+from cryptography.fernet import Fernet
 
 
 def handler(event, context):
     # Try using some of the modules to make sure they work & don't crash the process
-    # print(Fernet.generate_key())
+    print(Fernet.generate_key())
 
     return {"pi": "{0:.2f}".format(numpy.pi)}
 
diff --git a/tests/integration/testdata/buildcmd/PythonPyProject/pyproject.toml b/tests/integration/testdata/buildcmd/PythonPyProject/pyproject.toml
@@ -5,7 +5,5 @@ dependencies = [
   "numpy==2.0.0; python_version <= '3.9'",
   "numpy==2.1.3; python_version >= '3.10' and python_version < '3.14'",
   "numpy==2.3.4; python_version >= '3.14'",
-  # `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-  # Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-  # "cryptography~=2.4"
+  "cryptography==3.3.2",
 ]
diff --git a/tests/integration/testdata/buildcmd/PythonWithLayer/requirements.txt b/tests/integration/testdata/buildcmd/PythonWithLayer/requirements.txt
@@ -1,5 +1,3 @@
 # These are some hard packages to build. Using them here helps us verify that building works on various platforms
 
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/asset.b998895901bf33127f2c9dce715854f8b35aa73fb7eb5245ba9721580bbe5837/requirements.txt b/tests/integration/testdata/buildcmd/asset.b998895901bf33127f2c9dce715854f8b35aa73fb7eb5245ba9721580bbe5837/requirements.txt
@@ -1,2 +1,3 @@
 numpy<1.20.3; python_version < '3.10'
-numpy==1.26.4; python_version >= '3.10'
+numpy==1.26.4; python_version >= '3.10'
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_local_backend/my_layer_code/requirements.txt b/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_local_backend/my_layer_code/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_local_backend_container_windows/my_layer_code/requirements.txt b/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_local_backend_container_windows/my_layer_code/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_local_backend_windows/my_layer_code/requirements.txt b/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_local_backend_windows/my_layer_code/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_s3_backend/my_layer_code/requirements.txt b/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_s3_backend/my_layer_code/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_s3_backend_container_windows/my_layer_code/requirements.txt b/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_s3_backend_container_windows/my_layer_code/requirements.txt
@@ -2,6 +2,4 @@
 
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2
diff --git a/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_s3_backend_windows/my_layer_code/requirements.txt b/tests/integration/testdata/buildcmd/terraform/zip_based_lambda_functions_s3_backend_windows/my_layer_code/requirements.txt
@@ -3,6 +3,4 @@
 # NOTE: Fixing to <1.20.3 as numpy1.20.3 started to use a new wheel naming convention (PEP 600)
 numpy<1.20.3; python_version < '3.10'
 numpy==1.26.4; python_version >= '3.10'
-# `cryptography` has a dependency on `pycparser` which, for some reason doesn't build inside a Docker container.
-# Turning this off until we resolve this issue: https://github.com/awslabs/aws-lambda-builders/issues/29
-# cryptography~=2.4
+cryptography==3.3.2

Original file line number	Diff line number	Diff line change
`@@ -746,7 +746,7 @@ class BuildIntegPythonBase(BuildIntegBase):`
`746`	`746`	`"__init__.py",`
`747`	`747`	`"main.py",`
`748`	`748`	`"numpy",`
`749`		`- # 'cryptography',`
	`749`	`+ "cryptography",`
`750`	`750`	`}`
`751`	`751`
`752`	`752`	`FUNCTION_LOGICAL_ID = "Function"`