I had a situation where I incorrectly entered the PaGroupTemplateUrl when setting up the transit vpc account, which caused an error in the createNewPaGroup-transitVpcAccout function, failing with the following exception:
botocore.exceptions.ClientError: An error occurred (ValidationError) when
calling the CreateStack operation: TemplateURL must be an Amazon S3 URL.
Realizing my mistake, I then tried correcting the error by updating the stack. The updated stack applied just fine, but got the same error.
Digging into the DynamoDb table: TransitConfig-transitVpcAccout, I noticed that the parameter: PaGroupTemplateUrl was still set to the original, incorrect url for the paGroupCft.json file, even though the cloud formation stack had been successfully updated.
I learned that the causes is that the lambda TransitConfig-transitVpcAccout does not update the dynamo tables on a cloudformation update event.
I will submit a PR to update lambda/initializeTransitDynamoTables.py from:
I had a situation where I incorrectly entered the PaGroupTemplateUrl when setting up the transit vpc account, which caused an error in the createNewPaGroup-transitVpcAccout function, failing with the following exception:
botocore.exceptions.ClientError: An error occurred (ValidationError) when calling the CreateStack operation: TemplateURL must be an Amazon S3 URL.
Realizing my mistake, I then tried correcting the error by updating the stack. The updated stack applied just fine, but got the same error.
Digging into the DynamoDb table: TransitConfig-transitVpcAccout, I noticed that the parameter: PaGroupTemplateUrl was still set to the original, incorrect url for the paGroupCft.json file, even though the cloud formation stack had been successfully updated.
I learned that the causes is that the lambda TransitConfig-transitVpcAccout does not update the dynamo tables on a cloudformation update event.
I will submit a PR to update lambda/initializeTransitDynamoTables.py from:
to: