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

aws_instance: change instance type causes instance destroy/create #2423

Closed
partamonov opened this issue Jun 22, 2015 · 5 comments
Closed

aws_instance: change instance type causes instance destroy/create #2423

partamonov opened this issue Jun 22, 2015 · 5 comments

Comments

@partamonov
Copy link

Currently if you change aws instance(ebs root storage) type this will cause instance re-creation.
http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html
But AWS allows to change instance type only by stopping it, changing instance size and start it. CFN also in case of change of instance size just stop, change and start instance

@ghost
Copy link

ghost commented Jun 25, 2015

@partamonov several improvements must be done about aws_instance resources and other dependencies; currently terraform have an approach where several resources modified need to be recreated.

@catsby
Copy link
Contributor

catsby commented Dec 2, 2015

Hey @partamonov – I'm going to close this as a duplicate of #1887 and/or #1579 . The need to manage stop or other state like this noted there. Thanks!

@catsby catsby closed this as completed Dec 2, 2015
@tomstachura
Copy link

Is this in a plan to be fixed? It would be great if the instance survived.

@salewski
Copy link
Contributor

salewski commented Apr 2, 2017

For folks landing here from a google search: it looks like this feature was implemented in issue #9157 (see pull #11998), which was included in the terraform-0.8.8 release (2017-03-02).

@ghost
Copy link

ghost commented Apr 14, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants