
Renaming rules can change the downloaded Payee name to one of your choosing. The top box allows you to create what you want it to search for. You can search "Statement Name", which is exactly what comes from the financial institution, or you can search "Quicken Name", which is the name Quicken's back-end server thinks might be a more usable name. The key thing to understand is that this process breaks the search term into what Quicken confusingly calls "tags" (more properly called "tokens") here: individual words rather than a complete phrase. So if you enter "Home Depot", Quicken breaks it into "Home" "Depot". There is no way to search for a phrase, and you can't use wildcard characters. And that's where I think your problem lies, based on what you posted above.
If your credit card company is transmitting the Payee name as "Amazon1234", "Amazon2345" and "Amazon3456", Quicken sees those as a single tag. Quicken looks for a delimiter to separate words: a space, hyphen, comma, period, colon, semicolon, question mark, exclamation point, asterisk, dollar sign, hashtag, @ sign, parenthesis, plus sign, equals sign, apostrophe, quote, bracket, slash, backslash, pipe, percent sign, caret, ands doubtless some others. But letters and numbers together do not allow it to discern any place to separate the characters. So if the credit card company sent "Amazon*1234" or "Amazon-1234" or "Amazon 1234" or "Amazon.1234", etc., the renaming rule could search for Amazon and set the Payee name to be just "Amazon". But if they sent "Amazon1234", Quicken sees that as a single word or tag, which is not the same as "Amazon2345".
I suggest you click on one of the Amazon transactions and select View > Show Inspector. In this window, look at Statement Payee (what the credit card company is sending) and Quicken Name (what Quicken's server may be substituting, using its own version of renaming rules). If neither of them separate "Amazon" with a delimiter, then you can't create a renaming rule to do what you want.
Again, this is nothing new; I remember discussing it in this forum with the Quicken product manager back when renaming rules were first introduced. He said they looked at using numbers as separators, but there was some reason they couldn't because they have to be compatible with the way Quicken Windows works since both products share use of the Quicken mobile app and need to work the same way in this area.
I'd also note that other Amazon customers have not been reporting this, so again I think it's specific to your credit card company and they way they are formatting transactions from Amazon. You may want to try contacting their customer support to complain about this; things can and do get changed, but it may not be easy to get to talk to someone knowledgeable about their export to Quicken who can dig into this.
Meanwhile, if you reach a dead end with renaming rules, I would just note that Search in Quicken Mac does not use the same tag/token approach to searching. So if you have a bunch of Amazon transactions which come in under different Payee names like "Amazon1234", "Amazon2345" and "Amazon3456", you can type "Amazon" in the Search box and it will find all of them (along with anything names just "Amazon"). You can then select all the ones with numbers (Command-click on each one), go to Transactions > Edit Transaction, and change the Payee name to "Amazon" on all of them at once. It's not perfect because you have to do it after-the-fact, but at least this saves you editing each transaction individually.