# Galaxy API returning HTTP Error 500: Internal Server Error when fetching collection artifacts

**URL:** <https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526>\
**Category:** Get Help\
**Tags:** aws, awx, galaxy-ng\
**Created:** [October 24, 2026, 10:59am UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526 "2026-10-24T10:59:25Z")\
**Posts on this page:** 1\
**Showing post:** 13

<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:** [October 27, 2026, 9:48am UTC](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526/13 "2026-10-27T09:48:26Z")

</div>

What we are doing to improve this:

- Underlying issues: IAM life cycle management
- Monitoring & reporting: [Ansible Community Status page & Notifications - #18 by dbrennand](https://forum.ansible.com/t/ansible-community-status-page-notifications/45253/18)

---

_[View the full topic](https://forum.ansible.com/t/galaxy-api-returning-http-error-500-internal-server-error-when-fetching-collection-artifacts/46526)._