#Help Needed: Persistent 403 S3 Error with TWITTER_MEDIA_UPLOAD_MEDIA Action

1 messages · Page 1 of 1 (latest)

sacred palm
#

Getting a persistent 403 Forbidden error when calling S3 HeadObject from the backend when using Action.TWITTER_MEDIA_UPLOAD_MEDIA.

Details:

Action: Action.TWITTER_MEDIA_UPLOAD_MEDIA
Error: An error occurred (403) when calling the HeadObject operation: Forbidden
Integration: twitter_media
Active Connection ID: cbae3a12-15f9-4b87-b2fb-951d3d67ad82 (Confirmed ACTIVE & explicitly passed to ComposioToolSet in Python SDK).
Troubleshooting Summary:

Tried passing file path (gets 403) and base64 (gets local SDK TypeError).
Error persists even when explicitly providing the correct active connection ID (cbae3a12-...) to ComposioToolSet.
Successfully posted text tweets using Action.TWITTER_CREATION_OF_A_POST and the other active twitter integration (when its specific connection ID was also explicitly provided).
Conclusion:

Seems like an internal S3 permission issue within the twitter_media integration backend, specifically for HeadObject. The error occurs after the SDK call, even with the correct connection.

Is this a known issue? Can the backend team check S3 permissions for this integration?

Thanks! 🙏

crimson saddleBOT
#

Hi, There was an issue with downloading files. I have reported this to the team and should be fixed soon.