If that error is coming from the console, only AWS can fix that which they will do eventually.
Using the AWS CLI as you have done is perfectly acceptable, and actually a better way. In the real world nobody makes infrastructure changes via the console. It is always terraform, cloudformation or scripts using commands like the above as you then have an audit of what was done (storing scripts, templates etc in git), and a way to more easily change or undo things without having to remember what steps were done in the console.