Size of the library

[snap40ben]

Hello,

I'm checking if we could use AWS IoT for a product we have.

It's a linux based product which would have around 20MB of space available for the application using AWS IoT.

I've tried to compile using the -DCMAKE_SYSTEM_NAME=Linux -DCMAKE_SYSTEM_PROCESSOR=arm flags. The library files seem quite heavy and I'm not sure if the SDK would be a good fit given the constraint.

I know the AWS IoT C SDK is available too (I've integrated it on another project), however we would need the Secure Tunnel feature and it didn't seem to be supported in the C SDK.

Is this assumption correct?

I've tried building the basic-pub-sub app and its size is already 21MB.

Would 20MB of free space enough to use MQTT connection, shadow, jobs and secure tunnels? If yes, would there be some guidelines to do so?

Thanks for your help,
Ben

[bretambrose]

I recently took a look at size for various internal reasons, this was the table I ended up with for Linux builds.

All builds in release, shared objects; symbol stripped also included -Os.

Library	Base Size	-Os	Symbol Stripped
aws-c-common	320	277	224
aws-c-cal	81	78	64
aws-c-io	346	308	265
aws-checksums	52	48	46
aws-c-event-stream	118	102	88
aws-c-compression	17	17	15
aws-c-http	460	406	352
aws-c-mqtt	341	304	260
aws-c-auth	258	235	195
aws-c-sdkutils	116	105	88
aws-c-iot	124	113	97
Aws-c-* Sum	2233	1993	1694
aws-crt-cpp	866	757	516
libDiscovery-cpp	134	115	79
libEventstreamRpc-cpp	167	137	100
libGreengrassIpc-cpp	2196	2045	1217
libIotDeviceCommon-cpp	16	16	15
libIotDeviceDefender-cpp	88	90	63
libIotIdentity-cpp	163	128	79
libIotJobs-cpp	303	224	144
libIotSecureTunneling-cpp	185	169	119
libIotShadow-cpp	304	239	143
C++ Sum	3556	3163	1959
C/C++/CRT Sum	6655	5913	4169

[snap40ben]

That's great thanks!

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.