Tide can be used to compare and copy auto scaling groups, launch configurations, load balancers and security groups across your AWS VPCs, regions and accounts.

Spinnaker refers to an auto scaling group and all of its attached cloud resources as a server group. Tide is capable of migrating a server group to another location (account, region, and VPC). It performs a "deep copy" meaning that it will copy the whole server group including attached launch configurations, load balancers and security groups if they don't already exist in the new location. It can handle cyclical references and any necessary naming changes (load balancers must have unique names across all VPCs in a region). Nothing will be deleted or modified but new resources may be created. New ASGs will be disabled (not taking traffic) with zero instances. There is a "dry run" ability to show what will be created and why.

It is possible to migrate these without being attached to an ASG.

Tide can migrate a pipeline to another VPC. Copying a pipeline to another region or account raises some questions.

Tide can show differences of attributes across multiple AWS resources. It can be useful to see a diff of all security groups with the same name in an account for example.

It may also be handy as a cache for avoiding AWS throttling for reads of the resources mentioned above.

There is a task system that allows for long running tasks. Akka clustering and persistence are used to make the async task system resilient. Note that tide creates an Akka "cluster" from instances found in the same Spinnaker "cluster". Tasks can move between instances in the cluster. Tasks will also restart if all instances are terminated and then launched again.

New task types are easy to implement and harness task system functionality such as the task lifecycle, subtasks, parallel execution, and logging. Migrations are a type of task. There is also a task type that can continuously attach classicLink to running instances that need it.

See the swagger docs for usage: http://host/swagger-ui.html

• Redis is used by Akka to persist events.
• Edda (or AWS directly) is used for AWS read operations.
• CloudDriver is used for AWS write operations.
• Front50 is used for pipeline management.

Tide is configured like all other Spinnaker services.

AWS account config is handled just like CloudDriver.

You can find an example config file in the codebase. Note that you will need to add specifics for the dependencies mentioned above and AWS account specifics.

./gradlew bootRun