Closed alexwlchan closed 11 months ago
As of 2023-10-25
# digitisation (404315009621)
AV-Preingest-Copy
AV-Preingest-Convert
# platform (760097843905)
buildkite-elasticstack-na-AzRebalancingSuspenderFu-Ggu8z7mMGpFh
buildkite-elasticstack-sc-AzRebalancingSuspenderFu-LAWvOJKJF1Ij
calm_window_generator // upgraded via tf
buildkite-elasticstack-AzRebalancingSuspenderFunct-o116nKtDOJPv
deletion_check_initiator // upgraded via tf
As of 2023-10-30
# digitisation (404315009621)
AV-Preingest-Copy
AV-Preingest-Convert
# platform (760097843905)
buildkite-elasticstack-na-AzRebalancingSuspenderFu-Ggu8z7mMGpFh
buildkite-elasticstack-sc-AzRebalancingSuspenderFu-LAWvOJKJF1Ij
buildkite-elasticstack-AzRebalancingSuspenderFunct-o116nKtDOJPv
As of 2023-10-30
# digitisation (404315009621)
AV-Preingest-Copy
AV-Preingest-Convert
AV-Preingest-Copy
AV-Preingest-Convert
Upgraded directly in the AWS console as the lambdas were created there initially
https://wellcome.slack.com/archives/C3TQSF63C/p1698668957186089
Well, actually...
Checks lambdas with python < 3.9
from config import get_all_aws_accounts
if __name__ == "__main__":
for account_id, account_name, sess in get_all_aws_accounts():
print(f"\n# {account_name} ({account_id})\n")
lambda_client = sess.client("lambda")
for page in lambda_client.get_paginator("list_functions").paginate():
for function in page["Functions"]:
runtime = function.get("Runtime")
if runtime != None and runtime.startswith('python') and int(runtime.split(".")[1]) < 9:
print(function["FunctionName"])
print(runtime)
# platform (760097843905)
sierra_orders_window_generator // updated to 3.9 via aws console 2023-11-07
sierra_holdings_window_generator // updated to 3.9 via aws console 2023-11-07
sierra_bibs_window_generator // updated to 3.9 via aws console 2023-11-07
sierra_items_window_generator // updated to 3.9 via aws console 2023-11-07
// NOTE: all the above were detected by terraform when a subsequent 'apply' was run.
reporting_miro_transformer
reporting_miro_inventory_transformer // looks inactive, no invocation in last 6 months
lambda-v2_lambda_public // looks inactive, no invocation in last 6 months
lambda-v2_lambda_vpc // looks inactive, flagged as "idle" in console
miro_migration // looks inactive, no invocation in last 6 months
# workflow (299497370133)
archivematica-s3_start_transfer-staging
archivematica-start_test_transfer-staging
archivematica-transfer_monitor-prod
archivematica-start_test_transfer-prod
archivematica-transfer_monitor-staging
archivematica-s3_start_transfer-prod
# platform (760097843905)
update_embargoed_holdings
# storage (975596993436)
end_to_end_bag_test
daily_reporter
end_to_end_bag_test--staging
digital_production_report
2023-11-13 remaining:
# platform (760097843905)
reporting_miro_transformer -> python3.6
update_embargoed_holdings -> python3.8
# storage (975596993436)
end_to_end_bag_test -> python3.8
daily_reporter -> python3.8
end_to_end_bag_test--staging -> python3.8
digital_production_report -> python3.8
# platform (760097843905)
reporting_miro_transformer -> python3.6
update_embargoed_holdings -> python3.9 as of 2023-11-13
# storage (975596993436)
end_to_end_bag_test -> python3.8
daily_reporter -> python3.8
end_to_end_bag_test--staging -> python3.8
digital_production_report -> python3.8
All lambdas are at least on python3.9 except
reporting_miro_transformer on Python3.9 as of 2023-11-30, done though the AWS console as lambda is not terraformed
reporting_miro_inventory_transformer // looks inactive, no invocation in last 6 months
lambda-v2_lambda_public // looks inactive, no invocation in last 6 months
lambda-v2_lambda_vpc // looks inactive, flagged as "idle" in console
miro_migration // looks inactive, no invocation in last 6 months
We've had an email from AWS about some of our Lambdas on the Python 3.7 runtime:
I wrote a short script in the AWS account infra repo that looks for matching Lambdas in all of our accounts:
Here's the interesting output:
All of these Lambdas should be upgraded to newer versions of Python.