Soenke Ruempler

Looks like the underlying SSM Automation Client Libs have been updated, so we could now use SSM Automation to roll this out (should be similar to GD): 

Thanks for the PR. We will probably first have to: - implement a process to package Lambdas since we hit the 4096 inline Lambda CFN limit. See https://github.com/superwerker/superwerker/discussions/192 - have...

WIP in https://github.com/superwerker/superwerker/tree/backup-stack-resilient

We need to wait for another awsapilib release, since 3.0.0 is buggy. https://github.com/schubergphilis/awsapilib/pull/41 fixed this, but not released yet.

@yawn since you provided the script, could you please review this PR.

@gabeduke thanks for the hint. Do you think we can do anything on this side, or are we doomed to wait until AWS fixes this issue?

sorry, i don't have any idea, esp. in a windows env.

CloudFormation got ALB->Lambda support in the last release (https://aws.amazon.com/about-aws/whats-new/2019/04/aws-cloudformation-coverage-updates-for-amazon-ec2--amazon-ecs-a/). Here is a sample code how to use them: https://github.com/s0enke/cloudformation-templates/blob/master/templates/lambda-alb-sam-sample.yaml

Hi @costastf, you are correct, using AWS Transcribe would also need valid AWS credentials to work. It doesn't have to be the same account as the one that awsapilib is...

While waiting for this, I have documented a workaround here: https://ruempler.eu/2023/12/31/upgrade-aws-aurora-serverless-v1-to-v2-cloudformation-cdk/