Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update aws-batch.mdx #86

Open
wants to merge 4 commits into
base: master
Choose a base branch
from
Open

Update aws-batch.mdx #86

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ece016a
Update aws-batch.mdx
allyssonallan Jun 21, 2024
68945a2
Merge branch 'master' into patch-1
allyssonallan Jun 25, 2024
a9a1560
Rename aws-batch.mdx to aws-batch.mdx
justinegeffen Aug 7, 2024
091d487
Merge branch 'master' into patch-1
justinegeffen Aug 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
25 changes: 11 additions & 14 deletions platform_versioned_docs/version-23.4/compute-envs/aws-batch.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,19 +43,16 @@ We recommend that you create separate IAM policies for Batch Forge and launch pe
**Create an IAM user**

1. From the [AWS IAM console](https://console.aws.amazon.com/iam), select **Users** in the left navigation menu, then select **Add User** at the top right of the page.
2. Enter a name for your user (e.g., _seqera_) and select the **Programmatic access** type.
3. Select **Next: Permissions**.
4. Select **Next: Tags > Next: Review > Create User**.

:::note
For the time being, you can ignore the "user has no permissions" warning. Permissions will be applied using the **IAM Policy**.
:::

5. Save the **Access key ID** and **Secret access key** in a secure location as you will use these when creating credentials in Seqera.
6. After you have saved the keys, select **Close**.
7. Back in the users table, select the newly created user, then select **Add permissions** under the **Permissions** tab.
8. Select **Attach existing policies**, then search for and select each of the policies created above.
9. Select **Next: Review > Add permissions**.
2. Enter a name for your user (e.g., _seqera_).
3. Select **Next: Permissions > Add policies directly**.
4. Search and tick out: `launch-policy`, `forge-policy`, `s3-bucket-write`.
5. Select **Next: Tags > Next: Review > Create User**.
6. Click in your user (e.g., _seqera_).
7. Go to `Secure credentials` tab and choose `Create access keys`.
7. In `Access key best practices & alternatives` page choose `Application running outside AWS` use case.
8. Select **Next: Tags**.
9. In `Retrieve access keys` save in a secure location your **Access key ID** and **Secret access key** as you will use these when creating credentials in Seqera.
6. After you have saved the keys, select **Done**.

### S3 Bucket

Expand Down Expand Up @@ -190,7 +187,7 @@ Seqera Platform compute environments for AWS Batch include advanced options to c

**Batch Forge AWS Batch advanced options**

Specify the **Allocation strategy** and indicate any preferred **Instance types**. AWS applies quotas for the number of running and requested [Spot](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-limits.html) and [On-demand](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-on-demand-instances.html#ec2-on-demand-instances-limits) instances per account. AWS will allocate instances from up to 20 instance types, based on those requested for the compute environment. AWS excludes the largest instances when you request more than 20 instance types.
Specify the **Allocation strategy** and indicate any preferred **Instance types**. AWS applies quotas for the number of running and requested [Spot](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-spot-limits.html) and [On-demand](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-on-demand-instances.html#ec2-on-demand-instances-limits) instances per account. AWS will [allocate](https://aws.amazon.com/ec2/faqs/#how-many-instances-ec2) instances from up to 20 instance types, based on those requested for the compute environment. AWS excludes the largest instances when you request more than 20 instance types.

:::note
If these advanced options are omitted, Seqera Platform 23.2 and later versions' allocation strategy defaults are `BEST_FIT_PROGRESSIVE` for on-demand and `SPOT_CAPACITY_OPTIMIZED` for spot compute environments.
Expand Down
Loading