Open CharlesShen opened 4 years ago
I confirmed the newly spun up instance is the same (old) type by checking in EC2. (I went through the repo steps to see if it was only the Beanstalk UI that was not refreshing).
Any updates on this issue? I just ran into it when trying to move to a t2.small from t2.micro?
We are thinking that this would be come something you can only adjust from the Toolkit by re-publishing your application to Beanstalk. Have you tried that? Alternatively, have you tried changing the instance type from the web console?
i was able to change the instance type within the auto scaling group and the console took care of the rest. much easier fix than i imagined, but it is really odd that the AWS Toolkit in Visual Studio will let you apply changes, and create a new EC2 instance but when you check instance type after it is deployed it is whatever you had before (in my case t2.micro)
Any attempts to change instance type with the AWS Toolkit does not work. After hitting Apply, Elastic Beanstalk goes through its process of instantiating a new instance with the new instance type. However, after that process is done, you'll see that no changes have been made and the newly created instance is the original instance type.
Below is the EB trace when the Apply button is clicked
ebconfig.txt