2 Answers
- Newest
- Most votes
- Most comments
0
This is either user error or a bug. Assuming you have double checked everything, ask a colleague to triple check it - fresh set of eyes can see things that were originally overlooked. If thats all done then kindly raise a Support Ticket for deeper investigation.
answered a month ago
0
Hi,
As mentioned by MilindOke@, This seems has to be a user error or bug. If you are still facing the issue, Please raise a support case with us - https://docs.aws.amazon.com/awssupport/latest/user/case-management.html and share the cluster arn and view details.
Thank you.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 8 months ago