Hi @Shahzeena,
Thank you for reaching out on the SQL forum.
It looks like your issue is with the HTTP bindings in HTTP.sys rather than SSRS itself. A 503 from /ReportServer usually means the request isn’t reaching the SSRS service correctly.
A few things to check:
Verify URL reservations in HTTP.sys Run:
powershell
netsh http show urlacl
Make sure you see entries for both:
http://+:80/Reports
http://+:80/ReportServer If they’re missing, add them with:
powershell
netsh http add urlacl url=http://+:80/Reports user=DOMAIN\SSRSAccount
netsh http add urlacl url=http://+:80/ReportServer user=DOMAIN\SSRSAccount
Check SSRS config In RSReportServer.config, confirm <UrlReservations> includes HTTP as well as HTTPS. Since you removed UrlRoot, SSRS will auto‑detect, but it still needs valid reservations.
Authentication settings If Kerberos isn’t configured, disable Negotiate and leave NTLM only. /Reports can fall back gracefully, but /ReportServer often fails if Kerberos tickets aren’t available.
Firewall and security groups Double‑check that port 80 is open in both Windows Firewall and your AWS security group.
Event logs Look under System → HTTP Service in Event Viewer. HTTP.sys errors often show up there, not in SSRS logs.
Thanks,
Lakshmi.