Alex Shovlin

@adam-knights - we just released [Amazon.Lambda.DynamoDBEvents v3.1.1](https://www.nuget.org/packages/Amazon.Lambda.DynamoDBEvents/3.1.1), which should handle the "empty" case for `AttributeValue` when serializing to JSON.

@psdanielhosseini / @Dreamescaper - I separated this request over to https://github.com/aws/aws-lambda-dotnet/issues/1700. I'll leave this issue #1657 focused on going from the 3.0.0+ `DynamoDBEvent` to the SDK types, and then #1700...

The original issue based on the first stack trace should be fixed in [version 1.2.4](https://github.com/aws/aws-dotnet-deploy/releases/tag/1.2.4), which addressed the case of a deployment failure when deploying to an account+region without any...

Fixed in https://github.com/aws/aws-dotnet-deploy/releases/tag/1.21.13 via #837, we now timeout at a minute for the Docker and Node checks.

Sorry about the delay getting to this, we were just pointed at it internally. Merged into `develop` for the next V1 release, I'll reply again with the version number once...

`--proxy-url` has been added to V1 in 1.42.42 and V2 in 2.31.7. Thanks again @bendudz for the contribution!

We intentionally started with just `--use-device-code`. Our thinking was to shift usage to the newly recommended authorization code flow by requiring a more explicit intent to fallback rather than setting...

@Dalzhim - the Docker anecdote is helpful for prioritization, thanks for writing that up. @michaelbutleridt - `--use-device-code` for `aws configure sso` wasn't working at launch (2.22.0), but should be working...

Thanks for the contribution @bbodenmiller ! I've copied this change to the V2 docs as well via #9259.

We missed updating this when it was addressed, but 1.1.1zb was released in [2.24.12](https://github.com/aws/aws-cli/blob/v2/CHANGELOG.rst#22412). Additionally we moved to 1.1.1zc in [2.28.4](https://github.com/aws/aws-cli/blob/v2/CHANGELOG.rst#2284) yesterday.