null (Service: AmazonRDS; Status Code: 500; Error Code: InternalFailure when launching documentdb

[regaltopax]

Describe the bug

AWS Cloudformation Create/Update Stack fails with 500 error when creating a document DB cluster with null (Service: AmazonRDS; Status Code: 500; Error Code: InternalFailure CreateDBCluster' api call isn't being issued when we check Cloudtrail To reproduce In AzureDevops Create a Pipeline Under tasks, Add task AWS Cloudformation Create/Update Stack Use the template provided either as a LocalFile in Template Source, or source it from S3Bucket. Inline Parameters, reference the provided parameters from the Template [ { "ParameterKey":"VpcId", "ParameterValue":"$(VpcId)"}, { "ParameterKey":"DocDBSubnets", "ParameterValue":"$(DocDBSubnets)"}, { "ParameterKey":"DocDBInstanceSize", "ParameterValue":"$(DocDBInstanceSize)"}, { "ParameterKey":"DocDBUsername", "ParameterValue":"$(DocDBUsername)"}, { "ParameterKey":"DocDBPassword", "ParameterValue":"$(DocDBPassword)"} ] Under Capabilities specify CAPABILITIES_IAM and CAPABILITY_NAMED_IAM Create Release Pipeline Error: Stack creation request failed with error: 'Stack my-stack failed to reach completion status, error: 'Resource is not in the state stackCreateComplete'' Error: Stackmy-stack failed to reach completion status, error: 'Resource is not in the state stackCreateComplete

Expected behavior Cloudformation stack is created with DocumentDB

Screenshots

Here is the template doc.txt

Your Environment

• AWSTools for Microsoft Visual Studio Team Services 1.5.0 running on Azure Devops

Additional context The same template used to work without issues using the VSTS Tools version 14.0. This template works locally via cli, powershell Only fails on version 15.0

[rli]

Given that the template works everywhere else, and the "InternalFailure", this appears to be a transitive service issue.

Could you delete the stack and try again?

[regaltopax]

Thanks for the reply @rli . I have actually been having this same problem now for 2 straight weeks, using different stack-names. It has consistently failed. We actually thought it was transient issue also, but it seems consistent with the same error message

Here is a retry from today

[regaltopax]

Any progress on this please?