Database restore feature is BROKEN - currently awaiting support

Question

Warning to users, point in time recovery might be broken!  
  
I've just had a MySQL instance run out of space with connection not available. I'm trying to restore using point in time onto a larger instance but I'm getting the following error:  
_____  
CreateRelationalDatabaseFromSnapshot \[eu-west-2]  
The sourceRelationalDatabaseName must be specified together with restoreTime or useLatestRestorableTime.  
InvalidParams  
I have checked DevTools and the sourceRelationalDatabaseName is correct and is being sent in the request payload.  
_____  
  
I'm awaiting technical support - as an aside, if you upgrade it might take up to 24 hours for it to take effect, which needless to say, is the one time you don't want to wait!  
  
If anyone can look into case 6174685581 it would be much appreciated. Of all the features to fail, restore shouldn't be one of them!  
  
Hopefully

Answer

Thanks for reporting the issue. We are looking into the issue and will work toward a fix as soon as possible.  
  
Thanks,  
Steve

Answer

Just wanted to say thanks to AWS Support, once we were on the Business plan and I could demonstrate over a web chat that it was definitely nothing on my end that was wrong they very quickly amended my Lightsail RDS instance so that it could accept connections again.

Answer

As a follow-up, this has been escalated - regardless of using the web or cli I am getting this error.  
  
An error occurred (InvalidInputException) when calling the CreateRelationalDatabaseFromSnapshot operation: The sourceRelationalDatabaseName must be specified together with restoreTime or useLatestRestorableTime.  
  
(All parameters double-checked)  
  
At this moment it appears that point in time recovery is broken entirely unless the API is throwing the wrong error when the disk is full??? Seems very unlikely...

Answer

The fix for the issue you mentioned was released. It's great to hear that your issue is resolved. Thanks for reporting the issue to us.

Database restore feature is BROKEN - currently awaiting support

Relevant content