On one hand, I appreciate the extensibility. On the other, I fear that a complex vending process would be fragile, rigid, confusing to maintain, and eventually abandoned out of frustration or lack of understanding.
Regarding the single manifest pattern discussed around the 44-minute mark, it remains the case, to my knowledge, that it's still not possible to retrieve account IDs from the SSM Parameter Store. However, there is also the option to specify multiple account names as deployment_targets. For example, you could include the account names for both the test and production organizations. The CfCT pipeline would then attempt to convert these names into account IDs and compile them into a list. The stack sets are then applied to this list, allowing the CfCT pipeline to execute without any errors. Consequently, a single manifest can be used across two AWS organizations.
Where's the manifest file that is being used to manage multiple organizations? @45:44 Remek says, "let's look at the manifest file our team uses to manage multiple organizations", and then transitions right into the account vending solution... lol?
What English he is talking about, police? He said Police multiple time? He cant even pronounce policy. Go to a college which speaks English is necessary
You might speak a better English than him, but clearly he has very good command on what he does, so his video is featured by AWS in their official documentation and you clearly should focus on knowledge he is sharing than criticizing someone on pronunciation. SHAME ON YOU !
@@vamshikrishna6085 It's valid criticism. He clearly knows what he's talking about, but he's having a hard time expressing complex ideas that are important for this complex topic.
On one hand, I appreciate the extensibility. On the other, I fear that a complex vending process would be fragile, rigid, confusing to maintain, and eventually abandoned out of frustration or lack of understanding.
Regarding the single manifest pattern discussed around the 44-minute mark, it remains the case, to my knowledge, that it's still not possible to retrieve account IDs from the SSM Parameter Store. However, there is also the option to specify multiple account names as deployment_targets. For example, you could include the account names for both the test and production organizations. The CfCT pipeline would then attempt to convert these names into account IDs and compile them into a list. The stack sets are then applied to this list, allowing the CfCT pipeline to execute without any errors. Consequently, a single manifest can be used across two AWS organizations.
Can we get a copy of the all the customization code? I'm mainly interested in the deployment of Audit manger.
Where's the manifest file that is being used to manage multiple organizations? @45:44 Remek says, "let's look at the manifest file our team uses to manage multiple organizations", and then transitions right into the account vending solution... lol?
49:05 "next step, wlasnie, next step" :)
What English he is talking about, police? He said Police multiple time? He cant even pronounce policy. Go to a college which speaks English is necessary
You might speak a better English than him, but clearly he has very good command on what he does, so his video is featured by AWS in their official documentation and you clearly should focus on knowledge he is sharing than criticizing someone on pronunciation. SHAME ON YOU !
@@vamshikrishna6085 It's valid criticism. He clearly knows what he's talking about, but he's having a hard time expressing complex ideas that are important for this complex topic.
A good example of bad explanation. You simple fail to tell me in a few words what problem it is trying solve.