Moritz Zimmer

allow ssm:GetParameter with ssm config

1

Currently this module configures the following policy for `ssm_parameter_names`: ```hcl data "aws_iam_policy_document" "ssm_policy_document" { count = length(var.ssm_parameter_names) statement { actions = [ "ssm:GetParameters", "ssm:GetParametersByPath", ] resources = [ "arn:aws:ssm:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:parameter/${element(var.ssm_parameter_names, count.index)}",...

enhance and clarify secrets management

1

There are different possibilities and recommendations how to manage and access secrets (e.g. database passwords) inside Lambda functions (see e.g [here](https://epsagon.com/blog/aws-lambda-and-secret-management/) and [here](https://medium.com/better-programming/how-to-store-your-aws-lambda-secrets-cheaply-without-compromising-scalability-or-security-d3e8a250f12c)). Currently this module supports reading (optionally encrypted)...

Further development of this module will be continued in [moritzzimmer/terraform-aws-lambda](https://github.com/moritzzimmer/terraform-aws-lambda). Users of `spring-media/lambda/aws` should migrate to this module as a drop-in replacement for all provisions up to release/tag `5.2.1` to...

## what AWS Lambda service [supports](https://docs.aws.amazon.com/lambda/latest/dg/invocation-eventfiltering.html#filtering-syntax) up to five different filters for a single event source. This module allowed only one so far which will be fixed with this PR....

Can't update used `awscc_location_api_key`

6

### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request * Please do...

Enhance examples

1

We should provide examples depicting major features of this module. Those examples need to be `terraform apply`'able by users without errors. Possible examples: - [x] complete example with all basic...

We might remove internal dependencies to 3rd party terraform modules like [terraform-aws-modules/s3-bucket/aws](https://registry.terraform.io/modules/terraform-aws-modules/s3-bucket/aws/latest) which cuts interdependencies in terms of required/supported aws provider and terraform versions.

Add a [CONTRIBUTING.md](https://github.com/moritzzimmer/terraform-aws-lambda/blob/main/CONTRIBUTING.md) describing how to contribute to this project.

Currently the deployment is part of the main [stack](https://github.com/stroeer/terraform-aws-ecs-fargate/blob/715528a2e41b043effb517dc57e70844781c9c57/main.tf#L209), which can be deactivated using a [variable](https://github.com/stroeer/terraform-aws-ecs-fargate/blob/715528a2e41b043effb517dc57e70844781c9c57/variables.tf#L176). We might also separate those 2 stacks like in [terraform-aws-lambda/tree/master/modules/deploy](https://github.com/terraform-aws-modules/terraform-aws-lambda/tree/master/modules/deploy).

support apps w/o exposed ports

1

Providing a `container_port` used for the load balancer and/or mesh proxy configuration is mandatory at the moment. We might want to support apps w/o an exposed port as well, e.g....