You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ ansible-galaxy collection list
# /usr/share/ansible/collections/ansible_collectionsCollection Version----------------------- -------amazon.aws 7.3.0
AWS SDK versions
$ pip show boto boto3 botocoreWARNING: Package(s) not found: botoName: boto3Version: 1.34.42Summary: The AWS SDK for PythonHome-page: https://github.com/boto/boto3Author: Amazon Web ServicesAuthor-email:License: Apache License 2.0Location: /usr/local/lib/python3.9/site-packagesRequires: botocore, jmespath, s3transferRequired-by:---Name: botocoreVersion: 1.34.42Summary: Low-level, data-driven core of boto 3.Home-page: https://github.com/boto/botocoreAuthor: Amazon Web ServicesAuthor-email:License: Apache License 2.0Location: /usr/local/lib/python3.9/site-packagesRequires: jmespath, python-dateutil, urllib3Required-by: boto3, s3transfer
Configuration
$ ansible-config dump --only-changed
OS / Environment
No response
Steps to Reproduce
---
plugin: amazon.aws.aws_ec2regions:
- us-east-1hostnames:
- name: tag:Nameprefix: ""compose:
ansible_host: private_ip_addressgroups:
linux: "'windows' not in platform_details|lower"windows: "'windows' in platform_details|lower"use_ssm_inventory: true
Expected Results
Above inventory source code in AWX fetch ssm_inventory host variable as below.
ssm_inventory: agent_type: amazon-ssm-agent agent_version: 3.2.2222.0 computer_name: wmgtpadoagt01.WORKGROUP instance_id: i-032a8eda18421b1e4 instance_status: Active ip_address: 10.255.26.83 platform_name: Microsoft Windows Server 2022 Datacenter platform_type: Windows platform_version: 10.0.20348 resource_type: EC2Instance
Actual Results
No ssm_inventory host variable
Code of Conduct
I agree to follow the Ansible Code of Conduct
The text was updated successfully, but these errors were encountered:
Based on the issue reported in #1713 , I see a fix is merged through #1957
Now, we don't see failures in inventory sync when the count of EC2 instances in an account is more than the allowed limit of instances (default value is 40) for SSM send_command, but no host variables are fetched through SSM now. The scenario is same even if the count of instances in the account is lesser than 40 - which means the parameter use_ssm_inventory is not at all effective now.
@vijayreddiar I am unable to reproduce this locally, the ssm_inventory variable is returned as expected for all managed instances with inventory enabled -- note though that ssm_inventory is not present in the host variables for any instances that are not managed with inventory enabled. Just to confirm, does your Systems Manager Inventory include the instances for which you are not seeing that host variable in the result?
@vijayreddiar I am unable to reproduce this locally, the ssm_inventory variable is returned as expected for all managed instances with inventory enabled -- note though that ssm_inventory is not present in the host variables for any instances that are not managed with inventory enabled. Just to confirm, does your Systems Manager Inventory include the instances for which you are not seeing that host variable in the result?
My bad, I had randomly checked a few instances which were not managed instances, hence not part of SSM Inventory due to a change in IaC (remained unnoticed). Thanks for pointing out.
Summary
EC2 Inventory Plugin parameter
use_ssm_inventory
is not effective irrespective of the count of instances in the account.Issue Type
Bug Report
Component Name
aws_ec2
Ansible Version
Collection Versions
AWS SDK versions
Configuration
$ ansible-config dump --only-changed
OS / Environment
No response
Steps to Reproduce
Expected Results
Above inventory source code in AWX fetch
ssm_inventory
host variable as below.Actual Results
No
ssm_inventory
host variableCode of Conduct
The text was updated successfully, but these errors were encountered: