s2n-tls with aws-lc

[lucykorea414]

I installed both aws-lc and s2n-tls in my EC2 AL2 instance.
this is the full commands I made
`# install build dependencies
sudo yum groupinstall "Development Tools"
sudo yum install cmake3

#install aws-lc
sudo yum install ninja-build clang perl golang
git clone https://github.com/aws/aws-lc.git
mkdir aws-lc-build && cd aws-lc-build
cmake3 -GNinja
-DCMAKE_BUILD_TYPE=RelWithDebInfo
-DCMAKE_INSTALL_PREFIX=../aws-lc-install
../aws-lc
ninja-build run_tests
ninja-build install
cd ..

#install s2n-tls
git clone https://github.com/aws/s2n-tls.git
cd s2n-tls
cmake3 . -Bbuild
-DCMAKE_BUILD_TYPE=Release
-DCMAKE_PREFIX_PATH=../aws-lc-install
-DCMAKE_INSTALL_PREFIX=./s2n-tls-install
cmake3 --build build -j $(nproc)
cd build
CTEST_PARALLEL_LEVEL=$(nproc) ctest3
cd ..
cmake3 --install build`

I want to check if my s2n-tls is using aws-lc properly.
Is there a way to find this out? (maybe a test?)

also, the building commands for AL2 are different from the docs as posted in my PR(#4679 )

[lrstewart]

I discuss that in the PQ documentation I recently added: https://github.com/aws/s2n-tls/blob/main/docs/usage-guide/topics/ch15-post-quantum.md#aws-lc s2nc and s2nd now report which libcrypto they were built with.

Alternatively, you could check for kyber support in the output of the cmake configuration command. If you built with aws-lc, it should say "feature S2N_LIBCRYPTO_SUPPORTS_KYBER: TRUE"

[lucykorea414]

thanks!