Can't build on Ubuntu (AWS EC2)

[ivnsch]

After diverse issues trying to cross-compile my project, I decided to upload a minimal version of the source to AWS and build there.

The build however always gets stuck on the aws-sdk-s3 dependency:

Building [=======================> ] 398/402: aws-sdk-s3                                                                                                                                                                                       

There are no errors or warnings and I've waited for hours, tried again with a different instance etc. - it always gets stuck there.

Building with --verbose shows this:

 Running `rustc --crate-name aws_sdk_s3 --edition=2021 /home/ubuntu/.cargo/registry/src/github.com-1ecc6299db9ec823/aws-sdk-s3-0.12.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --crate-type lib --emit=dep-info,metadata,link -C embed-bitcode=no -C debuginfo=2 --cfg 'feature="default"' --cfg 'feature="rt-tokio"' --cfg 'feature="rustls"' -C metadata=6d29584a90ae0b41 -C extra-filename=-6d29584a90ae0b41 --out-dir /home/ubuntu/api/target/debug/deps -L dependency=/home/ubuntu/api/target/debug/deps --extern aws_endpoint=/home/ubuntu/api/target/debug/deps/libaws_endpoint-e261f76c6206aef1.rmeta --extern aws_http=/home/ubuntu/api/target/debug/deps/libaws_http-c74de03b7656b44d.rmeta --extern aws_sig_auth=/home/ubuntu/api/target/debug/deps/libaws_sig_auth-905021a37c460e27.rmeta --extern aws_sigv4=/home/ubuntu/api/target/debug/deps/libaws_sigv4-b64a611351fc5d53.rmeta --extern aws_smithy_async=/home/ubuntu/api/target/debug/deps/libaws_smithy_async-48a6ee129e7ff27b.rmeta --extern aws_smithy_client=/home/ubuntu/api/target/debug/deps/libaws_smithy_client-6b8a74132cf06540.rmeta --extern aws_smithy_eventstream=/home/ubuntu/api/target/debug/deps/libaws_smithy_eventstream-36b1134cf1958fcb.rmeta --extern aws_smithy_http=/home/ubuntu/api/target/debug/deps/libaws_smithy_http-89517899ca796fa6.rmeta --extern aws_smithy_http_tower=/home/ubuntu/api/target/debug/deps/libaws_smithy_http_tower-3518cb8175e1499f.rmeta --extern aws_smithy_types=/home/ubuntu/api/target/debug/deps/libaws_smithy_types-9f79dede2fce9fbb.rmeta --extern aws_smithy_xml=/home/ubuntu/api/target/debug/deps/libaws_smithy_xml-58e315b8ca09101f.rmeta --extern aws_types=/home/ubuntu/api/target/debug/deps/libaws_types-dc1c88c01a0397b8.rmeta --extern bytes=/home/ubuntu/api/target/debug/deps/libbytes-5e8424a0f7103369.rmeta --extern http=/home/ubuntu/api/target/debug/deps/libhttp-c7b51d7a319d3936.rmeta --extern md5=/home/ubuntu/api/target/debug/deps/libmd5-7686c4c65dd50a84.rmeta --extern tokio_stream=/home/ubuntu/api/target/debug/deps/libtokio_stream-d65a569d8cf69052.rmeta --extern tower=/home/ubuntu/api/target/debug/deps/libtower-391d97e2a6af0e6b.rmeta --cap-lints allow -L native=/home/ubuntu/api/target/debug/build/ring-cfe4dad9e4e90f9f/out

Building [=======================> ] 398/402: aws-sdk-s3

Relevant dependencies:

aws-config = { version = "0.12.0", features = ["rustls"] }
aws-sdk-s3 = { version = "0.12.0", features = ["rustls"] }

Cargo version:

cargo 1.63.0-nightly (a4c1cd0eb 2022-05-18)

(happens also with stable)

Ubuntu version:

Ubuntu 22.04 LTS

Storage:

$  df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/root        29G  7.7G   22G  27% /
tmpfs           484M     0  484M   0% /dev/shm
tmpfs           194M  828K  193M   1% /run
tmpfs           5.0M     0  5.0M   0% /run/lock
/dev/xvda15     105M  5.3M  100M   5% /boot/efi
tmpfs            97M  4.0K   97M   1% /run/user/1000

It builds without problems on my Mac.

[jdisanti]

How much RAM does the system it hangs on have? First thing that comes to mind for me is that if the system doesn't have a lot of memory, the compiler might be swapping a lot leading to an extremely long compile time. Our CI successfully compiles aws-sdk-s3 on Ubuntu 20.04, so not quite 22.04 but I can't imagine there would be too large of a difference there.

[SylvainSenechal]

Is this the only way available to us to work around this problem though ? It's a bit unfortunate that we are somewhat forced to upgrade to a 10$/month instance just to compile our rust project, when our webserver could run properly on the 3.5$ or 5$ instances

[Velfi]

EC2 and S3 have a very large API. We've considered feature-gating individual operations which would help, but I don't know if we're going to implement it. If this is a really important issue to you, could you take the time to submit a GitHub issue so we can track this?

[ivnsch]

Aah that was it! It had just 1GB, upgraded to 2 and now it finishes.

[timwsuqld]

I'm hitting a similar issue, with the aws-sdk-ec2 dep on a project taking forever to build in the cloud (a GCP instance). 2 vCPUs and 8 GB of RAM, no swapping occuring to disk. Same project compiled fine on my Laptop.

CPU is maxed out on both cores. It took about 15 minutes (out of a 16 minute build) before it progressed past the aws-sdk-ec2 stage.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.

[kriptonian1]

Guys, I am trying to build it on my PC it has 16 GB of ram but still it's crashing

[kriptonian1]

It's really getting hard for me to work this way

[erickfy]

yes I stuck with this