https://community.dynatrace.com/t5/Cloud-platforms/AWS-stack-failed-SeedIp-DynatraceNodeSecurityGroup-SeedToken/m-p/127202#M288 <P>Hi,</P><P>please have a look at the list of events of CloudFormation - typically you have more detailed reason for failure when creating a particular resource.</P><P>Common issue may be lack of sufficient permissions to create the stack - resources include IAM role and systems manager parameters, make sure that you CloudFormation is permitted to create these resources.</P><P>Another common issue is hitting your account limits - if you create Dynatrace stack with a new VPC the number of Elastic IP addresses created will exceed the default limit of 5 per region. In such case, you'd need to request a limit increase.</P><P>Please also check the troubleshooting section of deployment guide: <A href="https://s3.amazonaws.com/aws-quickstart/quickstart-dynatrace/doc/dynatrace-managed-cluster-on-the-aws-cloud.pdf">https://s3.amazonaws.com/aws-quickstart/quickstart-dynatrace/doc/dynatrace-managed-cluster-on-the-aws-cloud.pdf</A> for more hints.</P><P>regards,<BR />Krzysztof </P> Thu, 12 Mar 2020 17:05:50 GMT krzysztof_szynt 2020-03-12T17:05:50Z https://community.dynatrace.com/t5/Cloud-platforms/AWS-stack-failed-SeedIp-DynatraceNodeSecurityGroup-SeedToken/m-p/127201#M287 <P>Installing Dynatrace using the the "Deploy Dynatrace Managed into a new VPC on AWS" template, and receive the following error after creation of VPC and bastion host. Any ideas of how to create a successful stack getting past this point?</P><P>The following resource(s) failed to create: [SeedIp, DynatraceNodeSecurityGroup, SeedToken, DynatraceNodeRole, EIP2, EIP3, EIP1].</P> Tue, 11 Feb 2020 05:46:01 GMT https://community.dynatrace.com/t5/Cloud-platforms/AWS-stack-failed-SeedIp-DynatraceNodeSecurityGroup-SeedToken/m-p/127201#M287 anthony_giles 2020-02-11T05:46:01Z https://community.dynatrace.com/t5/Cloud-platforms/AWS-stack-failed-SeedIp-DynatraceNodeSecurityGroup-SeedToken/m-p/127202#M288 <P>Hi,</P><P>please have a look at the list of events of CloudFormation - typically you have more detailed reason for failure when creating a particular resource.</P><P>Common issue may be lack of sufficient permissions to create the stack - resources include IAM role and systems manager parameters, make sure that you CloudFormation is permitted to create these resources.</P><P>Another common issue is hitting your account limits - if you create Dynatrace stack with a new VPC the number of Elastic IP addresses created will exceed the default limit of 5 per region. In such case, you'd need to request a limit increase.</P><P>Please also check the troubleshooting section of deployment guide: <A href="https://s3.amazonaws.com/aws-quickstart/quickstart-dynatrace/doc/dynatrace-managed-cluster-on-the-aws-cloud.pdf">https://s3.amazonaws.com/aws-quickstart/quickstart-dynatrace/doc/dynatrace-managed-cluster-on-the-aws-cloud.pdf</A> for more hints.</P><P>regards,<BR />Krzysztof </P> Thu, 12 Mar 2020 17:05:50 GMT https://community.dynatrace.com/t5/Cloud-platforms/AWS-stack-failed-SeedIp-DynatraceNodeSecurityGroup-SeedToken/m-p/127202#M288 krzysztof_szynt 2020-03-12T17:05:50Z