Can executable business logic be designed in a Service instead of an Entity in DDD?

According to Eric Evans’ book "Domain-Driven Design", it seems to me that the key concepts of DDD are Ubiquitous Language, Bounded Context, and the defined Isolation between these bounded contexts.
Additionally, the key design elements provided are: Entity, ValueObject, and Service.

My question is:
In your opinion, is it acceptable to design business logic inside a Service instead of an Entity?
As a result, the Entity becomes anemic, BUT it continues to be part of the product aspect (as well as part of the context and the ubiquitous language) and still maintains its identity.

So, in this case, it seems that the main concept of DDD is preserved, despite the described "compromise".