I was creating a CloudFormation stack using a sample JSON template shown in below link:
https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/quickref-opsworks.html
However, I am getting a same error again and again i.e.
Error link
Please help me in troubleshooting the error.
Regards,
Raghav
Related
I created my AWS account, and I'm trying to manually create a bucket through the console. But all the action buttons are disabled, and it shows An unexpected error occurred as in the image below. Has anyone experienced this? What could be the possible cause of this?
When trying to update cloudformation stack below issue is coming. I found this error in cloudtrail logs.
"errorCode": "ValidationException",
"errorMessage": "No updates are to be performed."
what could be the reason ? i am trying to update parameters in CFT stck
I figured it out, there were some set of parameters which needs to be updated for auto scaling. it was not allowing to update single parameters.
by modifying some other parameters it started working
I'm just starting my serverless/cloudformation/AWS SAM journey. I've created a stack that has a resource of type AWS::CloudFormation::Stack, and I've separated some of my resources into that child stack.
When I do sam build and then sam deploy, I get the following error:
Embedded stack arn:aws:cloudformation:us-
west-2:111111111111:stack/ParentStack-
ChildStack-1QK94LXRA71CS/f9885e30-631c-11eb-
bfd8-021cb123b7ed was not successfully created: The
following resource(s) failed to create: [DynamoDBTable].
-
The following resource(s) failed to create:
[ChildStack].
Of course, what I really want to know is which resource in the nested stack failed to create, and why. When I copy/paste the resources from the child stack into the parent .yaml file and rebuild/redeploy, I see:
One or more parameter values were invalid: Some index key
attributes are not defined in AttributeDefinitions. Keys:
[userID], AttributeDefinitions: [userId] (Service:
AmazonDynamoDBv2; Status Code: 400; Error Code:
ValidationException; Request ID:
SMJDHUT0CQKM8IBQJVMAIJM4RRVV4KQNSO5AEMVJF66Q9ASUAAJG;
Proxy: null)
This is what I want to see in the output when I build the parent stack: the errors that caused the child stack to fail.
This has led me to use a rather tortuous workflow: build the resources in the main stack, then separate them to an independent stack when they build properly. There's got to be a better way, and I'm sure the community knows something here that I don't.
How do y'all debug child stacks when you're on the CloudFormation train?
This is normal behaviour you have to take help from the AWS Console or use AWSW CLI in this case.
Deploy error reporting is not showing the reason of failure when using nested stacks. #5974
Feature Requests for nested stacks
Why doesn't the error tell me what's wrong?:
CloudFormation passes the creation and updating of a resource to the service responsible for those resources. When a resource fails to create/update, the resource's backing service returns a reason to the stack, which gets logged as the Status Reason within the events. Child Stack is a CloudFormation::Stack resource, so it's being created by CloudFormation. As far as CloudFormation knows, it didn't run into an error trying to actually do anything. Everything it did relate to the CloudFormation side of things was fine; the blame is with the Service resource, which failed to create it. Therefore, Child Stack tells Parent-Stack that it only failed because Service failed to create, not because of a problem on the CloudFormation Service side of things.
you can read more about it here CloudFormation troubleshooting
So i am using the https://github.com/commonsearch/cosr-ops/ deployment tool for commonsearch. The tool creates clusters/instances in CloudFormation!
I had quite a few bugs with it, witch i fixed myslef, but this one i have been hitting my head for 2 days now.
Some things fail to CREATE, when calling make aws_elasticsearch_create
Error listed below, any ideas?
The following resource(s) failed to create: [ElasticsearchLbLaunchConfiguration, ElasticsearchMasterLaunchConfiguration, ElasticsearchDataLaunchConfiguration]. . Rollback requested by user.
I resolved this by changing MAPPINGS ami's.
BUT!
Ran into antoher problem.
This time its not the Configs, but the Scalings.
See below:
The following resource(s) failed to create: [ElasticsearchLbAutoScalingGroup, ElasticsearchMasterAutoScalingGroup, ElasticsearchDataAutoScalingGroup]. . Rollback requested by user.
Any ideas are welcome. Help a fellow programmer sort this out :)
Finally, i got progress!
You must signal the AutoScaling resources from local konsole, fot them to proceed. Heres how you do it:
aws cloudformation signal-resource --stack-name search-elasticsearch --logical-resource-id ElasticsearchDataAutoScalingGroup --status SUCCESS --unique-id ElasticsearchDataAutoScalingGroup
I have alredy next error, but its validation error. Will try to figure it out.
I was trying to execute the sample Access Analysis from the WSO CEP samples. After I created the bucket same as given in the sample I received an error and it doesn't created the bucket. Can any one help what is the problem?
Error log:
[2012-12-13 15:09:21,654] INFO {org.apache.axis2.deployment.DeploymentEngine} -
org.apache.axis2.deployment.DeploymentException: wrong configuration provided for adding AccessAnalysisBucket.xml
This error was appearing when I gave query syntax at the Add query Expression. If i am not giving this, it will create the bucket.