Add files via upload

docs/AWS-Batch-Setup.md

@@ -0,0 +1,51 @@
+# AWS Batch Setup
+
+## **0-Before You Begin**
+
+- Ensure you have a VPC, subnets, and security group set up before continuing the AWS Batch setup.
+- Attach following policies to your SageMaker notebook instance:
+
+![](../images/batch-policis.PNG)
+## **1-Creating a Compute Environment**
+
+Naviate to **'AWS Batch'** in the console. Within AWS Batch on the left side menu navigate to **'Compute environments'**, select **'Create'**.  
+For this tutorial we will be working with "Fargate".
+
+- Enter a name for your compute environment
+- Under service role select "AWSServiceRoleForBatch"
+- Click 'Next'
+
+![](../images/batch-compute1.PNG)
+
+We have set vCPUs to its maximum in the image below. Click Next.
+
+![](../images/batch-compute2.PNG)
+
+For Network Configuration select your VPC, subnets, and security groups you would like to utilize. This will allow AWS Batch to create instances that can communicate with each other and have access to acceptable networks.
+
+![](../images/batch-compute3.PNG)
+
+The last step is to review all the configuration made to your compute environment. Once you are satisfied click "Create compute environment".
+
+![](../images/batch-compute4.PNG)
+## **3-Creating a Job Queue**
+
+Now that we have created a compute environment lets create a job queue. Job queues help Batch to stay organized by holding jobs until they can be scheduled to run in a compute environment.
+
+In the AWS Batch console, go to the left side menu, click "Job queues" and click "Create".
+
+- Set orchestration type to "Fargate"
+- Give your queue a name and set its priority. for this tutorial we have se it to '1000' to have the highest priority
+- Associate the compute environment you created in the pervious step.
+- Review and create the job queue.
+
+![](../images/batch-queue1.PNG)
+## **4-Applying Permissions**
+
+For this step we are enabling AWS Batch permissions on EC2 clusters.
+
+- On the left side menu under 'Control settings' click 'Permissions'.
+- Next to Container insights click 'Edit'.
+- Using the toggles select with compute environment should have these permissions and click 'Save changes'.
+
+![](../images/batch-permission1.PNG)