We'll open a browser and we'll go to
http://PublicDNS/rest/v1/ and we should see something like this:
Setting the Input Locations
Now that the service is running, we need to give it data to read. We'll scroll down until we see a button named
Add inputLocation, go ahead and click it.
In the new text field added, put the name of the bucket that we setup in Prerequisite: Sign up for Programmatic Billing Access.
Then hit the red
Submit button just underneath.
This takes us to the Input Locations page, and if we scroll down to the bottom, we'll see the bucket we just input.
Let us now go back to the root of the service.
The service now knows where to find the files to read, but it hasn't started reading them yet. We can wait an hour for it to poll again, or we can manually reload. Go back to the root level,
http://PublicDNS/rest/v1/, and scroll down to
Manual Reload and hit the red
Submit button there.
This takes us to the reload page, and we can note that the service is now polling (checking for files to new files and loading them).
Next we'll go back to the root of the service.
status sections, click on the
Here we'll see if the service is polling. Once it's done loading all the files on this go around, polling will be
false and the database will be ready to query.
Now that the service is running, what can we do? We can query the database using the service. We can add a custom TCP rule to our security to allow port
5432, then we can log in through ODBC or using the
psql command line tool.