By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Newbie stuck creating a Stack with CloudFormation

0

Hi, I am new to the CloudFormation, trying to create support for a perforce server and followed the instructions and recommendations here Cloudformation intro

The only template I need is https://gametech-cfn-templates-public.s3.amazonaws.com/aws-perforce/templates/PerforceTemplateMain.yaml (though I couldn't locate this template within your aws, that would be nice to know too).

My Key Pair is selectable from the Specify Stack Details step and I reach the CREATE_IN_PROGRESS status.

After that, it always fails to create the PerforceMasterServerInstance with CREATED_FAILED error,

Embedded stack arn:aws:cloudformation:us-west-2:##########:stack/AWSPerforceTest-PerforceMasterServerInstance-######/#####3 was not successfully created: The following resource(s) failed to create: [VolumeHxdepots, VolumeHxmetadata].

Is there something missing on my account settings to access this service? My current plan is Basic and i know the CloudFormation is charged on demand, would that be ok as well?

Topics
Management & Governance
Tags
AWS CloudFormation
Language
English
dagonmeister
asked 10 months ago357 views
1 Answer
1

Hi,

Around the time of failure, you should see an additional nested stack for Perforce server with a prefix like stackname-PerforceMasterServerInstance. In the resources section you can see the resource creation status. Click on each of the failed resource and identify the reason.

Volume Size and IOPS need to be integer but are defined as strings in Parameters. I changed it to Number and was able to launch the requisite stack

--Syd

profile picture
Syd
answered 10 months ago
  • dagonmeister
    10 months ago

    Hi,

    Thank you for your support.

    Following the nested stack error logs, it is indeed the stackname-PerforceMasterServerInstance step with the [VolumeHxmetada].

    Properties validation failed for resource VolumeHxmetadata with message: #/Iops: expected type: Integer, found: String

    It is perhaps the last misconfiguration, I tried setting an integer number before but it complained with a different error gp2 not supporting Iops. I set it to 0 and again complained that [The parameter iops is not supported for gp2 volumes], did you notice same issue?

    Should I maybe just select the type io1 (which I believe is more expensive)?

    Regards

  • dagonmeister
    10 months ago

    Yes, after playing with more values using the error logs as you described i finally managed to create a success result. I did selected the io1 type to get an OK with my EC2 instance.

  • Syd
    10 months ago

    gp2 does not support IOPS. If you need to set IOPS, you need to change the volume type to io1 which obviously means higher cost. Also I guess the template you are using is perhaps an older one. Unless this exercise is only for testing and learning, you should be using gp3 rather than gp2 where you get 3000 IOPS by default

  • dagonmeister
    10 months ago

    Hi Syd, Absolutely seems old, where are those templates? I couldn't locate them within the AWS services. Can you direct me to the latest version?

  • Syd
    10 months ago

    Sorry I dont have the latest ones. I only inferred that was the case on the basis that it's using gp2 while gp3 has been out for quite some time.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content