Python tool for diagnosing AWS IoT Core & API Gateway latencies across AWS regions. Measures service response times, providing insights for optimal deployments based on region responsiveness.
This script is designed to measure the latency of two AWS services - AWS IoT Core and AWS API Gateway - across multiple AWS regions. By sending requests to these services and gauging the response time, it provides insights into their respective performances.
Upon execution, the script now also creates a report, encapsulating all vital statistics and results. This makes it easy to archive, share, or analyze results without having to rerun the script.
For users who don't have Python installed on their Windows machine, an executable file (.exe) is provided. Simply download the file and run it like any other Windows application to get the latency diagnostics. It will create a report file with name aws_latency_report.txt
- A predefined list of AWS regions with their corresponding human-readable names.
-
check_latency_iot: Measures the latency for the AWS IoT Core service in a designated region. -
check_latency_api_gateway: Gauges the latency for the AWS API Gateway service in a designated region.Both functions undertake a simple service-specific task multiple times (defaulted to 10 iterations) and then compute the average time taken (latency) for that task in the mentioned region. If a service isn't supported in a region, it's denoted as "Not supported".
get_all_region_latencies: Processes all regions, fetches latency values using the given service-specific function, and yields a sorted list of latencies.
- During execution, the script determines latencies for both AWS services across all regions and then showcases the results in an easy-to-understand manner. It also provides real-time updates on the iterations left, giving a clear picture of the progress.
This diagnostic tool is instrumental in understanding the responsiveness of these AWS services across diverse geographical zones. It stands beneficial for system architects and cloud strategists when making deployment choices.
The below output is a result of running the script from Edinburgh:
...
API Gateway Iteration 9 for eu-north-1: 0.0956 seconds. Total Remaining iterations: 1
API Gateway Iteration 10 for eu-north-1: 0.0862 seconds. Total Remaining iterations: 0
------------------------------------
Latencies for AWS IoT Core:
------------------------------------
Europe (London) (eu-west-2): 0.0455 seconds
Europe (Paris) (eu-west-3): 0.0525 seconds
Europe (Frankfurt) (eu-central-1): 0.0557 seconds
Europe (Ireland) (eu-west-1): 0.0583 seconds
Europe (Stockholm) (eu-north-1): 0.0819 seconds
Canada (Central) (ca-central-1): 0.1506 seconds
US East (N. Virginia) (us-east-1): 0.1562 seconds
US East (Ohio) (us-east-2): 0.1569 seconds
Asia Pacific (Singapore) (ap-southeast-1): 0.2214 seconds
US West (N. California) (us-west-1): 0.2246 seconds
Asia Pacific (Mumbai) (ap-south-1): 0.2412 seconds
US West (Oregon) (us-west-2): 0.2509 seconds
Asia Pacific (Tokyo) (ap-northeast-1): 0.3098 seconds
Asia Pacific (Seoul) (ap-northeast-2): 0.3653 seconds
Asia Pacific (Sydney) (ap-southeast-2): 0.3872 seconds
Asia Pacific (Osaka) (ap-northeast-3): Not supported
------------------------------------
Latencies for AWS API Gateway:
------------------------------------
Europe (London) (eu-west-2): 0.0705 seconds
Europe (Ireland) (eu-west-1): 0.0709 seconds
Europe (Paris) (eu-west-3): 0.0750 seconds
Europe (Frankfurt) (eu-central-1): 0.0786 seconds
Europe (Stockholm) (eu-north-1): 0.1121 seconds
Canada (Central) (ca-central-1): 0.1717 seconds
US East (N. Virginia) (us-east-1): 0.1728 seconds
US East (Ohio) (us-east-2): 0.1819 seconds
US West (N. California) (us-west-1): 0.2462 seconds
Asia Pacific (Singapore) (ap-southeast-1): 0.2500 seconds
US West (Oregon) (us-west-2): 0.2629 seconds
Asia Pacific (Mumbai) (ap-south-1): 0.2779 seconds
Asia Pacific (Osaka) (ap-northeast-3): 0.3400 seconds
Asia Pacific (Tokyo) (ap-northeast-1): 0.3477 seconds
Asia Pacific (Seoul) (ap-northeast-2): 0.3750 seconds
Asia Pacific (Sydney) (ap-southeast-2): 0.4136 seconds
Report generated and saved as 'report.txt'.
Process finished with exit code 0