Testing AWS Batch and Fargate Executors #710
Unanswered
Emmanuel289
asked this question in
Q&A
Replies: 1 comment
-
Tracking in the following GH issues: |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I setup the aws-batch and fargate plugins using pip install to test the batch and fargate executors.
Testing the Fargate Executor
In the case of the fargate executor, I followed these steps:
AWS Configuration setup
Configured aws credentials by copying the secret_access_key, access_key_id, and session_token generated for my profile into the
~/.aws/credentials
file. I also set the AWS environment variables to make sure that the right variables were pulled in the event that some variables were not properly set in the~/.aws/credentials
file.Verifying CLI Access to Resources
I ran some commands to verify cli access to AWS resources, especially those required by the fargate plugin, e.g,
aws ecs describe-clusters —cluster covalent-fargate-cluster
to inspect the fargate-clusterAdded entries for the fargate plugin to the covalent configuration file
I updated the
covalent.conf
file with entries for the fargate pluginExecuting an electron on the fargate executor
I tried to execute an electron in the workflow below, but the task execution failed with exit code - 1. The exception was raised by
poll_ecs_task()
infargate.py
.Testing the Batch Executor
In the case of the batch executor, I got a similar exception raised by
poll_batch_jobs()
inawsbatch.py
Beta Was this translation helpful? Give feedback.
All reactions