1 Answer
- Newest
- Most votes
- Most comments
0
It is unfortunate Bert that you have encountered this issue after a routine upgrade and Support should be able to assist you with resolution.
I just wanted to bring the a general recommendation of running the Production cluster on trailing track and have non-prod like UAT, QA, Dev on the latest i.e. current track. This way you catch such issues before they impact Production workloads.
Best of luck!
answered 3 months ago
Relevant content
- asked 2 years ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 9 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago