The Fargate Illusion

Re:The Fargate Illusion by village-idiot on Sunday April 14, 2019 @04:27PM (#19661500)

CF regularly lacks features that TF has, but the list of features is constantly changing as Amazon release new features and CF eventually catches up.

The one that got me this week was that CF cannot define global Dynamo tables, you have to find an alternative way to turn them on.

[ Parent | on HN ]

Re:The Fargate Illusion by scarface74 on Sunday April 14, 2019 @05:01PM (#19661689)

Or just do a quick Google search for a custom resource....

https://github.com/kspurrier/cfn-dynamodb-global-table/blob/...

[ Parent | on HN ]

Re:The Fargate Illusion by village-idiot on Monday April 15, 2019 @11:16AM (#19665927)

Ignoring the obnoxiousness of “just google it” replies, I would consider having to write a custom lambda function to enable global tables to be well within the realm of “CF doesn’t support it”.

Our experience also shows that custom resources can go into a 3 hour timeout cycle if you don’t handle error cases in your lambda perfectly, making them a sub-par development experience.

[ Parent | on HN ]

Re:The Fargate Illusion by scarface74 on Monday April 15, 2019 @12:24PM (#19666530)

Well, if you had an issue with Terraform wouldn't you first look to see if there were already a module for it?

But in the case of "global" tables, they are by definition cross region and CloudFormation stacks are per region.

Looking at the code from the link...

        for region in event['ResourceProperties']['ReplicationGroupList']:
            replication_group.append({ 'RegionName': region})

It is doing stuff across regions.

[ Parent | on HN ]