[doc] Updated AWS services dependencies

Signed-off-by: Maurizio Melato <[email protected]>

docs/source/aws_services.rst

@@ -25,21 +25,28 @@ For more details about AWS CloudFormation, see http://aws.amazon.com/cloudformat
 AWS Identity and Access Management (IAM)
 ----------------------------------------
 
-IAM is used within AWS ParallelCluster to provide an Amazon EC2 IAM Role for the instances. This role is a least privileged role specifically created for each cluster. AWS ParallelCluster instances are given access only to the specific API calls that are required to deploy and manage the cluster.
+AWS IAM is used within AWS ParallelCluster to provide an Amazon EC2 IAM Role for the instances. This role is a least privileged role specifically created for each cluster. AWS ParallelCluster instances are given access only to the specific API calls that are required to deploy and manage the cluster.  
+
+With AWS Batch clusters, IAM Roles are also created for the components involved with the Docker image building process at cluster creation time. 
+These components include the Lambda functions allowed to add and delete Docker images to/from the ECR repository and to delete the S3 bucket created for the cluster and CodeBuild project. Then there are roles for the AWS Batch resources, instance, job.
 
 For more details about AWS Identity and Access Management, see http://aws.amazon.com/iam/
 
-Amazon SNS
-----------
+Amazon Simple Notification Service (SNS)
+----------------------------------------
+
+Amazon SNS is used to receive notifications from Auto Scaling. These events are called life cycle events, and are generated when an instance launches or terminates in an Autoscaling Group. Within AWS ParallelCluster, the Amazon SNS topic for the Autoscaling Group is subscribed to an Amazon SQS queue.  
 
-Amazon Simple Notification Service is used to receive notifications from Auto Scaling. These events are called life cycle events, and are generated when an instance launches or terminates in an Autoscaling Group. Within AWS ParallelCluster, the Amazon SNS topic for the Autoscaling Group is subscribed to an Amazon SQS queue.
+The service is not used with AWS Batch clusters.
 
 For more details about Amazon SNS, see http://aws.amazon.com/sns/
 
-Amazon SQS
-----------
+Amazon Simple Queuing Service (SQS)
+-----------------------------------
+
+Amazon SQS is used to hold notifications(messages) from Auto Scaling, sent through Amazon SNS and notifications from the ComputeFleet instances. This decouples the sending of notifications from the receiving and allows the Master to handle them through polling. The MasterServer runs Amazon SQSwatcher and polls the queue. AutoScaling and the ComputeFleet instances post messages to the queue.  
 
-Amazon Simple Queuing Service is used to hold notifications(messages) from Auto Scaling, sent through Amazon SNS and notifications from the ComputeFleet instances. This decouples the sending of notifications from the receiving and allows the Master to handle them through polling. The MasterServer runs Amazon SQSwatcher and polls the queue. AutoScaling and the ComputeFleet instances post messages to the queue.
+The service is not used with AWS Batch clusters.
 
 For more details about Amazon SQS, see http://aws.amazon.com/sqs/
 
@@ -50,30 +57,77 @@ Amazon EC2 provides the compute for AWS ParallelCluster. The MasterServer and Co
 
 For more details about Amazon EC2, see http://aws.amazon.com/ec2/
 
-Auto Scaling
-------------
+AWS Auto Scaling
+----------------
+
+AWS Auto Scaling is used to manage the ComputeFleet instances. These instances are managed as an AutoScaling Group and can either be elastically driven by workload or static and driven by the config.  
 
-Auto Scaling is used to manage the ComputeFleet instances. These instances are managed as an AutoScaling Group and can either be elastically driven by workload or static and driven by the config.
+The service is not used with AWS Batch clusters.
 
 For more details about Auto Scaling, see http://aws.amazon.com/autoscaling/
 
-Amazon EBS
-----------
+Amazon Elastic Block Store (EBS)
+--------------------------------
 
-Amazon EBS provides the persistent storage for the shared volume. Any EBS settings can be passed through the config. EBS volumes can either be initialized empty or from an existing EBS snapshot.
+Amazon EBS provides the persistent storage for the shared volumes. Any EBS settings can be passed through the config. EBS volumes can either be initialized empty or from an existing EBS snapshot.
 
 For more details about Amazon EBS, see http://aws.amazon.com/ebs/
 
 Amazon S3
 ---------
 
-Amazon S3 is used to store the AWS ParallelCluster templates. Each region has a bucket with all templates. AWS ParallelCluster can be configured to allow allow CLI/SDK tools to use S3.
+Amazon S3 is used to store the AWS ParallelCluster templates. Each region has a bucket with all templates. AWS ParallelCluster can be configured to allow allow CLI/SDK tools to use S3.  
+
+With an AWS Batch cluster, an S3 bucket in the customer's account is created to store artifacts used by the Docker image creation and the jobs scripts when submitting jobs from the user's machine.
 
 For more details, see http://aws.amazon.com/s3/
 
 Amazon DynamoDB
 ---------------
 
-Amazon DynamoDB is used to store minimal state of the cluster. The MasterServer tracks provisioned instances in a DynamoDB table.
+Amazon DynamoDB is used to store minimal state of the cluster. The MasterServer tracks provisioned instances in a DynamoDB table.  
+
+The service is not used with AWS Batch clusters.
 
 For more details, see http://aws.amazon.com/dynamodb/
+
+AWS Batch
+---------
+AWS Batch is the AWS managed job scheduler that dynamically provisions the optimal quantity and type of compute resources (e.g., CPU or memory optimized instances) based on the volume and specific resource requirements of the batch jobs submitted. With AWS Batch, there is no need to install and manage batch computing software or server clusters that you use to run your jobs.
+
+The service is only used with AWS Batch clusters.
+
+For more details, see https://aws.amazon.com/batch/
+
+AWS CodeBuild
+-------------
+AWS CodeBuild is used to automatically and transparently build Docker images at cluster creation time.
+
+The service is only used with AWS Batch clusters.
+
+For more details, see https://aws.amazon.com/codebuild/
+
+AWS Lambda
+----------
+AWS Lambda service runs the functions that orchestrate the Docker image creation and manage custom cluster resources cleanup, that are the created Docker images stored in the ECR repository and the S3 bucket for the cluster.
+
+The service is only used with AWS Batch clusters.
+
+For more details, see https://aws.amazon.com/lambda/
+
+Amazon Elastic Container Registry (ECR)
+---------------------------------------
+
+Amazon ECR stores the Docker images built at cluster creation time. The Docker images are then used by AWS Batch to run the containers for the submitted jobs.
+
+The service is only used with AWS Batch clusters.
+
+For more details, see https://aws.amazon.com/ecr/
+
+Amazon CloudWatch
+-----------------
+Amazon CloudWatch is used to log Docker image build steps and the standard output and error of the AWS Batch jobs.
+
+The service is only used with AWS Batch clusters.
+
+For more details, see https://aws.amazon.com/cloudwatch/