You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/source/compute_config/aws_ec2.md
+46-4
Original file line number
Diff line number
Diff line change
@@ -109,13 +109,14 @@ In summary, you can use one of the following settings:
109
109
|---|---|---|---|---|
110
110
|aws_ec2 | region | |no | Region name, for example: `eu-west-1`. Lithops will use the `region` set under the `aws` section if it is not set here |
111
111
|aws_ec2 | instance_role | | yes | EC2 Instance role name created in the configuration section above. Do not use the full ARN here; only the role name is required. For example: `ec2LithopsInstanceRole`|
112
-
|aws_ec2 | vpc_id | | no | VPC id. You can find all the available VPCs in the [VPC Console page](https://console.aws.amazon.com/vpc/v2/home#vpcs:) |
113
-
|aws_ec2 | subnet_id | | no | Subnet id. You can find all the available Subnets in the [VPC Console page](https://console.aws.amazon.com/vpc/v2/home#subnets:) |
114
-
|aws_ec2 | security_group_id | | no | Security group ID. You can find the available security groups in the [VPC console page](https://console.aws.amazon.com/vpc/v2/home#SecurityGroups:). The security group must have ports 22 and 8080 open |
112
+
|aws_ec2 | vpc_id | | no | VPC id. You can find all the available VPCs in the [VPC Console page](https://console.aws.amazon.com/vpc/v2/home#vpcs:). If not provided, Lithops will create a new VPC |
113
+
|aws_ec2 | public_subnet_id | | no | Public subnet id. You can find all the available Subnets in the [VPC Console page](https://console.aws.amazon.com/vpc/v2/home#subnets:). If not provided, Lithops will create a new public subnet |
114
+
|aws_ec2 | public_subnet_cidr_block | 10.0.1.0/24 | no | In case a `public_subnet_id` is not provided, Lithops will create a new subnet with this CIDR block |
115
+
|aws_ec2 | security_group_id | | no | Security group ID. You can find the available security groups in the [VPC console page](https://console.aws.amazon.com/vpc/v2/home#SecurityGroups:). The security group must have ports 22, 6379, 8080 and 8081 open. If not provided, Lithops will create a new security group |
115
116
|aws_ec2 | ssh_key_name | | no | SSH Key name. You can find the available keys in the [EC2 console page](https://console.aws.amazon.com/ec2/v2/home#KeyPairs:). Create a new one or upload your own key if it does not exist|
116
117
|aws_ec2 | ssh_username | ubuntu |no | Username to access the VM |
117
118
|aws_ec2 | ssh_password | |no | Password for accessing the worker VMs. If not provided, it is created randomly|
118
-
|aws_ec2 | ssh_key_filename | ~/.ssh/id_rsa | no | Path to the ssh key file provided to access the VPC. It will use the default path if not provided |
119
+
|aws_ec2 | ssh_key_filename | ~/.ssh/id_rsa | no | Path to the ssh key file provided to access the VPC. If not provided, Lithops will use the default path and create a new ssh key for the VPC |
119
120
|aws_ec2 | request_spot_instances | True | no | Request spot instance for worker VMs|
120
121
|aws_ec2 | target_ami | | no | Virtual machine image id. Default is Ubuntu Server 22.04 |
121
122
|aws_ec2 | master_instance_type | t2.micro | no | Profile name for the master VM |
@@ -130,6 +131,47 @@ In summary, you can use one of the following settings:
130
131
|aws_ec2 | exec_mode | reuse | no | One of: **consume**, **create** or **reuse**. If set to **create**, Lithops will automatically create new VMs for each map() call based on the number of elements in iterdata. If set to **reuse** will try to reuse running workers if exist |
131
132
132
133
134
+
## Additional configuration
135
+
136
+
# Elastic Block Store (EBS)
137
+
138
+
To attach EBS volumes to an EC2 instance in Lithops, you can configure the `aws_ec2` section as follows.
139
+
140
+
```yaml
141
+
aws_ec2:
142
+
execution_role: <EXECUTION_ROLE_ARN>
143
+
region: <REGION_NAME>
144
+
...
145
+
ebs_volumes:
146
+
- device_name: /dev/xvda
147
+
ebs:
148
+
volume_size: 100
149
+
volume_type: gp2
150
+
delete_on_termination: true
151
+
encrypted: false
152
+
kms_key_id: <KMS_KEY_ARN>
153
+
- device_name: /dev/xvdf
154
+
ebs:
155
+
volume_size: 50
156
+
volume_type: gp3
157
+
delete_on_termination: true
158
+
encrypted: false
159
+
iops: 3000
160
+
throughput: 125
161
+
...
162
+
```
163
+
164
+
|Group|Key|Default|Mandatory|Additional info|
165
+
|---|---|---|---|---|
166
+
| ebs | volume_size | 8 | No | Size of the volume in GiB |
167
+
| ebs | volume_type | gp2 | No | Type of volume. Options: `gp2`, `gp3`, `io1`, `io2`, `sc1`, `st1`, `standard`|
168
+
| ebs | delete_on_termination| True | No | Whether the volume is deleted automatically when the instance is terminated |
169
+
| ebs | encrypted | False | No | Whether the volume is encrypted |
170
+
| ebs | kms_key_i | | No | ARN of the KMS key used for encryption. If not provided, the default AWS-managed key is used |
171
+
| ebs | iops | | No | Provisioned IOPS for `io1`, `io2`, or `gp3` volumes |
172
+
| ebs | throughput | | No | Throughput in MiB/s for `gp3` volumes |
173
+
174
+
133
175
## Consume mode
134
176
135
177
In this mode, Lithops can start and stop an existing VM, and deploy an entire job to that VM. The partition logic in this scenario is different from the `create/reuse` modes, since the entire job is executed in the same VM.
Copy file name to clipboardexpand all lines: docs/source/lithops_config_keys.csv
+2-2
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
Group;Key;Default;Mandatory;Additional info
2
-
lithops;backend;``ibm_cf``;no;Compute backend implementation. IBM Cloud Functions is the default. If not set, Lithops will check the `mode` and use the `backend` set under the `serverless` or `standalone` sections described below.
3
-
lithops;storage;``ibm_cos``;no;Storage backend implementation. IBM Cloud Object Storage is the default.
2
+
lithops;backend;``aws_lambda``;no;Compute backend implementation. AWS Lambda is the default.
3
+
lithops;storage;``aws_s3``;no;Storage backend implementation. AWS S3 is the default.
4
4
lithops;data_cleaner;``True``;no;If set to True, then the cleaner will automatically delete all the temporary data that was written into `storage_bucket/lithops.jobs`.
5
5
lithops;monitoring;``storage``;no;Monitoring system implementation. One of: **storage** or **rabbitmq**.
6
6
lithops;monitoring_interval;``2``;no;Monitoring check interval in seconds in case of **storage** monitoring.
0 commit comments