Welcome! This GitHub project provides a Python-based solution to containerize your application using Docker and deploy it to AWS Lambda with the AWS CLI. Follow the instructions below to get started.

This project helps analyze the network performance and implicitly, CPU power scaling of AWS Lambda functions by testing various memory configurations. Crucially, AWS Lambda's resource model ties CPU power to memory allocation; increasing memory directly increases the proportional CPU resources available to your function and affects pricing. Therefore, understanding how network speed and compute resources scale with memory is vital for cost-effectively optimizing Lambda functions, especially those performing network-intensive tasks like data processing, API integrations, and external service interactions.

This python based project will create a docker container and deploy it to AWS Lambda using the AWS CLI (instructions below)

Invoking the function will return network speed information and vcpu count.

The netspeed-test.py code will loop through AWS Lambda memory sizes and output the results of the speed test for each iteration.

Requirements: Docker, Python3, Boto3, Virtualenv, AWS CLI

region=us-west-2
aws configure set region $region

git clone https://github.com/5tev3G/lambda-netspeed.git

cd lambda-netspeed

virtualenv venv
source venv/bin/activate

; required on mac
chmod -R o+rX .

docker build -t netspeed . --provenance=false   

aws ecr create-repository --repository-name netspeed --image-scanning-configuration scanOnPush=true --image-tag-mutability MUTABLE

registryId=$(aws ecr describe-repositories --repository-name netspeed --query "repositories[0].registryId" --output text)

aws ecr get-login-password --region $region | docker login --username AWS --password-stdin $registryId.dkr.ecr.$region.amazonaws.com 


docker push $registryId.dkr.ecr.$region.amazonaws.com/netspeed:latest        

aws iam create-role --role-name LambdaBasicExecutionRole --assume-role-policy-document file://LambdaBasicExecutionRole-Trust-Policy.json

aws iam attach-role-poldocker tag  netspeed:latest $registryId.dkr.ecr.$region.amazonaws.com/netspeed:latest
icy --policy arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole --role-name LambdaBasicExecutionRole

; --architectures x86_64 | arm64
aws lambda create-function --function-name netspeed \
    --package-type Image  \
    --timeout 60 \
    --architectures arm64 \
    --memory-size 256 \
    --code ImageUri=$registryId.dkr.ecr.$region.amazonaws.com/netspeed:latest  \
    --role arn:aws:iam::$registryId":role/LambdaBasicExecutionRole" 

aws lambda wait function-exists --function-name netspeed

aws lambda invoke --function-name netspeed response.json

cat response.json

; Here's how to change the resource footprint
aws lambda update-function-configuration --function-name  netspeed --memory-size 512

# run speed test loop
pip install boto3
python3 netspeed-test.py

# references
https://www.speedtest.net/apps/cli
https://pypi.org/project/speedtest-cli/
https://hub.docker.com/r/amazon/aws-lambda-python
https://docs.aws.amazon.com/lambda/latest/dg/images-create.html
https://docs.aws.amazon.com/lambda/latest/dg/troubleshooting-deployment.html

pip install speedtest-cli
aws lambda delete-function --function-name netspeed -