We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Initializing the lambda function with defined subnets and security groups should be possible by adding support for an optional VpcConfig object in
VpcConfig
scar/scar/providers/aws/lambdafunction.py
Line 52 in 99a8cb2
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.
The text was updated successfully, but these errors were encountered:
Implements #364
3c18f74
No branches or pull requests
Initializing the lambda function with defined subnets and security groups should be possible by adding support for an optional
VpcConfig
object 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.
The text was updated successfully, but these errors were encountered: