# create

Create the initial lambda function and related security role.

## Usage

```bash
claudia create {OPTIONS}
```

## Options

*  `--region`:  AWS region where to create the lambda. For supported values, see
    https://docs.aws.amazon.com/general/latest/gr/rande.html#lambda_region
    * _For example_: us-east-1
*  `--handler`:  (_optional_) Main function for Lambda to execute, as module.function
    * _For example_: if it is in the main.js file and exported as router, this would be main.router
*  `--api-module`:  (_optional_) The main module to use when creating Web APIs. 
    If you provide this parameter, do not set the handler option.
    This should be a module created using the Claudia API Builder.
    * _For example_: if the api is defined in web.js, this would be web
*  `--arch`:  (_optional_) Specifies the desired architecture, either x86_64 or arm64. 
    If a value is not provided, x86_64 will be used as the default.
    * _Defaults to_: x86_64
    * _Introduced in version_: 5.13.2
*  `--deploy-proxy-api`:  (_optional_) If specified, a proxy API will be created for the Lambda 
    function on API Gateway, and forward all requests to function.
    This is an alternative way to create web APIs to --api-module.
*  `--binary-media-types`:  (_optional_) A comma-delimited list of binary-media-types to 
    set when using --deploy-proxy-api. Use an empty string in quotes
    to not set any binary media types.
    * _For example_: image/png,image/jpeg
    * _Defaults to_: */*
*  `--name`:  (_optional_) lambda function name
    * _For example_: awesome-microservice
    * _Defaults to_: the project name from package.json
*  `--version`:  (_optional_) A version alias to automatically assign to the new function
    * _For example_: development
*  `--source`:  (_optional_) Directory with project files
    * _Defaults to_: current directory
*  `--config`:  (_optional_) Config file where the creation result will be saved
    * _Defaults to_: claudia.json
*  `--policies`:  (_optional_) A directory or file pattern for additional IAM policies
    which will automatically be included into the security role for the function
    * _For example_: policies/*.json
*  `--allow-recursion`:  (_optional_) Set up IAM permissions so a function can call itself recursively
*  `--role`:  (_optional_) The name or ARN of an existing role to assign to the function. 
    If not supplied, Claudia will create a new role. Supply an ARN to create a function without any IAM access.
    * _For example_: arn:aws:iam::123456789012:role/FileConverter
*  `--runtime`:  (_optional_) Node.js runtime to use. For supported values, see
    http://docs.aws.amazon.com/lambda/latest/dg/API_CreateFunction.html
    * _Defaults to_: nodejs14.x
*  `--description`:  (_optional_) Textual description of the lambda function
    * _Defaults to_: the project description from package.json
*  `--memory`:  (_optional_) The amount of memory, in MB, your Lambda function is given.
    The value must be a multiple of 64 MB.
    * _Defaults to_: 128
*  `--timeout`:  (_optional_) The function execution time, in seconds, at which AWS Lambda should terminate the function
    * _Defaults to_: 3
*  `--no-optional-dependencies`:  (_optional_) Do not upload optional dependencies to Lambda.
*  `--use-local-dependencies`:  (_optional_) Do not install dependencies, use local node_modules directory instead
*  `--npm-options`:  (_optional_) Any additional options to pass on to NPM when installing packages. Check https://docs.npmjs.com/cli/install for more information
    * _For example_: --ignore-scripts
    * _Introduced in version_: 5.0.0
*  `--cache-api-config`:  (_optional_) Name of the stage variable for storing the current API configuration signature.
    If set, it will also be used to check if the previously deployed configuration can be re-used and speed up deployment
    * _For example_: claudiaConfigCache
*  `--post-package-script`:  (_optional_) the name of a NPM script to execute custom processing after claudia finished packaging your files.
    Note that development dependencies are not available at this point, but you can use npm uninstall to remove utility tools as part of this step.
    * _For example_: customNpmScript
    * _Introduced in version_: 5.0.0
*  `--keep`:  (_optional_) keep the produced package archive on disk for troubleshooting purposes.
    If not set, the temporary files will be removed after the Lambda function is successfully created
*  `--use-s3-bucket`:  (_optional_) The name of a S3 bucket that Claudia will use to upload the function code before installing in Lambda.
    You can use this to upload large functions over slower connections more reliably, and to leave a binary artifact
    after uploads for auditing purposes. If not set, the archive will be uploaded directly to Lambda.
    
    * _For example_: claudia-uploads
*  `--s3-key`:  (_optional_) The key to which the function code will be uploaded in the s3 bucket referenced in `--use-s3-bucket`
    * _For example_: path/to/file.zip
*  `--s3-sse`:  (_optional_) The type of Server Side Encryption applied to the S3 bucket referenced in `--use-s3-bucket`
    * _For example_: AES256
*  `--aws-delay`:  (_optional_) number of milliseconds betweeen retrying AWS operations if they fail
    * _For example_: 3000
    * _Defaults to_: 5000
*  `--aws-retries`:  (_optional_) number of times to retry AWS operations if they fail
    * _For example_: 15
    * _Defaults to_: 15
*  `--security-group-ids`:  (_optional_) A comma-delimited list of AWS VPC Security Group IDs, which the function will be able to access.
    Note: these security groups need to be part of the same VPC as the subnets provided with --subnet-ids.
    * _For example_: sg-1234abcd
*  `--subnet-ids`:  (_optional_) A comma-delimited list of AWS VPC Subnet IDs, which this function should be able to access.
    At least one subnet is required if you are using VPC access.
    Note: these subnets need to be part of the same VPC as the security groups provided with --security-group-ids.
    * _For example_: subnet-1234abcd,subnet-abcd4567
*  `--set-env`:  (_optional_) comma-separated list of VAR=VALUE environment variables to set
    * _For example_: S3BUCKET=testbucket,SNSQUEUE=testqueue
*  `--set-env-from-json`:  (_optional_) file path to a JSON file containing environment variables to set
    * _For example_: production-env.json
*  `--env-kms-key-arn`:  (_optional_) KMS Key ARN to encrypt/decrypt environment variables
*  `--layers`:  (_optional_) A comma-delimited list of Lambda layers to attach to this function
    * _For example_: arn:aws:lambda:us-east-1:12345678:layer:ffmpeg:4
*  `--dlq-sns`:  (_optional_) Dead letter queue SNS topic name or ARN
    * _For example_: arn:aws:sns:us-east-1:123456789012:my_corporate_topic