Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TodosDynamoDbTable - todos already exists. #38

Closed
safaiyeh opened this issue Dec 20, 2016 · 5 comments
Closed

TodosDynamoDbTable - todos already exists. #38

safaiyeh opened this issue Dec 20, 2016 · 5 comments

Comments

@safaiyeh
Copy link

How does serverless handle DynameDb instances? Running sls destory does not remove the DB instance from AWS.

@DavidWells
Copy link
Contributor

Run sls remove to remove the service

https://serverless.com/framework/docs/providers/aws/cli-reference/remove/

@safaiyeh
Copy link
Author

Whoops, yeah I was running sls remove

Tried again and I am getting the same behavior.
screen shot 2016-12-23 at 2 31 08 pm

@DavidWells
Copy link
Contributor

You might need to login to your AWS console and go to cloudformation and manually delete the stack that is causing this issue.

@nikgraf
Copy link
Contributor

nikgraf commented Jan 14, 2017

@JSafaiyeh the tables DeletionPolicy is set to retain in the example. This means even if you run serverless remove the Table will not be removed to prevent data loss.

You need to go into the console and remove the table manually. Then you can deploy again. Of course you also can change the table name. Let me know if this worked for you 🙂

@nikgraf nikgraf closed this as completed Jan 14, 2017
@quantuminformation
Copy link
Contributor

Does sls remove involve less steps than using the AWS console?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants