Initializing the lambda function with defined subnets and security groups should be possible by adding support for an optional VpcConfig object in
|
def _get_creations_args(self, zip_payload_path: str, supervisor_zip_path: str) -> Dict: |
Example: The following configuration:
functions:
aws:
- lambda:
name: scar-cowsay
run_script: runcow.sh
container:
image: grycap/cowsay
vpc_config:
SubnetIds:
- <SUBNETA-ID>
- <SUBNETB-ID>
SecurityGroupIds:
- <GROUPA-ID>
- <GROUPB-ID>
should configure the resulting lambda function to use Subnet IDs A and B, and Security Groups A and B.
This would be necessary once #360 is implemented, in order to allow access to Elastic File Shares contained within a VPC.
Initializing the lambda function with defined subnets and security groups should be possible by adding support for an optional
VpcConfigobject inscar/scar/providers/aws/lambdafunction.py
Line 52 in 99a8cb2
Example: The following configuration:
should configure the resulting lambda function to use Subnet IDs A and B, and Security Groups A and B.
This would be necessary once #360 is implemented, in order to allow access to Elastic File Shares contained within a VPC.