amazon web services - Cannot Delete ENI - RDS Already Deleted -
i tried deploy code elasticbeanstalk environment. every-time try deploy branch environment eb kills instances, elb, rds, etc , tries rebuild fails. leaves environment in bad state because deletes rds not delete security groups or eni. when try delete security groups manually fails saying there dependant objects.
i traced network interface when try detach (even force detach) error not have permission. eni should have been removed rds instance not. cannot rid of environment @ , cannot rebuild it.
i not sure why application cause environment attempt re-create upon every deployment ec2 instances go away , when load added elb elb cannot health checks put out of service , environment in dead state. nice if somehow see logs causing environments crash application.
having elasticbeanstalk delete instances including rds not acceptable deployment because have re-seed this, not mention if ever deployed production wipe production data , cannot have that.
is there way see going on during deployment , why may happening?
elastic beanstalk uses cloudformation behind scenes. able delete entire environment identifying correct stacks (prefixed awseb-e-j5zfptidfe-stack according logs) , removing them - or @ least removing 1 eni.
you need remove environment within elasticbeanstalk. reset everything. if there dependent stacks - security groups. best solution read messages determine dependencies , clean first.
it practice not include rds in elastic beanstalk stack if know want preserve data in it. create separately , pass in connection details stack. aws provide detailed instructions. short summary be:
- create security group database
- create rds database security group
- add database connection paremeters environment variables eb stack
- add ec2 security group database security group allowed source of traffic db.
finally. need determine why instances being terminated in stack. looks not becoming 'healthy'. disable ignore health check option elastic beanstalk deployments.
this should result in environment ec2 instances marked 'unhealthy'. can use whatever tools need to, diagnose why ec2 instances not correctly responding health checks , resolve issue.
there many reasons ec2 instance fails health check. check incorrectly configured, security groups wrong or service on ec2 instance may not responding should.
Comments
Post a Comment