glad I managed to help back in some way

The scenario I'm going for is never to run on the dev machine, so all I'll need to do once the server + agents are up is to add task.execute_remotely... after the Task.init line and after the execution of the script is called on the dev machine, it won't actually run but rather enqueue itself for the agent to run it?

I was sure you are on Israel times as well, sorry for the night time thing 😄

I guess so

💪

The latest, I curl ed the docker-compose like 10 minutes ago

cool the /login worked

Okay, I'll try that

can you tell me which API call exactly are you using for spinning up? I would like to debug and try to use boto3 myself in order to spin up an instance, so I can understand where the problem is coming from

no need to do it again, I ahve all the settings in place, I'm sure it's not a settings thing

So just to correct myself and sum up, the credentials for AWS are only in the cloud_credentials_*

I doubled checked the credentials in the configurations, and they have full EC2 access

So what's our next move FriendlySquid61 ? O_O

the trains ones

Now I remind you that using the same credentials exactly, the auto scaler task could launch instances before

and when looking at the running task, I still see the credentials

the ones in the export are like you said

Actually I removed the key pair, as you said it wasn't a must in the newer versions

I'll try to debug this and updat

I'll try to put it again

now I get this error in my Auto Scaler task
Warning! exception occurred: An error occurred (AuthFailure) when calling the RunInstances operation: AWS was not able to validate the provided access credentials Retry in 15 seconds

I have them in two different places, once under Hyperparameters -> General

I ran the wizard liek a milion times

and I'm using the same credentials

I have them only in one place

oops m ybad

Okay martin, I'll try that

I think I got it, I'll ping her again if it won't succeed