Ditto! Sometimes I wonder if the one largest skillsets of becoming an AWS “engineer” is learning to memorise the service names and how they associate to the service offered!
GCP has a few products that AWS doesn't. BigQuery ML and Cloud Spanner are a few that I can think of. These might have approximations on AWS, but not 1-to-1 feature competitors. Plus GCP has one-click integrations with pretty much every Google API out there (analytics, ads, drive, etc).
It's been a minute since I worked with AWS, but they have tons and tons of products. On the order of two, maybe three times as many.
The basic stuff like VMs, storage, networking, and managed postgres/mysql SQL databases are close, but the specialized services can be very different when you look at them closely.
This isn't exactly true. I have worked extensively with Azure, Google Cloud and AWS. While many of their basic services do seem to map 1 to 1 there are enough differences in the details that it's almost like learning a completely new system. At a very high level the basics are relevant, but the differences are much greater than you might expect.
After 2-3 years of working with one then the other, yes and no. They can be quite similar on some accounts, but not quite the same. GCP also has that very Google thing of having very slightly different yet still kind of competing products at the same time.
So does AWS. For just messaging there is SQS, SNS, Amazon MQ, Event Bridge, Kinesis, MSK and probably a couple more tied to product families like IoT and video streaming.