{"message": "Error uploading to s3: Client error '403 Forbidden' for url 'https://s3.amazonaws.com/<bucket>/<path>/Cloud%20Tooling/ugie-dev/2026-03-31/time-17-52-52-187284_chatcmpl-a642e753-bda8-482a-89b3-d63b8c449daa.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403", "level": "ERROR", "timestamp": "2026-03-31T17:52:59.582760", "stacktrace": "Traceback (most recent call last):\n File "/usr/lib/python3.13/site-packages/litellm/integrations/s3_v2.py", line 375, in async_upload_data_to_s3\n response = await self.async_httpx_client.put(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n url, data=json_string, headers=signed_headers\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n )\n ^\n File "/usr/lib/python3.13/site-packages/litellm/llms/custom_httpx/http_handler.py", line 579, in put\n raise e\n File "/usr/lib/python3.13/site-packages/litellm/llms/custom_httpx/http_handler.py", line 541, in put\n response.raise_for_status()\n ~~~~~~~~~~~~~~~~~~~~~~~~~^^\n File "/usr/lib/python3.13/site-packages/httpx/_models.py", line 829, in raise_for_status\n raise HTTPStatusError(message, request=request, response=self)\nhttpx.HTTPStatusError: Client error '403 Forbidden' for url 'https://s3.amazonaws.com/llm-gateway-dev-logs/dev/Cloud%20Tooling/ugie-dev/2026-03-31/time-17-52-52-187284_chatcmpl-a642e753-bda8-482a-89b3-d63b8c449daa.json'\nFor more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/403"}

TL;DR

The 403 error when uploading to S3 with a team name containing a space may be resolved by properly encoding or handling the space in the team alias prefix.

Guidance

• Verify that the issue is indeed caused by the space in the team name by testing with a team name without spaces.
• Check the documentation for S3 logging and team alias prefix to ensure that spaces are allowed and properly handled.
• Consider encoding the team name or using a different character in place of the space to avoid potential issues with URL encoding.
• Review the S3 bucket policy to ensure that it allows uploads from the LiteLLM proxy with the specified team alias prefix.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The root cause of the issue is likely related to the handling of spaces in the team alias prefix, but without further information, it is difficult to provide a definitive solution.

Recommendation

Apply a workaround, such as encoding the team name or using a different character in place of the space, as the issue is likely related to the handling of special characters in the team alias prefix.