Markus Bergholz

> How should we structure the interface? Imo, keeping the API structure makes it easier to maintain the code along to boto3 and to add more features. Maybe there comes...

> That requires care to make the change backwards compatible. hm, what did you mean? Atm `s3_bucket` does not support any `expire_` parameters. And I noticed that the module has...

Ah oh boy. Blame me. 🙈 I was confused because the inition post included still `s3_bucket`. [But it's right. as mentioned above, the functionality must be included `s3_lifecycle`](https://github.com/ansible-collections/community.aws/issues/796#issuecomment-947901889) So the...

> If we want the multipart abort to match the API, should we also change expiration to match the API? > > Instead of: > > ``` > expiration_days: >...

I'm fine with both :)

Try ```yml - name: Create DB Instance community.aws.rds_instance: engine: aurora region: eu-west-1 db_instance_identifier: bla-db # unique name of a new node instance_type: db.t3.small # don't use t2. it's more expensive...

@jatorcasso do you plan to target also this? > Maybe username and password should be mutual exclusive with db_cluster_identifier this is not possible atm, because `db_cluster_identifier` is required. maybe *...

I guess some extra documentation about the difference between `rds_instance` and `rds_cluster` would be also helpful as a guidance for users

> Shouldn't be mutually exclusive instead? > > ``` > username > password and > new_db_instance_identifier > ``` > oh yeah, right. > and of course these ones (as you...

hmmm maybe you're right. At least the `EXAMPLE` section should be appended with a replica example. I think that helps people in that case. In case of RDS (_not aurora_)...