fix(sdk): cherrypick default az for wing app

[garysassano]

Currently, when a new Wing app is created for AWS targets, it's left up to AWS to choose a random AZ in which to deploy the private and public subnets. With this change, we tell AWS that we always want to deploy to the first AZ of whatever region specified by the user, which is generally the one that has the broadest range of services available.

Closes #4126

By submitting this pull request, I confirm that my contribution is made under the terms of the Wing Cloud Contribution License.

[monadabot]

Console preview environment is available at https://wing-console-pr-4151.fly.dev 🚀

Updated (UTC): 2023-09-19 09:39

[hasanaburayyan]

@garysassano thanks for the fix, curious did you get a chance to try deploying to AWS with this change?

Side note: I think this is the right approach to fix the bug Sebastian ran into, but I think eventually we need to rethink the approach, creating this simple VPC on the user's behalf is great but we need to offer the user a way to customize their VPC. (something easier than using a Wing plugin)

[garysassano]

@hasanaburayyan I tested the code and it works. For the future, I think Wing will have to provide some external network modules that are cloud-specific (something like ex.AWSNetwork, ex.GCPNetwork, etc.) which allow you to customize where your Wing app resources are created.

[hasanaburayyan]

@garysassano thanks for the fix!

[mergify]

Thanks for contributing, @garysassano! This PR will now be added to the merge queue, or immediately merged if garysassano/fix-redis-az is up-to-date with main and the queue is empty.

[mergify]

Thanks for contributing, @garysassano! This PR will now be added to the merge queue, or immediately merged if garysassano/fix-redis-az is up-to-date with main and the queue is empty.

[monadabot]

Congrats! 🚀 This was released in Wing 0.31.5.