feat: roll instances + modify ASG sizes + add aqua

[Gowiem]

what

• Updates module to roll existing ASG instances when the launch template is updated (AMI, user-data, whatever)
• Adds aqua.yaml
• Removes the instance_count variable and uses the actual desired_capacity, min_size, max_size variables
• Bumps our pin of the AWS provider to 5.0+

why

• We want these instances to update and roll off / on when we make changes to the launch template. That is part of the point!
• Adds aqua so we can keep standard tooling versions across users.
• Removes the instance count var because it was holding back full control and helps in rolling instances
• Bump AWS provider to keep folks who are using this module moving forward + keeps us on the latest ASG resource config

references

• N/A

[gberenice]

Looks good!
A couple of small comment + I suggest to update the default type to t4g.nano. What do you think?

[gberenice]

I've never noticed that it's implemented like that. Good call 👍

[gberenice]

This is false by default.

What if we add a variable protect_from_scale_in, and set it to false in case a user wants to protect an instance, AND add the attribute scale_in_protected_instances to aws_autoscaling_group:

scale_in_protected_instances - (Optional) Behavior when encountering instances protected from scale in are found. Available behaviors are Refresh, Ignore, and Wait. Default is Ignore.

[Gowiem]

👍 Will do.

[gberenice]