Amazon AWS Collection 10.3.1 — Bugfixes for S3, ASG, and KMS
Introduction
The amazon.aws collection version 10.3.1 was released in May 2026 with important bugfixes for four modules: s3_object_info (duplicate dictionary fix), autoscaling_group (key assignment reliability), kms_key (key assignments), and CloudFront module utilities (TypeError fix). If you manage AWS infrastructure with Ansible, upgrade to avoid hitting these bugs.
What's Fixed
s3_object_info — Duplicate Dictionary Keys
Previous versions could produce duplicate keys in the returned dictionary when listing S3 objects with common prefixes, leading to lost data in results.
# Now returns correct, deduplicated results
- name: List S3 objects
amazon.aws.s3_object_info:
bucket_name: my-bucket
prefix: "backups/2026/"
register: s3_objects
- name: Show object count
ansible.builtin.debug:
msg: "Found {{ s3_objects.s3_keys | length }} objects"
autoscaling_group — Key Assignment Reliability
Fixed an issue where Auto Scaling Group configuration could fail with duplicate key assignments when updating launch templates or mixed instance policies.
- name: Update ASG (now reliable)
amazon.aws.autoscaling_group:
name: web-asg
launch_template:
launch_template_name: web-lt
version: "$Latest"
min_size: 2
max_size: 10
desired_capacity: 4
vpc_zone_identifier:
- subnet-abc123
- subnet-def456
kms_key — Key Assignment Fix
Resolved duplicate key assignment issues when managing KMS keys with complex policies and grants.
- name: Create KMS key (fixed)
amazon.aws.kms_key:
alias: my-app-key
description: "Encryption key for my application"
key_usage: ENCRYPT_DECRYPT
key_spec: SYMMETRIC_DEFAULT
tags:
Environment: production
Application: myapp
state: present
CloudFront Utilities — TypeError Fix
Fixed a TypeError in CloudFront module utilities that could occur during distribution configuration updates.
- name: Update CloudFront distribution (fixed)
amazon.aws.cloudfront_distribution:
distribution_id: E1234567890
origins:
- id: my-origin
domain_name: my-bucket.s3.amazonaws.com
default_cache_behavior:
target_origin_id: my-origin
viewer_protocol_policy: redirect-to-https
state: present
Upgrade
# Upgrade to 10.3.1
ansible-galaxy collection install amazon.aws:10.3.1 --force
# Or update requirements.yml
# collections:
# - name: amazon.aws
# version: ">=10.3.1,<11.0.0"
# Verify installed version
ansible-galaxy collection list amazon.aws
# Check current version in playbook
- ansible.builtin.debug:
msg: "{{ lookup('ansible.builtin.pipe', 'ansible-galaxy collection list amazon.aws 2>/dev/null') }}"
Version History (Recent)
| Version | Date | Highlights |
|---|---|---|
| 10.3.1 | May 2026 | S3, ASG, KMS, CloudFront bugfixes |
| 10.3.0 | Apr 2026 | New features |
| 10.2.0 | Mar 2026 | EC2 improvements |
| 10.0.0 | Jan 2026 | Major release, breaking changes |
Should You Upgrade?
| If you use... | Action |
|---|---|
s3_object_info with prefixes | Upgrade immediately — data loss risk |
autoscaling_group updates | Upgrade — prevents config failures |
kms_key management | Upgrade — prevents policy errors |
| CloudFront distributions | Upgrade — prevents TypeError crashes |
| None of the above | Low priority but recommended |
Best Practices
- Pin to 10.3.1+ — avoid the fixed bugs
- Test before upgrading major versions — 10.x → 11.x may have breaking changes
- Use requirements.yml —
">=10.3.1,<11.0.0"for safe updates - Check changelogs — review before upgrading:
ansible-galaxy collection info amazon.aws
Conclusion
amazon.aws 10.3.1 is a bugfix-only release that resolves data integrity issues in S3 object listing, reliability problems in Auto Scaling Group updates, KMS key management fixes, and a CloudFront TypeError. If you manage AWS infrastructure with Ansible, upgrade to 10.3.1 to avoid these bugs — especially the s3_object_info duplicate dictionary issue which can cause silent data loss.