# AWS SSM Connection Refactoring & Plugin Promotion

**URL:** <https://forum.ansible.com/t/aws-ssm-connection-refactoring-plugin-promotion/39930>\
**Category:** Collection Development\
**Tags:** aws-wg, aws\
**Created:** [January 30, 2025, 3:00pm UTC](https://forum.ansible.com/t/aws-ssm-connection-refactoring-plugin-promotion/39930 "2025-01-30T15:00:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alinabuzachis](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/alinabuzachis/32/1243_2.png) [@alinabuzachis](https://forum.ansible.com/u/alinabuzachis)\
**Post date:** [January 30, 2025, 3:00pm UTC](https://forum.ansible.com/t/aws-ssm-connection-refactoring-plugin-promotion/39930/1 "2025-01-30T15:00:03Z")

</div>

Hi everyone,

We’d like to provide an update on the **aws\_ssm** connection plugin, which was originally proposed for **promotion** in [this GitHub issue](https://github.com/ansible-collections/amazon.aws/issues/2394). It was initially considered for **amazon.aws. 9.0.0** , but due to limited capacity, its promotion has been postponed to **amazon.aws 10.0.0**.

### Current Plan

As part of this effort, we are working on **refactoring** the module within **community.aws** to improve maintainability and ensure a smoother promotion process. To facilitate this, we will:

1. **Merge the refactor PRs into the main branch** – This will lay the foundation for a more robust and maintainable plugin.
2. **Address critical bugs before migration** – Ensuring stability before moving forward is a priority.
3. **Backport the refactoring PRs** – As a general rule, we include major refactoring only in major releases. However, we are making an exception in this case, as we believe backporting these changes will not introduce any issues.

### Request for Feedback

We’d love to hear your thoughts!

- Do you have any **objections** to this approach?
- Are there any **suggestions** or concerns we should consider?
- Any **additional feedback**?

---

<div class="post-metadata">

**Author:** ![GomathiselviS](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gomathiselvis/32/544_2.png) [@GomathiselviS](https://forum.ansible.com/u/GomathiselviS)\
**Post date:** [January 30, 2025, 3:04pm UTC](https://forum.ansible.com/t/aws-ssm-connection-refactoring-plugin-promotion/39930/2 "2025-01-30T15:04:29Z")

</div>

I agree with backporting the refactor PRs, as it would make backporting the bug fix PRs much easier.