periodic-rds-push | Lambda application

Getting the Lambda instance to operate correctly requires some setup, primarily around configuring an AWS VPC instance for the Lambda and RDS instance.
Create an RDS instance. I used the AWS webui to create an RDS instance. The instance was automatically created with 3 subnets (since I was doing it in eu-central-1, this was 1 subnet per availabilty zone).
In the zappa_settings.json add the vpc_config field and populate it with the SubnetIds and SecurityGroupids The subitems are just the security group and subnets that the webui created for the RDS: "vpc_config" : { "SubnetIds": [ "subnet-b34237c9", "subnet-1e092076", "subnet-affbd0e5" ], "SecurityGroupIds": [ "sg-1c93fb77" ] }
Add the S3 endpoint to the VPC This is done in the VPC config within the webui: VPC Dashboard > Endpoints > Create Endpoint and then follow the instructions
Create NAT Gateway instance + Elastic IP This is where it starts to get convoluted. You need the NAT Gateway to handle address translation for the public/private subnets you're about to create.
Create a new subnet This will be our new public subnet
Create a new route table and move the internet gateway to it The new route table needs to have 0.0.0.0/0 associated with the internet gateway to route properly
Change the 3 existing subnets to use the NAT Gateway Now we change the the ones the RDS wizard created to use the NAT Gateway instance.
a Zappa profile that launches Lambdas in the private subnets,
a connection to S3 via the VPC Endpoint for the service,
access to the RDS since it's in the same subnet,
access to the internet to access other AWS resources such as SQS.