litellm - 💡(How to fix) Fix [Bug]: Service must be in list - S3 callback does not work [1 participants]

10:46:07 - LiteLLM Proxy:ERROR: _health_endpoints.py:465 - litellm.proxy.proxy_server.health_services_endpoint(): Exception occured - 400: {'error': "Service must be in list. Service=s3 not in typing.Union[typing.Literal['slack_budget_alerts', 'langfuse', 'langfuse_otel', 'slack', 'openmeter', 'webhook', 'email', 'braintrust', 'datadog', 'datadog_llm_observability', 'generic_api', 'arize', 'sqs'], str]"}

TL;DR

The S3 callback issue may be due to the service not being recognized in the allowed list, and modifying the service list or updating the LiteLLM version might resolve the issue.

Guidance

• The error message indicates that the s3 service is not in the list of allowed services, suggesting a potential issue with the service configuration or version compatibility.
• Verify that the s3 service is supported in the current LiteLLM version (main-v1.83.7-stable.patch.1) and check for any updates or patches that may include S3 support.
• Check the health_services_endpoint function in _health_endpoints.py to see if the s3 service can be manually added to the allowed list, although this may require code modifications.
• Consider reaching out to the LiteLLM community or support team for further assistance, as the issue may be specific to the version or configuration being used.

Notes

The provided log output and error message suggest a specific issue with the s3 service not being recognized, but without further information about the LiteLLM version or configuration, it's difficult to provide a more detailed solution.

Recommendation

Apply workaround: The best course of action would be to try updating the LiteLLM version or modifying the service list, if possible, to include the s3 service, as the current version may not support it.