Nuru

Yes, the breaking changes in AWS provider v4.0.0 did, in fact, break this module and many others. You should pin your providers in your top-level components, using either version blocks...

This is, in fact, the plan. This module will be refactored to use https://github.com/cloudposse/terraform-aws-cloudfront-cdn and https://github.com/cloudposse/terraform-aws-s3-bucket as part of the migration to support AWS Terraform Provider v4.

@osterman This is not a bad idea. We could run a back-fill task, maybe with a date/version count limit so we don't go back too far. We will not get...

I think we keep the current `VERSION` file as the latest we have (or want to build) and continue auto-updating it as we have. Then, separately, we run a backfill...

@osterman if you still want to do this, we are now in pretty good shape to accomplish it. We could generate the pages along with `README.md`, just need a template...

We are not going to support this use case by adding even more inputs, however we welcome documentation about how to achieve the desired results with the current module. @darkwizzarddude...

As stated in the README, the number of different possibilities for creating subnets is overwhelming, and we do not want to complicate this module even further by supporting rare use...

@chrisjaimon2012 #203 restores operation of SMS and TOTP 2FA, but not U2F. I did not write the previous U2F integration and am not quite sure how it worked, so maybe...

I do not understand the problem. Why would the security group name change? How is creating a new security group with a new name solving the problem?

Any progress on this? Not that my list of accounts is too big for the window, this is a bigger annoyance than before.