5 ms·

Because while "ready" for new features includes API support, it does not include CloudFormation support. The problem is entirely AWS politics and culture.

jcims 6y ago
Who builds the cloudformation support? I could understand not baking it in on an initial feature release but it should be there ’soon’. Same with Config.
- x3n0ph3n3 6y ago
  I've been told that each product team is supposed to add CloudFormation support themselves. For some reason, it's not treated as a high priority and often lands on the laps of the core CloudFormation team. It may turn out that the tools that CloudFormation team provides don't make integration easy, especially if the operation takes longer than 15 minutes (meaning they can't implement support via a single lambda invocation as an under-the-hood custom resource).
  - scarface74 6y ago
    You can also invoke a custom resource via SNS and then the SNS topic is subscribed to an API endpoint. But it’s hard to believe if the team responsible for the blue green deployment functionality developed an API endpoint to do it, they couldn’t just hand it to the CF team to call. At the end of the day that’s all CF does. Call APIs based on the different lifestyle events as far as how it actually creates resources.
    - jcims 6y ago
      >lifestyle events Intentional or not, I'm going to start using this. :P
      - scarface74 6y ago
        Ughhh. And it’s outside of the edit window...
lozenge 6y ago
You would have thought that product teams would love using CloudFormation to create and tear down test resources as it already has code to handle all related resources that they want to interact with (networking objects, DNS, etc)
takeda 6y ago
> The problem is entirely AWS politics and culture. Someone higher up should enforce it. I've been in teams, where if something isn't in cloudformation it doesn't exist and that attitude is totally understandable, having to do some operations by hand seriously hurts IaC efforts.

jcims 6y ago

Who builds the cloudformation support? I could understand not baking it in on an initial feature release but it should be there ’soon’. Same with Config.

x3n0ph3n3 6y ago
I've been told that each product team is supposed to add CloudFormation support themselves. For some reason, it's not treated as a high priority and often lands on the laps of the core CloudFormation team. It may turn out that the tools that CloudFormation team provides don't make integration easy, especially if the operation takes longer than 15 minutes (meaning they can't implement support via a single lambda invocation as an under-the-hood custom resource).
- scarface74 6y ago
  You can also invoke a custom resource via SNS and then the SNS topic is subscribed to an API endpoint. But it’s hard to believe if the team responsible for the blue green deployment functionality developed an API endpoint to do it, they couldn’t just hand it to the CF team to call. At the end of the day that’s all CF does. Call APIs based on the different lifestyle events as far as how it actually creates resources.
  - jcims 6y ago
    >lifestyle events Intentional or not, I'm going to start using this. :P
    - scarface74 6y ago
      Ughhh. And it’s outside of the edit window...

lozenge 6y ago

You would have thought that product teams would love using CloudFormation to create and tear down test resources as it already has code to handle all related resources that they want to interact with (networking objects, DNS, etc)

takeda 6y ago

> The problem is entirely AWS politics and culture. Someone higher up should enforce it. I've been in teams, where if something isn't in cloudformation it doesn't exist and that attitude is totally understandable, having to do some operations by hand seriously hurts IaC efforts.