ansible-navigator VS amazon.aws

If you need out-of-core modules in an air-gapped environment, you can use a machine with external network access to prepare your execution environment (EE) which is basically a docker image using ansible-builder, add all modules/collections you need, export the resulting image, and import it into your air-gapped server. You can then use ansible-navigator to run Ansible playbooks using that EE.

Please do check out the release notes for all the updates.

Projects to make it easier to write and test Ansible Content. Includes VScode extension, language server, ansible-lint, molecule, ansible-navigator and potentially other development goodies. To see what's planned, and how you can help checkout the foundation-devtools project board

But this does not mean there is no way of using EEs from the command line. For example, Ansible Runner can run playbooks and ad hoc commands using EEs since version 2, but the preferred tool for using EEs locally is Ansible Navigator.

... As a base before mapping in ssh keys. Also, have a look at navigator which works with execution environments: https://github.com/ansible/ansible-navigator

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.