This error is seen just using 'test' on a target endpoint right?
Did it ever work, or is this a brand new endpoint?
Do you have similar target endpoints which work? What is the difference?
If it is the very first time go ahead and request support as suggested , but support is not a great training tool. You may benefit more from some Professional Service to help build up your Replicate working knowledge. Was there a Proof Of Concept and can you use that as starting point.
Did you try to map the error message details onto you work environment? There is a good change the message actually has a meaning and that there is an unexpected character at that position 281. That could be an extra comma or closing curly bracket. Admittedly it can be hard to know where to look and where to start counting.
You should try to get the JSON behind the target definition you have. Now Replicate oddly enough still does not have a simple UI to export an endpoint. Your choice is to create a dummy task with that endpoint and export that task with its endpoints or use REPCTL EXPORTREPOSITORY to get it all, navigate to the problematic Redshift target in an JSON aware editor (Notepad++ recommended) and look for db_settings and S3Region in that JSON blob. Mind you I'm not sure you'll find it as I do not have a Redshift target handy myself.
Doing this, at best you'll spot the problem yourself and will not have to be embarrassed by the support answer, and at least you'll build up the context/vocabulary to work with Support more efficiently.
Note: If any reader has an operational Redshift target, can you do me a favor and post a sample JSON description after obfuscating sensitive information?
Good luck,
Hein
