When i paste the URL and the activation code and press OK, it asks me for a user/pass.
I have tried this with the Resource Tracker online, and because it costs money i deleted it and tried again, but no luck. Tried all the users/passwords Ive created on this adventure and none of them helped.
Thanks very much !! i was stuck on Authentication Failed error and thanks to Manage ID documentation at the bottom of the page you sent, i managed to understand i needed to manually register the AWS instance for a Client role.
So i did and i managed to get a frame into the machine!! The Redshift log said there was no compatible GPU on the C5 instance type i had chosen.
So i tried G instance types instead and i can not get a spot fleet of 1 machine to fullfill.
This is slow and frustrating. I requested 20 quotas and got 8 instead.
g5.xlarge = Redshift error: GPU not compatible
g4dn.8xlarge = requires 16 quotas min (nothing smaller available on the region)
p2.xlarge = request instance type not supported in the requested availability zone
p3 = not available
As for not getting the requested instances, it could either be that there are indeed no instances of that type available at the time of request (even though the region has them) or as in the case youâve screenshot youâre bumping into the upper limit your account is permitted to request.
As you suspect youâll have to request an increase for the âSpot Instance Requestâ limit for the particular instance families youâre looking to use. Request for Spot Instance increase here.
I donât have a record of which instances have Redshift supported GPUs, though that might be fix-able with the right drivers.
Itâs not possible to filter out which instances are compatible with your workflow, but I did write this guide on minimizing spot interruption which shows how to use AWS tools to pick the best possible set of instances for a given region at a given time.
Thanks very much for the light and attention given to my particular case. Sincerely. I admit a feeling of increasing guilt since i veered off vigorously and unintentionally from the threadâs subject title - lmao
I can confirm i tried again at a later time and found the instances (ha!), then submitted my test scene and it âworkedâ** ! ( after having been granted the quota increase from 0 to 8 )
** By worked, i mean i got a REDSHIFT error. Not complaining about the incompatible GPU, but the proxy version (rs file). Which means the redshift installed on the Linux standalone redshift IAM its not the same version im running currently. According to the docs, the standalone linux IAM uses redshift 2.6.39 whilst im running 3.5.xx
So im now diving into custom IAM prepping. what a time to be alive ! â˘