amazon.aws VS Ansible

amazon.aws 6.4.0 has been released with a new module named amazon.aws.ec2_key_info, some documentation improvements, new features and bugfixes (see changelog for details).

amazon.aws 5.5.1 has been released with several bugfixes (see changelog for details).

amazon.aws 5.5.0 has been released with a number of bugfixes, new features and new modules. This is the last planned minor release prior to the release of version 6.0.0 (see changelog for details).

amazon.aws 5.4.0 has been released with bugfixes for the ec2_metadata_facts, ec2_vol, rds_instance and route53_info modules, as well as feature enhancements for the ec2_spot_instance and route53_health_check modules - see changelog for details.

Hi folks! I'm one of the docs writers for community Ansible (aka docs.ansible.com, not access.redhat.com). It sounds like you've found a place to log your docs problems already but I did open an issue on the amazon.aws collection directly to handle the examples that aren't quoted for `filters` at https://github.com/ansible-collections/amazon.aws/issues/1331

The amazon.aws collection version 5.0.0 has been released. See the changelog for details on new modules and features.

amazon.aws 4.0.0 has been released with some new features, bugfixes, breaking changes and deprecated features. The amazon.aws collection has also dropped support for botocore<1.20.0 and boto3<1.17.0 (see changelog for details).

amazon.aws 2.2.0 has been released with bug-fixes (see changelog for details).

amazon.aws 3.1.1 has been released with some new features, bugfixes and a deprecation (see changelog for details). 3.1.0 failed to publish on Galaxy, hence, we had to bump the release version.

The AWS community has begun planning for the 4.0.0 releases of amazon.aws and community.aws. Please see the linked issues for more details or to get involved.

Ansible is an open-source IT automation tool that simplifies application deployment, cloud provisioning, and configuration management across diverse environments. It uses a declarative language to describe the desired state of the system, and then takes the necessary actions to achieve that state. Ansible has become incredibly popular due to its simplicity, agentless architecture, and extensive community support. Document: ansible.com, ansible basics

Ansible v2.16

Ansible is a tool used to help manage software automation processes, configuration management across machines, deployment as well as remote execution of commands and scripts. In sports, Ansible operates as the coach of your team by providing strategies (playbooks), and actions, and ensuring the smooth execution of tasks across your infrastructure, just like a coach guides and directs players (Servers)during a game.

They support for-if from python, too: https://jinja.palletsprojects.com/en/3.1.x/templates/#loop-f... but I haven't tried the "recursive" keyword to know if ansible supports that. I say "ansible supports that" because they don't just drop jinja2 into ansible and call it a draw, they have a bunch of custom execution integrations: https://github.com/ansible/ansible/blob/v2.16.3/lib/ansible/...

To manage a VM, you can use something as simple as just manual actions over SSH, or can use tools like Ansible, Hashicorp's Packer and Terraform or other automations. For an app where there is minimal load and security/reliability concern, VMs are still a great option that provide a lot of value for the buck

In this article's context, it is simply a tool that provides a declarative way to automate your machine/OS to configure the development machine as you want (install package, modify the configuration, etc). Examples of these tools are Ansible, Puppet, etc.

Now we're getting more tangential, but for years, Ansible releases were named for Van Halen songs (see old Changelog here: https://github.com/ansible/ansible/blob/v1.8.4/CHANGELOG.md)

In the lab to follow, we'll quickly provision a 3-node kubeadm cluster (1 master, 2 workers) on the cloud provider of your choice using an automation stack comprised of OpenTofu and Ansible, then deploy Rook Ceph using the official Helm charts and confirm that we are now able to successfully create CSI volume snapshots from PVCs by reusing the MinIO example from our last article.