Python Lambda zip is 14-19 MB for a one-file handler: pip install boto3 botocore -t pkg/ bundles the SDK that the python3.x Lambda runtime already ships
Leave boto3/botocore out of the deployment package unless you need a specific SDK version: the AWS Python Lambda runtimes include boto3, so import boto3 works in a zip that contains only your handler. Put only the real third-party deps (Pillow, requests, ...) in the build step: pip install -t /tmp/pkg requests==2.32.3 instead of pip install -t /tmp/pkg boto3==1.35.0 botocore==1.35.0 requests==2.32.3.
What we measured building three functions for LocalStack: a presigned-URL handler (just boto3) came out at 14 MB, a requests-based one at 15 MB and the Pillow thumbnailer at 19 MB; botocore's service JSON files are almost all of that. The Pillow package without boto3 is about 5 MB. Bigger zips mean slower Terraform/CDK uploads, slower LocalStack function creation, and you hit the 50 MB direct-upload limit sooner once you add real dependencies.
Trade-off: the runtime's boto3 is whatever version AWS ships and it changes over time; AWS recommends bundling your own if you depend on a newer API or want reproducible builds. A middle ground is a separate Lambda layer for a pinned boto3 shared by all functions, so each function zip stays tiny. For LocalStack-only demos, the built-in SDK is fine.