CIDR 10.0.1.0.24 is invalid - ec2 Standalone backend hello world

[RichardScottOZ]

Trying a test using a VPC created by someone else - range is different to this, so is this configurable?

File "C:\Users\rscott\AppData\Local\miniconda3\envs\pygplates_py310\lib\site-packages\botocore\client.py", line 1023, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (InvalidSubnet.Range) when calling the CreateSubnet operation: The CIDR '10.0.1.0/24' is invalid.

[RichardScottOZ]

I notice in the code public and private subnet_id options in the help main page just has subnet_id - maybe should use these?

[RichardScottOZ]

and theorising that might have to make some changes if wanting to use with private subnets etc?

[RichardScottOZ]

apparently have got it to launch a hello world machine anyway - after some private subnet adjustments/additions

also - had to have encrypted drive for work reasons, so tells me the device name for the example machine is sda1 for reference

[JosepSampe]

Hi @RichardScottOZ , In PR https://github.com/lithops-cloud/lithops/pull/1418, I added the ability to specify a custom CIDR block for the public subnet and fixed the documentation to match the configurable public_subnet_id, which was incorrectly specified as subnet_id in the docs.

I also added support for specifying EBS volumes in the config file, which ensures that all EC2 Lithops workers can have encrypted volumes attached.

[RichardScottOZ]

Thanks! Will try again soon.