[Enhancement] Upgrade remaining node.js 12 Lambda's

[Brian969]

Required Basic Info

• Accelerator Version: v1.5.3

Describe the bug

• inline Lambda's were left at v12 based on Lambda/CFN limits, remaining v12 Lambda's need to be upgraded with upcoming Nov15th deprecation of Lambda v12

[BlakePierantoni]

@Brian969 Any status on when this enhancement may be implemented? Would this change be made to 1.5.3 or would it release a 1.5.4?

[Brian969]

(see updated comment below)

[Brian969]

(Note updated guidance) This issue has been escalated to a top priority - RELEASED ~~we hope to have a release out within a week that incorporates a fix~~.

Customers must upgrade by ~~Nov 14th, 2022~~ Mar 31st, 2023 to avoid being impacted as follows:

• all customers attempting new ASEA installs using versions prior to v1.5.4-a will fail;
• all ASEA upgrades to a version of ASEA prior to v1.5.4-a will fail;
• all new sub-account creations will fail the State Machine (SM) until upgraded to v1.5.4-a;
• NEW: SM will fail (in all situations) in all pre-v1.5.0 installations (all Lambda’s are node12, not just inline Lambda’s)
• SM will continue to function on existing v1.5.0 to v1.5.3 ~~pre-v1.5.4~~ installs as long as a config file change is NOT made which causes the deployment or update of a Node.js 12 Lambda (i.e. adding a new ALB, a new sub-account, ~~others being researched,~~ but most config file changes allowed);
• v1.3.8, v1.3.9, and v1.5.0+ will continue to be upgradable directly to v1.5.4 or above after ~~Nov 14th, 2022~~ Mar 31st, 2023;
• Customers still running releases prior to v1.3.8 will be stuck post ~~Nov 14, 2022~~ Mar 31st, 2023.

[Brian969]

UPDATE: The AWS Lambda team has delayed the deprecation of Node.js 12 from Nov 15, 2022 to March 31, 2023 (documented here).

While this update pushes out the critical Nov 15th upgrade deadline, it should not reduce the urgency in getting to a supportable version of the ASEA. We strongly encourage all customers to upgrade to v1.5.4-a as soon as possible and to NOT wait until the new deadline.

AWS continues to recommend customers stay no more than 6-months behind the latest ASEA code release, and preferably no more than 3-months. We continue to recommend customers plan for an ASEA upgrade every quarter, and no more than semi-annually.

NOTE: The role trust policy changes still require an upgrade prior to Feb 14, 2023.