Migrate AWS (legacy) to AWS
StackState Self-hosted v5.1.x
Overview
The new AWS integration available from StackState v4.4 is an entirely new StackPack that replaces the old AWS (legacy) StackPack. The AWS (legacy) StackPack has now been deprecated, and it's advised that you migrate your StackState AWS integration to use the new AWS StackPack.
In the new AWS integration, topology data is collected using StackState Agent V3. Within StackState, each installed AWS StackPack instance can now be used to collect data from all regions in a single account.
Migrate from AWS (legacy)
The best way to start using the new AWS integration is to migrate one AWS account at a time. In the new AWS integration, data for all regions associated with an account can be gathered by one StackPack instance. This means that one AWS StackPack instance can replace a number of AWS (legacy) StackPack instances.
To migrate AWS accounts from the AWS (legacy) StackPack to the new AWS StackPack:
Install StackState Agent V3 on a machine that can connect to both AWS and StackState.
For each region that you will migrate, deploy an AWS CloudFormation stack.
For the account to be migrated, install an AWS StackPack instance.
Configure the StackState Agent V3 AWS check with the
role_arnand theregionsassociated with the account.For the account and regions being migrated, uninstall all related instances of the AWS (legacy) StackPack.
Restart StackState Agent V3 to apply the configuration changes and enable the updated AWS check.
Once the Agent has restarted, wait for data to be collected from AWS and sent to StackState.
Repeat steps 2 to 7 for each account you want to migrate.
Labels in StackState
During migration, topology data from the new AWS integration and the AWS (legacy) integration can be identified by the labels attached to components in StackState:
stackpack:aws-v2
New AWS integration
stackpack:aws
AWS (legacy) integration
Last updated