[BUG][Functional] Perimeter ALB Forwarding Lambda Function Error: Runtime.Unknown about aws-secure-environment-accelerator HOT 6 CLOSED

Hi Brian, we fixed the Prod issue by increasing the Lambda memory to 512 MB.
Please consider implementing that via code.
Thanks!

from aws-secure-environment-accelerator.

Hi, I'm not sure, I haven't run it since fixing the Lambda memory manually.
I assume (based on the nature of CFN) that if the CFN synthesized template is not changing, CFN will not detect a drift and will leave the manual fix alone. Once you release 1.5.8-e (with the memory increase) then CFN will see a change and will attempt to update the function, then the function will be 'updated' from 512 (already done manually) to 512 (from the code) and the drift will be gone.
BTW, how's the LZA upgrade script going?
Thanks!

from aws-secure-environment-accelerator.

Ho, i'm not involved with ASEA or LZA development, i'm a customer using ASEA for his landing zone :)

from aws-secure-environment-accelerator.

Thank's Ray to report the problem. We just updated to 1.5.8-d and got the problem. We also increased the lambda memory to 512mb.

Do you know if running the statemachine (like creating a new account) will overide the change?

Regards,

Eric

from aws-secure-environment-accelerator.

We are noticing that newly created forwarding rules do not seem to work after this update. We have increased the memory on the Lambda function to 512MB which got rid of the errors, but if we create a new forwarder, we see the following behaviour:

• Rule is successfully created on the ELB.
• Target group is successfully created.
• Target group does NOT register any targets - we have waited up to a couple hours with no change.

When checking the table entry in DynamoDB, the targetGroupIpAddresses entry never gets updated with any addresses.

Is anyone else seeing this behaviour?

from aws-secure-environment-accelerator.

Fixed in 1.5.9

from aws-secure-environment-accelerator.