Examples of using Original instance in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Then you can terminate the original instance.
If the original instance is a Reserved Instance, change the Availability Zone for your reservation.
Returning an Expanded Partition to Its Original Instance.
Then, you can terminate the original instance, or wait for it to terminate as scheduled.
Now, we can interpret the prediction made for the original instance.
If the original instance has an associated Elastic IP address, associate it with the new instance. .
This file contains the MAC address for the Ethernet adapter of the original instance.
You can use the same instance type as the original instance, or select a new instance type.
On the Choose an AMI page,select the same AMI that you used to launch the original instance.
Select the Elastic IP address that is associated with the original instance, choose Actions, and then choose Disassociate address.
If you don't specify the same device name as the original attachment, you cannot start the original instance.
Any EBS volumes that you detached from the original instance and want to attach to the new instance, or new EBS volumes based on the snapshots that you created.
Select the instance and verify that you are about to terminate the original instance, not the new instance. .
For example, if the original instance uses the AWS Windows AMI for Windows Server 2008 R2, launch the temporary instance using the AWS Windows AMI for Windows Server 2012.
From the temporary instance, unmount the volume that you attached so that you can reattach it to the original instance.
The migration process involves creating an AMI from the original instance, launching an instance in the new Availability Zone, and updating the configuration of the new instance, .
This enables you to connect tothe new instance using the same private key file as your original instance.
While this is similar to its normal"replacement" behavior, the original instance will continue to exhibit the same properties, replicating if damaged and continuing to"replace" itself every 24 hours.
If you want to allow the same traffic to reach the new instance, select the security group that is associated with the original instance.
Keep the original instances in the deployment group running: After traffic is rerouted to the replacement environment, the instances that were deregistered from the load balancer are kept running.
A blue/green deployment registers a replacement set of instances for the deployment group with a load balancer andderegisters the original instances.
If you launched your original instance from an AWS Marketplace AMI and your volume contains AWS Marketplace codes, you must first stop the temporary instance before you can attach the volume.
Switching back to the most recent version of an application is faster andmore reliable because traffic can be routed back to the original instances as long as they have not been terminated.
The similarity between each permuted instance and the original instance feeds as a weight into the simple model so that higher importance is given to instances which are more similar to the original instance. .
However, when instances in the original environment are deregistered from the load balancer,the overall deployment is marked as Failed if even a single original instance fails to be deregistered successfully.
In a blue/green deployment, traffic is rerouted from one set of instances to another by deregistering the original instances from a load balancer and registering a replacement set of instances that typically has the latest application revision already installed.
If you create a Linux AMI from an instance, and then use the AMI to launch a new instance in a different region or account,the new instance includes the public key from the original instance.
Create an AMI from the instance, launch a new instance from this AMI with the security groups that you need, disassociate any Elastic IP address from the original instance and associate it with the new instance, and then terminate the original instance.
If you want to maintain normal operation during a scheduled maintenance window, you can launch a replacement instance from your most recent AMI,migrate all necessary data to the replacement instance before the scheduled maintenance window, and then terminate the original instance.
You must stop the instance, detach its root volume and attach it to another instance as a data volume, modify the authorized_keys file,move the volume back to the original instance, and restart the instance. .