gns-science / nshm-kororaa-apigw Goto Github PK

configure project for

• pretty / linting checks local and GHA
• (and badges)
• coverage.io
• Version tags
• add badges top README

use PINO library as per NSHM_WEKA_APIGW

investigate

see below from AMAZON..

Hello,

We are contacting you as we have identified that your AWS Account currently has one or more AWS Lambda functions using the Node.js 16 runtime.

We are ending support for Node.js 16 in Lambda on June 12, 2024. This follows Node.js 16 End-Of-Life (EOL) reached on September 11, 2023 [1].

As described in the Lambda runtime support policy [2], end of support for language runtimes in Lambda happens in several stages. Starting on June 12, 2024, Lambda will no longer apply security patches and other updates to the Node.js 16 runtime used by Lambda functions, and functions using Node.js 16 will no longer be eligible for technical support. Also, Node.js 16 will no longer be available in the Console, although you can still create and update functions using Node.js 16 via AWS CloudFormation, the AWS CLI, AWS SAM, or other tools. Starting July 15, 2024, you will no longer be able to create new Lambda functions using the Node.js 16 runtime. Starting August 15, 2024, you will no longer be able to update existing functions using the Node.js 16 runtime.

We recommend that you upgrade your existing Node.js 16 functions to Node.js 20 before June 12, 2024. A list of your Node.js 16 functions can be found in the 'Affected resources' tab of the AWS Health Dashboard.

End of support does not impact function execution. Your functions will continue to run. However, they will be running on an unsupported runtime which is no longer maintained or patched by the AWS Lambda team.

This notification is generated for functions using the Node.js 16 runtime for the $LATEST function version. The following command shows how to use the AWS CLI [3] to list all functions in a specific region using Node.js 16, including published function versions. To find all such functions in your account, repeat this command for each Region:

aws lambda list-functions --region us-west-2 --output text --query "Functions[?Runtime=='nodejs16.x'].FunctionArn"

From 180 days before deprecation, you can also use Trusted Advisor to identify all functions using the Node.js 16 runtime, including published function versions [4].

If you have any concerns or require further assistance, please contact AWS Support [5].

[1] https://github.com/nodejs/Release
[2] https://docs.aws.amazon.com/lambda/latest/dg/runtime-support-policy.html
[3] https://aws.amazon.com/cli/
[4] https://docs.aws.amazon.com/awssupport/latest/user/security-checks.html#aws-lambda-functions-deprecated-runtimes
[5] https://aws.amazon.com/support

Sincerely,
Amazon Web Services

Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210

We want the new stitched API gateway using a single API gateway instance

• https://www.serverless.com/blog/api-gateway-multiple-services/
• https://www.serverless.com/blog/serverless-api-gateway-domain/
• https://www.serverless.com/examples/aws-node-shared-gateway

TODO:

• get new domain / certificate configured (w GNS IT)
• configure gateways nshm-api-test serverless domain manager (own repo ??)
• configure nshm-kororaa-api to use the new gateway
• deploy kororaa-api to new gateway
• deploy toshi-api to new gateway
• deploy solvis-api to new gateway

new composite features

You have an SSL/TLS certificate from AWS Certificate Manager in your AWS account that expires on Feb 15, 2024 at 23:59:59 UTC. This certificate includes the primary domain nshm-api-test.gns.cri.nz and a total of 1 domains.

We want to be sure we're using stitching properly: Some testing & decisions are needed:

• can we get by without subschema PREFIXES?
• can they be added later as non-breaking change
• Should all our subschemas use Relay/node what if they
• #25
• remove unused (SMS etc)

When maximum rate < 0 no solution analysis is returned.
Example query:
{ "query": "query FaultModelPageSolvisQuery(\n $solution_id: ID!\n $location_codes: [String]\n $radius_km: Int\n $minimum_mag: Float\n $maximum_mag: Float\n $minimum_rate: Float\n $maximum_rate: Float\n $location_colour: String\n $fault_colour: String\n) {\n SOLVIS_analyse_solution(input: {solution_id: $solution_id, location_codes: $location_codes, radius_km: $radius_km, minimum_mag: $minimum_mag, maximum_mag: $maximum_mag, minimum_rate: $minimum_rate, maximum_rate: $maximum_rate, location_area_style: {stroke_color: $location_colour, stroke_width: 1, stroke_opacity: 0.5, fill_color: $location_colour, fill_opacity: 0.5}, fault_trace_style: {stroke_color: $fault_colour, stroke_width: 3, stroke_opacity: 1}}) {\n analysis {\n fault_sections_geojson\n solution_id\n location_geojson\n }\n }\n}\n", "variables": { "fault_colour": "red", "location_codes": [], "location_colour": "grey", "maximum_mag": 10, "maximum_rate": -2, "minimum_mag": 6, "minimum_rate": -20, "radius_km": 0, "solution_id": "U2NhbGVkSW52ZXJzaW9uU29sdXRpb246MTIwNzU3" } }

We want finer grained auth, see https://rahmanfadhil.com/deploy-graphql-aws-lamda/

NB possibly the warmup function calls? this error occurs about once every 5m .

eg

https://ap-southeast-2.console.aws.amazon.com/cloudwatch/home?region=ap-southeast-2#logsV2:log-groups/log-group/$252Faws$252Flambda$252Fnshm-kororaa-apigw-test-app/log-events/2023$252F04$252F27$252F$255B$2524LATEST$255Dff698d4b000e4b71aed2d3e3c73f5def$3FfilterPattern$3D

2023-04-27T21:30:30.639Z	d82de34a-7de5-40a5-9851-e75e030d49c3	ERROR	Invoke Error 	
{     "errorType": "Error",     
      "errorMessage": "Unable to determine event source based on event.",    
      "stack": ...