Updating AWS AMI for Plakar Control Plane
#Plakar Control Plane is distributed on AWS as an Amazon Machine Image (AMI) through AWS Marketplace.
Most Plakar Control Plane updates can be installed directly page without replacing the EC2 instance. However, in rare cases, the underlying AMI also needs to be updated. This usually happens when infrastructure-level changes are required.
Deployment layout
#A Plakar Control Plane deployment on AWS runs as an EC2 instance with two attached EBS volumes:
- A small root volume used for the operating system (
1GB) - A larger data volume used to store Plakar Control Plane data (
1TB)
The important volume is the larger data volume because it contains the actual Plakar Control Plane data.
Updating the AMI
#The update process consists of:
- Detaching the existing data volume
- Deploying a new EC2 instance from the newer AMI
- Reattaching the existing data volume to the new instance
1. Stop the current instance
#Stop the currently running Plakar Control Plane EC2 instance before making any storage changes.
2. Detach the existing data volume
#Locate the larger attached data volume (1TB) and detach it from the stopped instance. Before detaching the volume, note down the volume ID because the same volume will later be attached to the new instance.
Volume ID
Make sure you detach the larger data volume and not the root volume.
3. Launch a new Plakar Control Plane instance
#Deploy a new Plakar Control Plane instance from AWS Marketplace using the newer AMI. Follow the standard deployment process documented in the AWS installation guide.
The new instance will be provisioned with:
- A new root volume
- A new empty data volume
4. Stop the new instance
#Once the new instance has been provisioned successfully, stop it before modifying its attached volumes.
5. Remove the new empty data volume
#Detach the newly created empty data volume from the new instance. This volume is not needed because the original data volume from the previous deployment will be reused instead.
Do not delete the detached volume yet until the migration is confirmed working correctly.
6. Attach the old data volume
#Attach the original data volume from the previous instance to the new instance. Once attached, the new instance will use the existing Plakar Control Plane data and configuration.
7. Reconfigure instance settings
#Reapply any configuration that existed on the previous instance. This may include:
- IAM roles
- Security groups
- Elastic IP assignments
- DNS configuration
- Monitoring or automation integrations
8. Start the new instance
#Start the new EC2 instance.
Once the instance is running, Plakar Control Plane should resume normally using the existing data volume. All inventories, schedules, policies, configuration, and backup data should remain intact.
9. Cleanup
#After confirming the new deployment is working correctly, you can safely remove unused resources:
- Delete the old EC2 instance
- Delete the old root volume
- Delete the unused empty data volume created with the new instance
Deleting Volumes
Do not delete any volumes until you have verified the new deployment is working correctly.