So the aws Alias thing is probly more of an enhancement request, unless I’m Missing Something.  I’ve attached two screenshots from my aws interface and one from Fivetran’s setup screens.  The first (“lambda_function_name_dashboard.png) shows the name of the function which Fivetran calls to update our PostgreSQL (circled). You can see the hint that I am managing this function through CloudFormation just below it with an arrow pointing to it. The function name ends with “-pAYn9t4hQ52W” – that’s the 12-character random string that CloudFormation puts on the name I gave it in the script I used to create my Stack. Every time I do a Full reload of the Stack (that is, reload the libraries _and_ my application code) or drop and reload the Stack, that random string is gonna change, and I ( or my successor) will have to go back into FiveTran’s Connector screen and change the “Lambda Function” name there for Things to Continue to Work.  There’s about an 80% probability that this will be screwed up.

The second attachment (“alas_name_tab.png”) shows the contents of the “Alias” tab my aws Stack-managed function. I can force that alias (circled, it’s “mavenlink-to-fivetran”) to be the same in my CloudFormation Stack no matter how many times I do a Full reload or drop and reload my side.  But if I attempt to put that name into the “Lambda Function” box in the Fivetran Lambda Function setup form, I get the “not found” error you can see in “alias_wont_work.png”.  This alias is different from the function name and has its own life in aws; I suspect that if instead of asking for a name you asked for an arn I could do ‘er.

Lambda_function_name_dashboard.png:

alas_name_tab.png: