I'm trying to create a DB stack, it has and RDS Cluster, and RDS Proxy and some other stuff.
When I first run cdk deploy always fails half way with the following message:
Embedded stack
arn:aws:cloudformation:us-east-2:####:stack/MainStack-DBNestedStackDBNestedStackResource####/###
was not successfully created: The following resource(s) failed to create: [memcachedApp, Parameters6795E5B4, DatabaseproxyIAMRole7D0578A1].
If I run again cdk deploy it works.
I'm trying to find out what is causing the error but I don't know where to look and because the ROLLBACK start immediately, I can't see any more errors.
Do you know if there is something I missing?
Related
I use cdk to deploy my AWS stack. It's NextJS app with RDS instance. Initialization Database I do using CustomResource approach (Lambda build from Docker image) as suggested that Article
Sometimes my deployment fails with error message
Received response status [FAILED] from custom resource. Message returned: Connection timed out after 120000ms
Im sure because my database init takes to much time. I do filling the database with "INSERT INTO" SQL queries that repeat about 5000 times.
Could you advise how to avoid that error because deployment script is unstable and I can't rely on it? Many thanks.
When I try to run codedeploy, I get the following error :
The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems.
When I look at the ec2 instances created by the auto scalable group, they are both running, and status is passed 2/2 checks passed in green. I am wondering if this is just a catch all error, because its supposed to throw this error if one or both or all are not running.
It seems it wanted an appspec.yml. I am not sure why a appspec.yml is needed, If you create the autodeploy group, and create the codedeploy application, why is there a need for a appspec.yml. I am using jenkins to run the code deploy. I gave it a appspec.yml that is empty, and seems to work.
I am creating a VPC through aws cdk on vscode. While running the cdk bootstrap it is creating a stack successfully but after running cd deploy it is showing vpc creation failed and ROLLBACK is also not created.
Error Code: AddressLimitExceeded
I have tried creating vpc earlier with same approach and it was a success but now I am trying to create another vpc with same approach its showing several errors after deploying. Please help me understand and resolve this issue.
Base on your capture, you reached the maximum EIPs (5 EIPs), you need to delete the not in use EIPs or submit a ticket to increase your quota.
I wanted to delete an ASP.NET MVC application on the Elastic Beanstalk. But before deleting the app I first deleted the RDS server instance linked to the application. The RDS instance got deleted succesfully but now when I try to delete the Elastic Beanstalk application I get the following error message in the console -
Stack deletion failed: The following resources failed to delete AWSEBRDSDatabase
How do I proceed to delete this? I am not able to find any help regarding this issue!
ran across the same issue myself today.. there doesn't appear to be a way to delink the deleted RDS instance in the Elastic Beanstalk configuration sadly. I did however manage to delete the application though by first recreating the RDS instance using the same name as before.
Go to AWS RDS > Intances > Launch DB Instance
recreate the deleted instance using the exact name that was previously used. Once successfully created, go back to Elastic Beanstalk and it allows you to terminate the environment. Bit of a pain but works none the less.
Thanks
TJ
It happened to me and the way I was able to resume the removal of Elasticbeanstalk sucked on this status was to go through CloudFormation panel and remove the stack with failed status as described on: https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-delete-failed/
After that I was able to remove the Environment and Application under Elasticbeanstalk.
I had this error "The following resource(s) failed to delete: [AWSEBRDSDatabase]" this helped me to resolve the problem.
Open the AWS CloudFormation console.
Choose the stack that's stuck in DELETE_FAILED status.
Choose Delete.
Note: A window opens and lists the resources that failed to delete.
4. In the window, select all the resources that you want to retain, and then choose Delete stack.
I checked to retain resource, even though the resource that was retained didn't exist but it helped me to delete it, if I didn't check it it was not deleted
https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-delete-failed/
https://aws.amazon.com/premiumsupport/knowledge-center/elastic-beanstalk-deleted-rds-database/
I am working with Blue/Green Deployment using AWS CodeDeploy. The sample deployment provided by AWS is working fine but when I am doing the same thing using custom Deployment, I am getting the following error:
The overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems. (Error code: HEALTH_CONSTRAINTS)
Can anyone help me with this?
You get this error when the overall deployment failed because too many individual instances failed deployment, too few healthy instances are available for deployment, or some instances in your deployment group are experiencing problems. You can check which lifecycle event failed for the instance and what is the error, also it would be helpful to log in to the failed instance and check the host agent logs.