I have all of my software configured on my instance1.
I have a local repo, as well as a cloud repo.
I have put in the correct keys in both repos and enabled the EC2, but absolutely nothing happens.
I am using RC7.
If I enter an intentionally incorrect key, there is still no feedback that anything is wrong.
Am I missing something? Can someone help me get some feedback and hopefully some success?
Thanks,
Alexander.
If you bring up the Console panel in the Monitor, any EC2 connection errors should be showing up in there. If you could post that here, that’d be great!
I would definitely check to make sure any extra characters didn’t sneak in at the end/start of the key during a copy/paste (spaces are especially sneaky). Also make sure that you’re putting the credentials into the correct EC2 region. I’ve personally been caught by both of those things before
I should also note that we’re working on an improved version of the config screen that will have a verify button that gives better feedback to ensure you’ve configured things correctly.
I’m looking into some of the python files where errors are thrown.
EC2.py for example has a lot of hard coded data that appears not to match the data which amazon has provided for our instances.
We have managed to find the problem, this was NOT Deadline related.
After installing the SDK for the Amazon API I was getting the same error.
My boss who manages the account works on mac and when he thought he was using my key to perform the actions, he was not in fact doing so.
As such there were some significant permissions missing and once those were resolved, suddenly Deadline was populated with servers.
Now that that is taken care of, we suddenly need to manage the permissions to a more precise level.