The first step in your cloud migration project is discovering what you have. With the tidal command, doing a quick scan for web applications and uploading them to your instance of Tidal Migrations is a breeze and a good place to start. You'll add to this with other data sources and through customer engagement from here.
Note: See here for instructions on how to install Tidal Tools and take note of how-to configure your credentials too.
Check it out in action
The command we're going to focus on here is tidal analyze. This command can be run against one web application, a list of URLs, or an IP subnet in CIDR notation like 10.0.0.0/24.
The simplest way to use tidal analyze is against one application:
tidal analyze http://www.mississauga.ca/portal/home
Running against the City of Mississauga's home page should just take a second or two, and present results like:
If you want to import this application to your Tidal Migrations instance, just add --upload.
tidal analyze http://www.mississauga.ca/portal/home --upload
You will see the same results, followed by the happy word "Complete!".
Analyzing more than one URL
As it happens, most folks have multiple applications in their environment that they would like to assess and migrate to the cloud. There are a couple of ways to assess multiple applications, depending on what data you have, you might try these options:
- Simply save a list of URLs in a text file and use that as input.
tidal analyze my_urls.txt --upload
- Get a list of FQDNs from your DNS server based on IPs and subnets with dns-tools.
e.g. if you use Route53
- Scan a network
tidal analyze 10.1.1.1/27 --upload
- Scan multiple networks and DNS services with a "discovery plan"
tidal analyze --plan my_plan.yml
discovery: - network: 10.83.2.0/24 name: My Datacenter front-end tcp_ports: - 80 - 443 dns_service: route53 - network: 10.83.3.0/24 name: My Other Datacenter front-end tcp_ports: - 80 - 443 path_to_bind: "/etc/bind"
Stuck behind a firewall?
No problem. Most of us are.
You can confirm that you are behind a firewall by running tidal ping. If it shows API server xyz is UP, then you're good to go!
But if you are stuck behind the great firewall of IT, or if you just want to inspect all data before sending to Tidal Migrations, output your scan results to JSON and upload later.
tidal analyze my_urls.txt --type json > my_apps.js
and then later, when you can tidal ping
tidal analyze --upload-file=my_apps.js