413 Payload Too Large Error from Atlassian While Communicating with AWS Backend

[Lakshmi Narayanan N D]

Hello,

I’m encountering a 413 Payload Too Large error while using an Atlassian Forge app. The issue occurs when my Forge app, running on the Atlassian platform, attempts to communicate with a backend API hosted on AWS.

Details:

• Forge App Context: The app is deployed using Forge and is interacting with Jira Software (Cloud).
• Error Scenario:
  • From the Frontend (Forge), the request payload is sent to the Atlassian infrastructure.
  • Atlassian then communicates with my AWS backend API.
  • The 413 error is triggered during this communication.
• Backend API Details: Hosted on AWS API Gateway.
• Payload Size: Approximately Payload Size (in MB) : 1.4920
  
• I am passing image file in base64Image. Its throw error 413 too large.

Questions:

1. Are there known payload size limits enforced by Atlassian when using Forge apps?
2. Are there any recommendations to mitigate this issue (e.g., chunking payloads, modifying the app manifest)?
3. Is there a way to configure or increase the payload size limit for Forge apps?

Any guidance on resolving this issue would be greatly appreciated. Thank you!

[Nathan Phillips]

Hello @Lakshmi Narayanan N D,

Thanks for reaching out here on the Atlassian Community.

I wanted to let you know about the Atlassian Developer Community, specifically our community for all things Forge. 

I would actually recommend you reach out there as well.

[Lakshmi Narayanan N D]

Thanks