Markus Bergholz

Let's plan to release community.aws 3.3.0 and 2.5.0 on may 30th.

> Release ETA Release Plan > 4.0.0 2022-06-23 #895 > 3.3.0 2022-05-30 > 2.5.0 2022-05-30 > > [Amazon Web Services Working Group Agenda - 2022](https://github.com/ansible/community/issues/654) community.aws [3.3.0](https://github.com/ansible-collections/community.aws/releases/tag/3.3.0) and [2.5.0](https://github.com/ansible-collections/community.aws/releases/tag/2.5.0) has...

community.aws 2.6.0, 3.4.0 and 4.0.0 has been released.

Theoretically the parameter `cache_policy_id: 658327ea-f89d-4fab-a63d-7e88639e58f6` works already. But the default values for min/max/default_ttl that are added, are incompatible together.

> ansible_aws_ssm_bucket_name: nghc-sbox2-s3

I think all described possibilities will break backwards compatility. A new module is not a solution and will gain entropy of the aws modules. The only way to implement it,...

There is a none-active PR left in community.aws that is targeting in this direction: * PR https://github.com/ansible-collections/community.aws/pull/461 * comment related to this issue: https://github.com/ansible-collections/community.aws/pull/461#issuecomment-803266114

Is this attribute supported by all loadbalancers? ALB, Classic, Network...? I Cannot find any informations. If yes - it might be easy to implement.

The big problem imho is, that we don't know if a target group is actually attached to an ALB, Classic LB or Network LB. Similar to: https://github.com/ansible-collections/community.aws/pull/282 I need to...

@gen2fish Thank you for the PR. The sanity checks are failing ``` ERROR: Found 2 validate-modules issue(s) which need to be resolved: ERROR: plugins/modules/lambda.py:0:0: doc-missing-type: Argument 'image_uri' in argument_spec uses...