#terraform-aws-modules - May 2022

Hi team, just checking if we have roadmap to create modules for AWS Appstream 2.0

Interesting situation and looking for possible solutions. Trying to utilize the dynamic-subnets module but our default gateway is going to be a transit gateway not an internet gateway as we run everything out through a security VPC that has the IGW. The way the dynamic-subnets module is written foe rhe public subnet routing table it expects an IGW ID be provided. In our case we want that to be the TGW ID. I'm really trying not to reinvent the wheel and have to maintain a whole lot of code to manage this.

@Jeremy G (Cloud Posse) what I found with the VPC module, more to the point the VPC endpoint sub-module, was that while the interface endpoint allowed for the optional subnet IDs to be passed through the gateway endpoint did not accept route table IDs so it could associate the gateway service with the VPC route table. It makes sense having it as a sub-module as you need both the VPC and the subnets created before it can be of use. Inside the sub module makes sense to perform the aws_vpc_endpoint_route_table_association resource definition but it requires passing along the route table IDs. Also it could probably just more simply be passed as the optional property to the aws_vpc_endpoint itself. I thought it could be added as an optional variable in the existing mapped variable just like how the subnet IDs are for interface endpoints.

Question for anyone who has worked with the transit-gateway module as it is... I'm currently working to codify our existing setup that has been done mostly by hand thus far. It follows a hub-spoke design with 2 route tables but we're looking to add a 3rd RT into it. As I have been reading over the module I see it allows passing either a RT you create outside the module or creating one, but it appears like it only deals with a single RT.

Okay so this is down-right silly as far as I'm concerned but I'm being asked if it's possible to not include some of the context tags or rename them. Is it possible at all as is? ie- they want to use App instead of Namespace and Env instead of Environment and not even have the Attributes tag appear. My first response is to say no we have to deal with it but also feel obligated to ask before drawing a line in the sand

a very dumb question if someone can chime in... im trying to set up a lambda backed by a build package (ref), but how do i wire it back to the lambda itself? do i need to specify store_on_s3 or something to push the package into s3?

module "lambda_function_from_package" {
  source = "terraform-aws-modules/lambda/aws"
  version = "3.2.0"

  function_name = "hello-lambda"
  description   = "hello-lambda"
  handler       = "index.handler"
  runtime       = "python3.9"
  maximum_retry_attempts = 0
  timeout       = 60

  create_package = false
  # local_existing_package = "${data.archive_file.source.output_path}"
  source_path = [
    "${path.module}/packages/index.py",
    {
      pip_requirements = "${path.module}/packages/requirements.txt"
      prefix_in_zip    = "vendor"
    }
  ]

...
}

# heres the error i got...

Code: InvalidParameter: 2 validation error(s) found.
│ - minimum field size of 3, UpdateFunctionCodeInput.S3Bucket.
│ - minimum field size of 1, UpdateFunctionCodeInput.S3Key.