ssm-connector: better debugging and exception in exec_command file_transport_command methods

[ryancabrera]

Summary

I suspect there might be a bug in the file_transport_command method as any federated user I attempt to use with the SSM connector yields unhandled errors. Specifically, when the script attempt to curl the AnsiballZ.py script from the S3 bucket back to my instance using the presigned URL, the returned object is an XML file with an error (Unsure how to capture the .xml file and save the error)

I'm unsure if the issue is when the connector puts the file into s3 or when it copies the file from s3 to the ec2 instance. I can try to check out the bucket history in CloudTrail to see what is going on there but I believe the script itself should have additional debugging output that shows specifically what is happening with the get/puts in addition to having validation that a get/put is successful.

Issue Type

Feature Idea

Component Name

aws_ssm.py

Additional Information

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• [plugins/modules/aws_kms.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/aws_kms.py)
• [plugins/modules/aws_ssm_parameter_store.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/aws_ssm_parameter_store.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @116davinder @jillr @markuman @mikedlr @nathanwebsterdotme @ozbillwang @s-hertel @tremble
click here for bot help

[tremble]

The XML-related error is likely due to #1190 and should be fixed in release 5.2.0. Unfortunately because of where the failure you're seeing is there's not much we can do to improve the logging.