I'm trying to create stack to deploy fabric blockchain network on EC2, but I've always the same error
The following resource(s) failed to create: [FabricEC2CommonStack]. .
Rollback requested by user. CREATE_FAILED AWS::CloudFormation::Stack
FabricEC2CommonStack Embedded stack
arn:aws:cloudformation:us-east-1:>:stack/FabricStack-FabricEC2CommonStack-NNFUD6RJCZB1/<>
was not successfully created: The following resource(s) failed to
create: [EC2InstanceForDev].
I thought it was a problem with my EC2 Instance profile, but it seems correct. It has the policies to use ECR+S3. Thanks
Related
I'm trying to get this repo going: https://github.com/mydatastack/google-analytics-to-s3.
A link is provided to launch the AWS CloudFormation stack, its meant to be one click to launch the stack but it is no longer working because the S3 bucket containing the template is no longer active.
As a result I'm trying to launch the stack myself via sam deploy --guided --capabilities CAPABILITY_AUTO_EXPAND CAPABILITY_IAM since all the resources for the stack are within the repo. I've added this lambda layer for the paramiko package referenced by collector-ga.yaml to fix this error .
Frustratingly, I'm not quite up and running yet, GlueConfigurationLambda, an AWS lambda function (line 691) failed to create:
Waiting for changeset to be created..
CloudFormation stack changeset
---------------------------------------------------------------------------------------------------------------------
Operation LogicalResourceId ResourceType Replacement
---------------------------------------------------------------------------------------------------------------------
+ Add GoogleAnalyticsCollectorSta AWS::CloudFormation::Stack N/A
ck
---------------------------------------------------------------------------------------------------------------------
Changeset created successfully. arn:aws:cloudformation:eu-central-1:XXXXXX:changeSet/samcli-deploy1628597635/4ee26e-46b5-4131-bdba-1b9fc34f99d6
Previewing CloudFormation changeset before deployment
======================================================
Deploy this changeset? [y/N]: y
2021-08-10 13:14:04 - Waiting for stack create/update to complete
CloudFormation events from changeset
---------------------------------------------------------------------------------------------------------------------------------------------------------
ResourceStatus ResourceType LogicalResourceId ResourceStatusReason
---------------------------------------------------------------------------------------------------------------------------------------------------------
CREATE_IN_PROGRESS AWS::CloudFormation::Stack GoogleAnalyticsCollectorStack -
CREATE_IN_PROGRESS AWS::CloudFormation::Stack GoogleAnalyticsCollectorStack Resource creation Initiated
CREATE_FAILED AWS::CloudFormation::Stack GoogleAnalyticsCollectorStack Embedded stack
arn:aws:cloudformation:eu-central-1:
XXXXXX:stack/GAN2S3-GoogleAnal
yticsCollectorStack-JUATDT3EBD82/e19
a4950-ff27-11ea-943e-06072e1f2808
was not successfully created: The
following resource(s) failed to
create: [GlueConfigurationLambda].
Full Trace - https://pastebin.pl/view/50b3e402
My first question is if there's anywhere to get a more in-depth log of the error?
My second question is if anyone knows how to fix this error.
Can you have a look at the AWS Console CloudFormation application? You should be able to opt to view the Deleted stacks, after which you should be able to select the substack that has failed. In the events list of that deleted stack, you should be able to view a more precise error of what went wrong.
If it's still unclear from that precise error, feel free to edit the question to add the specific error and add a comment to this answer to draw my attention to it.
(Edit)
I've looked through the template file again and noticed the Lambda that's failing is still configured to use Node.js 8, which has been deprecated for some time. You should change it to a newer version, e.g., Node.js 14.
Find the currently supported runtimes here: Lambda runtimes
I used to deploy a Java web application to Elastic Beanstalk (EC2) as root user without this problem. Now I'm using a recommended way of deploying as IAM service user and I get the following errors. I suspect it's because of lack of permissions (policies) but I don't know what policies should I assign to the IAM user.
QUESTION: Could you help me in finding the right policies?
commands:
eb init --profile eb_admin
eb create --single
output of the 2nd command:
Printing Status:
2019-05-26 12:08:58 INFO createEnvironment is starting.
2019-05-26 12:08:59 INFO Using elasticbeanstalk-eu-central-1-726173845157 as Amazon S3 storage bucket for environment data.
2019-05-26 12:09:26 INFO Created security group named: awseb-e-ire9qdzahd-stack-AWSEBSecurityGroup-L5VUAQLDAA9F
2019-05-26 12:09:42 ERROR Stack named 'awseb-e-ire9qdzahd-stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [MountTargetSecurityGroup, AWSEBEIP, sslSecurityGroupIngress, FileSystem].
2019-05-26 12:09:42 ERROR Creating security group failed Reason: The vpc ID 'vpc-7166611a' does not exist (Service: AmazonEC2; Status Code: 400; Error Code: InvalidVpcID.NotFound; Request ID: c1d0ce4d-830d-4b0c-9f84-85d8da4f7243)
2019-05-26 12:09:42 ERROR Creating EIP: 54.93.84.166 failed. Reason: Resource creation cancelled
2019-05-26 12:09:42 ERROR Creating security group ingress named: sslSecurityGroupIngress failed Reason: Resource creation cancelled
2019-05-26 12:09:44 INFO Launched environment: stack-overflow-dev. However, there were issues during launch. See event log for details.
Important!
I use a few .ebextensions scripts in order to initialize the environment:
nginx
https-instance-securitygroup
storage-efs-createfilesystem
storage-efs-mountfilesystem
After reviewing the logs, I also noticed that I forgot to create VPC which is required for EFS filesystem. Could it be that 1 failed script (storage-efs-createfilesystem) is the root cause of subsequent failing operations?
Yes, the lack of VPC has caused the other resources to fail to create. Elastic Beanstalk and the storage-efs-createfilesystem extension use CloudFormation underneath.
storage-efs-createfilesystem Cfn template creates MountTargetSecurityGroup SG and that failed due to lack of VPC. The AWSEBEIP, sslSecurityGroupIngress and FileSystem resource creation is then cancelled.
I'm trying to create a new elastic beanstalk with AWS but it gives me this error.
Stack named 'aws ... -stack' aborted operation. Current state: 'CREATE_FAILED' Reason: The following resource(s) failed to create: [AWSEBAutoScalingGroup].
There is really not many options for me to change something.
not sure if it is related but right afte this error I'm getting another one
Creating Auto Scaling group named: ...-AWSEBAutoScalingGroup-.... failed. Reason: This account is currently blocked and not recognized as a valid account. Please contact aws-verification # amazon.com if you have questions. Launching EC2 instance failed.
I send email to aws-verification # amazon.com, but nothing so far.
You can contact AWS Customer Service (which is different to Customer Support).
They can advise you on the status of the account.
Go to: https://console.aws.amazon.com/support/v1#/case/create?issueType=customer-service
I am trying to use CloudFormation for a WordPress site. I am using the template provided by AWS and 3/4 of the way I am having error which is terminating the process:
12:39:17 UTC-0400 ROLLBACK_IN_PROGRESS AWS::CloudFormation::Stack MyProdWPSite The following resource(s) failed to create: [WebServerGroup]. . Rollback requested by user.
Physical ID:arn:aws:cloudformation:us-west-2:085664598559:stack/MyProdWPSite/955a5660-6b0a-11e7-a813-503aca41a061
Client Request Token:Console-CreateStack-6768960d-41f1-4d9b-b641-b8220af0e895
12:39:16 UTC-0400 CREATE_FAILED AWS::AutoScaling::AutoScalingGroup WebServerGroup Received 0 SUCCESS signal(s) out of 1. Unable to satisfy 100% MinSuccessfulInstancesPercent requirement
Physical ID:MyProdWPSite-WebServerGroup-1DXD0NN8C0R00
Client Request Token:Console-CreateStack-6768960d-41f1-4d9b-b641-b8220af0e895
How can I solve this issue?
I am following this tutorial (http://mobile.awsblog.com/post/TxCD57GZLM2JR/How-to-set-up-Parse-Server-on-AWS-using-AWS-Elastic-Beanstalk) to install parse example on bean stalk. But getting this error. Any idea whats going on?
2016-04-28 22:17:28 UTC-0400 INFO Launched environment:
parseserver-2p4z3-env. However, there were issues during launch. See
event log for details.
2016-04-28 22:17:25 UTC-0400 ERROR Stack named
'awseb-e-b2hkj7pugi-stack' aborted operation. Current
state:'CREATE_FAILED' Reason: The following resource(s) failed to
create:[AWSEBAutoScalingGroup].
2016-04-28 22:17:24 UTC-0400 ERROR Creating Auto Scaling group named:
awseb-e-b2hkj7pugi-stack-AWSEBAutoScalingGroup-1414ZZE9B4G64 failed
Reason: The specified instance type can only be used in a VPC. A
subnet ID or network interface ID is required to carry out the
request. Launching EC2 instance failed.