# AWS MediaLive module PR: Guidance needed on CI build failures

**URL:** <https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911>\
**Category:** Get Help\
**Tags:** github, aws\
**Created:** [July 16, 2025, 5:10pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911 "2025-07-16T17:10:52Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![buxell](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/buxell/32/9045_2.png) [@buxell](https://forum.ansible.com/u/buxell)\
**Post date:** [July 16, 2025, 5:10pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/1 "2025-07-16T17:10:52Z")

</div>

Hi AWS Ansible community,

I’ve submitted a PR to the community.aws repository that adds new MediaLive modules. While the code and tests work in my environment, I’m encountering two build failures that I need help addressing:

1. Documentation Build Failure

- I’ve noticed this same documentation build error appearing in other recently merged PRs
- Would appreciate guidance on whether this is a known issue that can be bypassed

1. Integration Test Permissions

- The integration tests run successfully in my environment using an IAM role with MediaLive permissions
- The automated build system appears to be failing due to insufficient IAM permissions for MediaLive and IAM
- Looking for confirmation if this is an environment-specific issue that needs to be addressed at the CI level

PR Link: [feat(medialive): add Elemental MediaLive modules to community collection by buxell · Pull Request #2318 · ansible-collections/community.aws · GitHub](https://github.com/ansible-collections/community.aws/pull/2318)

I’ve commented on the PR but haven’t received any response. Would greatly appreciate any guidance on how to proceed with these build failures or if they can be considered non-blocking for this contribution.

Thanks in advance for any help!

```auto

```

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 16, 2025, 7:44pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/2 "2025-07-16T19:44:30Z")

</div>

@buxell Welcome to the forum, thanks for your PR and pointing out this problems

@bianca I know you often help with `community.aws`.

It looks like [module documentation builds](https://github.com/ansible-collections/community.aws/actions/workflows/docs-pr.yml) have been failing in `community.aws` for a while. Is this a know issue?

Any ideas on the other questions that @buxell has?

---

<div class="post-metadata">

**Author:** ![bianca](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bianca/32/7233_2.png) [@bianca](https://forum.ansible.com/u/bianca)\
**Post date:** [July 16, 2025, 8:49pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/3 "2025-07-16T20:49:31Z")

</div>

Hi @buxell ! The module documentation build failures are a known issue, and are not typically considered a PR blocker.

Thanks for linking to your PR; I went ahead and approved the workflow run, so the full test suite should be running now.

---

<div class="post-metadata">

**Author:** ![gundalow](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/gundalow/32/99_2.png) [@gundalow](https://forum.ansible.com/u/gundalow)\
**Post date:** [July 18, 2025, 12:08pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/4 "2025-07-18T12:08:04Z")

</div>

@bianca Thanks, I think we’ve fixed the underlying documentation issues in [this pr](https://github.com/ansible-collections/community.aws/pull/2327).

Do you know how we update the IAM permissions

> Integration test failures in CI - I’ve confirmed these tests pass locally using an IAM role with the required MediaLive permissions. Looking for guidance on how to update the CI environment’s IAM role to include these permissions, if that is needed.

---

<div class="post-metadata">

**Author:** ![bianca](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/bianca/32/7233_2.png) [@bianca](https://forum.ansible.com/u/bianca)\
**Post date:** [July 18, 2025, 4:29pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/5 "2025-07-18T16:29:55Z")

</div>

I unfortunately don’t have the answer, but I’ve reached out to teammates who might know how to resolve this issue.

---

<div class="post-metadata">

**Author:** ![mgraves](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mgraves/32/1059_2.png) [@mgraves](https://forum.ansible.com/u/mgraves)\
**Post date:** [July 18, 2025, 4:39pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/6 "2025-07-18T16:39:04Z")

</div>

There is some information about updating CI permissions in [Guidelines for Ansible Amazon AWS module development — Ansible Community Documentation](https://docs.ansible.com/ansible/latest/collections/amazon/aws/docsite/dev_guidelines.html#aws-permissions-for-integration-tests).

---

<div class="post-metadata">

**Author:** ![buxell](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/buxell/32/9045_2.png) [@buxell](https://forum.ansible.com/u/buxell)\
**Post date:** [July 18, 2025, 5:54pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/7 "2025-07-18T17:54:51Z")

</div>

Thanks everyone for the prompt feedback! I’ve rebased the PR, and while the doc build is still failing, I’ve identified a few formatting issues in our docstrings that I can resolve. For the integration tests, I’ll be working on gathering the minimum required IAM permissions to submit a PR to mattclay/aws-terminator. I’ll update once these changes are complete.

---

<div class="post-metadata">

**Author:** ![buxell](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/buxell/32/9045_2.png) [@buxell](https://forum.ansible.com/u/buxell)\
**Post date:** [July 29, 2025, 6:05pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/8 "2025-07-29T18:05:37Z")

</div>

I’ve created a PR in the aws-terminator repository to add the required MediaLive IAM permissions that should resolve the integration test failures in CI.

> <https://github.com/mattclay/aws-terminator/pull/315>
>
> \# Add permissions for AWS Elemental MediaLive
> 
> This PR adds comprehensive supp…ort for AWS Elemental MediaLive by updating IAM policies and implementing resource cleanup functionality.
> 
> \## Changes
> 
> \### IAM Policy Updates
> \- \*\*\`aws/policy/security-services.yaml\`\*\*: Added \`AWSElementalMediaLiveFullAccess\` to allowed managed policies and consolidated several policy patterns to stay under max policy length
> \- \*\*\`aws/policy/application-services.yaml\`\*\*: Added MediaLive-specific permissions including:
> - Read permissions: \`medialive:Describe\*\`, \`medialive:List\*\`
> - Resource management: Create, delete, update, start/stop operations for channels, inputs, clusters, networks, and other MediaLive resources
> - Resource ARNs for MediaLive services
> 
> \### Resource Cleanup Implementation
> \- \*\*\`aws/terminator/application\_services.py\`\*\*: Added 8 new terminator classes for MediaLive resources:
> - \`MediaLiveChannel\` - Handles channel lifecycle with proper stop-before-delete logic
> - \`MediaLiveInput\` - Manages input sources
> - \`MediaLiveInputSecurityGroup\` - Security group cleanup
> - \`MediaLiveChannelPlacementGroup\` - Placement group management
> - \`MediaLiveCluster\` - Cluster resource cleanup
> - \`MediaLiveNetwork\` - Network resource management
> - \`MediaLiveNode\` - Node cleanup
> - \`MediaLiveSdiSource\` - SDI source management
> 
> \## Testing
> \- ✅ Sanity tests passed via \`tox\`
> \- ✅ Deployed IAM role with updated permissions
> \- ✅ MediaLive integration tests executed successfully
> 
> \<details\>
> \<summary\>Tox output (click to expand)\</summary\>
> ...
> 
> PLAY RECAP \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
> localhost : ok=2 changed=0 unreachable=0 failed=0 skipped=3 rescued=0 ignored=0   
> 
> pycodestyle: OK (0.32=setup\[0.06\]+cmd\[0.26\] seconds)
> pylint: OK (3.48=setup\[0.02\]+cmd\[3.47\] seconds)
> yamllint: OK (1.47=setup\[0.02\]+cmd\[1.45\] seconds)
> policy: OK (1.82=setup\[0.02\]+cmd\[0.83,0.98\] seconds)
> congratulations :) (7.21 seconds)
> \</details\>

I’ve also updated the docstrings in the original MediaLive modules PR and resolved the documentation formatting issues - the Doc Build is now passing successfully. Once the aws-terminator PR is merged, the integration tests should pass as well.

---

<div class="post-metadata">

**Author:** ![r363x](https://avatars.discourse-cdn.com/v4/letter/r/57b2e6/32.png) [@r363x](https://forum.ansible.com/u/r363x)\
**Post date:** [October 30, 2025, 7:04pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/9 "2025-10-30T19:04:09Z")

</div>

Hi everyone,

I’ve taken over the shepherding of @buxell’s PRs.  
His original `community.aws` PR `#2318` community.aws has been closed in favor of the new [#2353](https://github.com/ansible-collections/community.aws/pull/2353).

The PR still depends on `aws-terminator` [#315](https://github.com/mattclay/aws-terminator/pull/315) for its integration tests to pass. The latter has been up since late July with no activity, so I’m tagging @mattclay here in the hopes of getting his attention.

Thank you.

---

<div class="post-metadata">

**Author:** ![mattclay](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/mattclay/32/268_2.png) [@mattclay](https://forum.ansible.com/u/mattclay)\
**Post date:** [October 30, 2025, 9:39pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/10 "2025-10-30T21:39:36Z")

</div>

It looks like @alinabuzachis was reviewing the original `community.aws` PR, so I recommend following up with them on next steps for both PRs.

---

<div class="post-metadata">

**Author:** ![r363x](https://avatars.discourse-cdn.com/v4/letter/r/57b2e6/32.png) [@r363x](https://forum.ansible.com/u/r363x)\
**Post date:** [October 30, 2025, 11:27pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/11 "2025-10-30T23:27:10Z")

</div>

Thanks @mattclay.

Hi @alinabuzachis. Could you please spare some time to look at the two PRs from my last message?

---

<div class="post-metadata">

**Author:** ![r363x](https://avatars.discourse-cdn.com/v4/letter/r/57b2e6/32.png) [@r363x](https://forum.ansible.com/u/r363x)\
**Post date:** [November 6, 2025, 7:48pm UTC](https://forum.ansible.com/t/aws-medialive-module-pr-guidance-needed-on-ci-build-failures/43911/12 "2025-11-06T19:48:50Z")

</div>

Please, can someone else take a look at those PRs? I haven’t gotten any response from the previous reviewer in months.
