|
|
|
|
|
by vasco
1043 days ago
|
|
So now tell me, between 7-9 years have gone by since Aurora is a multi database product, what sense does it make to assume its mysql? That's like saying at your company people call AWS "S3" or "SQS" because that's how it started. I don't even know what point you're trying to make because unless the majority of the time was mysql only and then recently other databases would've been added, the anecdote would still not make sense. |
|
The majority of the time, it was identified as "aurora" in CloudFormation templates. 5.6 hit EOL in February of THIS YEAR, aka 2023.
https://aws.amazon.com/blogs/database/upgrade-amazon-aurora-...
So… that would make it the majority of time, wouldn't it? Why does this upset you so?