[DOCS-3526] Document best practices for migrating from EC2 Classic to EC2 VPC Created: 02/Jun/14 Updated: 11/Jan/17 Resolved: 27/Jul/16 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | ecosystem |
| Affects Version/s: | None |
| Fix Version/s: | 01112017-cleanup |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 7 years, 29 weeks ago | ||||
| Description |
|
Some of this is covered in a general sense by http://docs.mongodb.org/manual/tutorial/migrate-sharded-cluster-to-new-hardware/ , but it would be useful to have a document for the specific (and increasingly common) case of migrating from AWS EC2 "Classic" to EC2 "Virtual Private Cloud" (VPC). |
| Comments |
| Comment by Emily Hall [ 27/Jul/16 ] |
|
Closed by Emily Hall for Housekeeping on 7/27/16. Thank you! |