Stack Creation Errors

[scorpiontx-awhelan]

Hello Again,
Getting some additional stack creation errors, any thoughts? Not sure if related to security group again or not, do you have any general guidance on the minimal entries needed within the security group?

• CloudFormation did not receive a response from your Custom Resource. Please check your logs for requestId [dc9341b8-fcd6-4bda-808c-78c1e243c51e]. If you are using the Python cfn-response module, you may need to update your Lambda function code so that CloudFormation can attach the updated version.

-The following resource(s) failed to create: [GetAWSServiceRoleForEC2Spot, Container, GetAWSServiceRoleForEC2SpotFleet]. Rollback requested by user.

Thank You

[jmtroywork]

FYI: I've seen this issue too when specifying existing security group, VPC and subnet. Today I ran the cloudformation stack (link in readme) without specifying security group, VPC and subnet, (and setting multiple-AZ to N) and did NOT get that error.

[scorpiontx-awhelan]

Thanks for the confirmation. I don't want to have a whole new VPC setup. Just curious if your willing would you be able to provide me the security rules it generated?

[brianloyal]

Thanks for reaching out and sorry about the delay responding to your first comment! I'll take look and see what's going on with the "bring your own VPC" option

[scorpiontx-awhelan]

Thanks Brian!

[jmtroywork]

Hi @scorpiontx-awhelan the security group that was created is the default SG for the also created VPC. The inbound rules for the SG reference itself. So if the security group id is sg-123456 the one in-bound rule is Security Group Rule ID=sgr-xxxxxx, Type=All traffic, Protocol=All, Port Range=All, Source=sg-123456. Note that the source references itself. The outbound rule is wide open as shown below:

[scorpiontx-awhelan]

Thanks, I'm thinking it's not likely due tot he SG at this point.

[kyleoconnell-CDC]

Wondering if anyone has found a solution to this issue? I am unable in my account to create a new VPC, but am getting the error at the top, which I am not sure how to troubleshoot.

[kyleoconnell-CDC]

My bring-your-own VPC error has been resolved in the latest version.

[scorpiontx-awhelan]

great news!

[kyleoconnell-CDC]

Only issue is that I don't have a launch template created. Is there recommended launch template or AMI for these compute environments?