Migrating stacks between spaces with AWS integrations and worker pools

Last updated: December 19, 2025

When migrating stacks between spaces in Spacelift, you may encounter issues with AWS integrations and worker pools that prevent the migration from completing successfully.

AWS Integrations and Space Migration

AWS integrations in Spacelift are space-specific by design for security and organization purposes. This means they cannot be shared across spaces, and you'll receive an error when trying to move a stack that has attached integrations to a different space.

To successfully migrate stacks with AWS integrations:

  1. Create a new AWS integration in the target space with the same permissions and configuration as the original

  2. Detach the existing integration from the stack by going to Stack → Stack Settings → Stack Details → Integrations → Remove

  3. Move the stack to the target space

  4. Attach the new AWS integration to the stack in the target space

Worker Pool Considerations

Worker pools are also scoped to the space they're created in, which means stacks in a new space will need access to a worker pool within that space.

You have two options for handling worker pools during migration:

  • Create new worker pools: Set up dedicated worker pools in each target space

  • Temporary root space approach: Move your worker pool to the root space temporarily, allowing child spaces to inherit it during migration. After migration is complete, you can rescope the worker pool back to its original space if needed

Best Practices for Space Migration

To avoid setup issues and ensure a smooth migration process, follow these steps before migrating stacks:

  1. Pre-configure all necessary AWS integrations in the target space

  2. Set up required worker pools in the target space

  3. Ensure permissions and configurations match the original resources

  4. Test the setup with a sample stack to confirm everything works as expected

  5. Only then proceed with migrating your production stacks

This preparation approach helps prevent the need to repeatedly go back and fix configuration issues after attempting stack migrations.