Your concern is very valid. These two appear fairly similar. However their usage may vary depending on what do you need. Some of the differences:
SQS supports single consumer, while if you have multiple consumer for same stream then Kinesis is the solution for you.
If read throughput above a certain threshold is required with less application layer + sharding logic that Kinesis requires, then SQS is the solution.
If you require message replayability then Kinesis is the solution as SQS deletes the message as soon as consumer read it, while Kinesis maintain it for a day.
Refer this : https://sookocheff.com/post/aws/comparing-kinesis-and-sqs/