Brooke: Hello, everyone. Thank you for joining today's webinar on Get the Most Out of GoAnywhere: Achieving Cloud File Transfers and Integrations. We know many of you are current customers and some of you are new to GoAnywhere. So either way, welcome, and we're glad you're here. A few things to know before we get started. The event is scheduled for an hour. We are recording the event. So if you'd like to rewatch it or share it with a colleague afterwards, you definitely can. We'll send out a link to the recording within a day after the event. If you have any questions throughout the webinar, please submit them through the Q&A pane, and we'll have a couple of team members online answering them throughout the presentation. We'll also, if time permits, have a Q&A time at the end of the webinar if you'd like to stay on the line and submit a question live.
Lastly, after we wrap up today, you'll see a quick survey pop up. Filling that survey out gives us good feedback on what parts of the presentation were most helpful to you. If you have any questions that aren't answered on today's call, you can enter those there as well and someone will get them to you. So without further ado, let me introduce you to our speakers for today. So we'll actually have two presenters today. I'll go ahead and introduce you to both of them. Dan Freeman has spent the last 10 years of his career in various security roles ranging from system engineered to security officer, and he currently serves as senior solutions consultant at help systems for the GoAnywhere product line. Then Steve Luebbe has been in IT for 18 years, and he currently heads up research and development at HelpSystems for the GoAnywhere product line. Welcome Dan and Steve.
Dan Freeman: Thank you.
Brooke: All right. So I will go through our agenda quick, and then I'll hand it off to these guys. So what we're going to cover today is starting with the cloud kind of overview of benefits, the growth of the cloud and common objections to the cloud that people often have. We're going to talk through capability that GoAnywhere offers in terms of the cloud, and then we're going to talk through our cloud connectors, what they are, how to use them and some cool examples of how customers are actually already using them in their environments. As I mentioned, we will have some time for questions at the end. With that, Dan and Steve, you guys can take it away.
Benefits, Growth, and Common Objections to the Cloud
Dan Freeman: All right. Thanks, Brooke. I appreciate it, and thanks to, excuse me, every that did take the time out to go ahead and listen to this webinar kind of on our part series that we picked up from last year to get the most out of GoAnywhere series. Today we're going to focus on the cloud, as Brooke mentioned. We will be taking a closer look at some of the benefits of cloud service providers and how going to work can leverage both the infrastructure as a service as well as some native [inaudible 00:02:44] connections, the via rest and back at API calls and our latest cloud connectors, which Steve will dive into a little bit later in the presentation.
Now, some of you may have been... I've had the wonderful privilege to attend a similar cloud-based webinar, so our opening joke might be a bit repetitive, but don't refresh. We'll expand on that set joke just a little bit. Now, without further ado, a very important questions to set the stage and get a good visual of the content today, I'm compelled to ask, what kind of clothes do clouds wear? I know you guys are on mute, you can't answer, but I'm sure everybody's screaming out thunder wear. It totally makes sense. It goes without saying.
Now, having said that, it kind of gives it a little different perspective when you're outside, maybe enjoying, singing in the rain, just singing in the rain. Okay. I'll pull that back in. I digress. No one gets it. Well, let's just think about that one for a little bit. But definitely, like factor in the right frame of mind knows, let's dive in and get busy, shall we?
All right. So what's all the fuss about moving to the cloud? Although it may not be perfect or even the best solution for all businesses, there are a lot of reasons and advantages for doing so. Flexibility. Now, being able to meet the ever-changing demands and business needs without wasting full-time expenditures or resources during the proper analysis to decide on what may be needed. The cloud provides means to turn up and down bandwidth, the resources and just a few clicks. With little thought into configuration of the resources, you can have the applications or infrastructure resources, do auto scaling depending upon thresholds that you define. Now, this flexibility of scale not only meets demands but can avoid costly procurement or potentially even worse, not enough bandwidth to support potential customers and money coming in the door.
On the security side of the things, we'll touch it upon here and maybe a couple of slides turns just a second as well. This one is an interesting topic as has been lately been the positive reason why businesses are moving to the cloud but can also be reason for hesitancy? I will talk a little bit more about security of CSPs in a couple of slides. But from a compliance and regulations standpoint, well, one of the biggest problems security officers have in the past is sensitive information being lost of a lost or stolen laptop. Not only the cost of the hardware itself, but more importantly the sensitive information that was stored on the device.
Incident reporting certifications is very costly and even if due diligence is proven, if not, fines can break the bank. Disaster recovery, it's always a good intention to most every business out there. For those with deep pockets, having geographically dispersed hot data centers with replicated data and resources can be an option. But instead, maybe pushing data up to the cloud be a very affordable option for all the other guys out there. Most of this piece have different tiers of data stores depending on service level agreements and how fast information would need to be recovered.
Not only is it much cheaper than traditional offsite storage, but your data can be replicated as to avoid any of the major geographic disasters. I mean, not to mention, who likes changing out tape media and shipping it to iron mountain or some other third-party vendor every week and keeping a log of those things and rotating them every Friday. I don't know about you guys. That wasn't very fun.
Document control. Document control is definitely one way that we mention very often, but just having your data inherently replicated throughout geographic locations, depending upon how you configure it can make your data available to all employees no matter where they're located, all with huge performance issues. Cloud storage can keep the one version of the truth and maintain versioning on each document.
How many of us, especially in the exchange of Lotus Notes admins out there love the idea that email is a document management system? In fact, Microsoft I believe announced back in 2010 they were going to drop the support for public folders by exchange 2016. But apparently, everyone went crazy about the idea in Microsoft as sense rescinded that statements since public folders were being used for documentaries by so many. Point being is email has been the de facto way of documents exchange and management and not a good one, I might add.
Cloud document management can facilitate actual efficient collaboration and better true vision into our business critical information. Now, this slide here we're talking today is mainly infrastructure as a service. Here we can leverage the cloud service providers in the computing resources, especially when it comes to installing GoAnywhere leveraging infrastructures of service and their associated storage options.
As you can see, yeah, well maybe not so clearly on that slide there, top line is for the software as a service. The middle is for infrastructure to service, and the bottom is for platform as a service. So they can see, although infrastructure to service is still second in terms of billion spent, the trend for leveraging infrastructure in the cloud is gaining fastest and popularity, mainly for all the reasons previously discussed.
So wouldn't we migrate then. So we just painted what seems to be a picture perfect solution in cloud service providers. So why wouldn't we move our infrastructure up to the cloud? Well, security still seems to be a big reason why most folks are leery of moving all their prize information up to the cloud. Over the past five years or so, we've had some breaches of large cloud-based providers from Adobe, Microsoft Windows, Azure, and even Amazon. But these breaches are not because of the inherent security inadequacies, but rather in either configuration issues or social engineering tactics, most notably phishing scams to compromise the system, again, foothold for further scanning.
I know that a lot of folks believe that if you have control of their own devices and equipment, they can better protect them and someone providing a convenience type service. Bottom line is that's the thinking our money under the mattress is more secure than the bank, which I suppose is debatable. But seriously, even though even more so now, security is such a hot topic. They remain competitive, and all CSPs must put and limit those resources into ensuring safety and security of their customer's data. Not only the reputation drives differ, but also so many regulations that are constantly coming out with the new compliance standards in the wake of all high profile breaches of late.
This is definitely in those sorts of innovation for the cloud service providers to make sure that they have the latest cipher suites algorithm, key exchange methods to provide customers the ability to make their data secure. The potential list may come from unsecure configurations of resources within cloud networks. But it is no different than the risks you run on-premises. At least at the CSP level, the infrastructure's provided for compliance regulations, and mandates are checked regularly. I'm not sure most organizations can honestly say the same thing as their home shops.
So in essence, these guys, the folks that are actually housing out the cloud types environment, they do have the resources. They do have the auditors coming in on a regular basis to check to make sure that their infrastructure is secure. They do have those types of resources do those things, whereas most organizations trying to do it on their own or on-prem to actually secure a "system" can make it very, very daunting.
This next slide kind of slipped in here. It's kind of hard to read but just a speaking topic on kind of thinking like a hacker. This was just one of the slides that we had for the statistics of any given breach, and I thought it was interesting. The ones on the top right in the darker color, those are kind of the cost savings because of what you're doing on the far left, instant response team, extensive use from encryption, employee training, things like that.
The one there at the bottom, I thought it was interesting to go to this one here is just looking at the extensive cloud migration. Now, it was noted in the [inaudible 00:11:10] Institute as well as the Verizon Data Breach Investigative Report that was mostly done when you were in the midst of doing an actual cloud migration, not when your data was actually out in the cloud. I just thought it was kind of interesting to point outside, threw it out there just for food for thought, I suppose.
What Cloud Capabilities Does GoAnywhere MFT Offer?
All right. So how does GoAnywhere fit into all of this? For now, we're leveraging the security flexibility, cost-effectiveness, disaster recovery, efficiency, and all the benefits of their infrastructure service models. For instance, we can install, GoAnywhere with Amazon Web Services Arena, either by spinning up EC2 instances using multiple flavors of Windows or Linux operating systems, or we have the developer preload instance or AMI the Windows server and Linux 2016 versions or multiple versions by searching the AWS marketplace. With just a few clicks, we can have GoAnywhere up and running, testing the point, which we'll kind of go through here in just a second.
In the same way, you can run GoAnywhere within Microsoft Azure by choosing a Windows or Linux resource and install an MFT in their cloud space. Again, we'll take a look at both environments here. Now, with those instance running on cloud resources, GoAnywhere can automate file transfers and data manipulation with ease strictly in the clouds place or between potential hybrid solutions. We're just trading partners and customers alike. Anything from offloading archive data for cheaper storage use, backups for potential disaster recovery or for the efficient collaboration and visibility for your entire organization, no matter where they're located without the effects of slow and expensive bandwidth limitations.
Now, most of the regulations require data encryption while in transit as well as at rest. Moving files to and from the cloud can be done via HTTPS as well as server-side encrypt and levering cloud managed KMS solution. Currently going inward does have the capability to natively connect up to AWS S3 buckets for that cheap and secure storage since our release of 5S6.0 as well as the ability to leverage blob storage within Microsoft Azure. All of these can be server-side AES 256-bit encryption, and that's going to be adhering to the NIS standards for not only encryption in transit using the HTTPS protocol, but also using those standards so that you're properly encrypting that data at rest.
Now, as always, all transactions within going everywhere, they're on-prem or in the cloud instances are audited by service protocol use, file activity, and web and avenues or activity. These logs can be viewed and segregated out log files via the GoAnywhere gooey, but also the absence of [inaudible 00:14:00] to essential SIS logs servers should you desire and have the ability to connect up to one.
Now here, this one here, not the most colorful in the world. We kind of went to black and green, it looks like. But this kind of gives you a real high level depiction of a common set up, and we're choosing AWS, I guess for sake of time here. Azure deployments, if you're familiar with both. A lot of the terminology and a lot of the actual architecture is going to be the exact same. But this is going through and showing you the top two boxes here.
Let me kind of get my little annotator quick here if I can. I apologize. We're new to the GoToMeeting. Just transitioned over here. So these top two boxes here... Nope, nevermind. All right. Maybe we won't annotate on this one, but the top two boxes at the top, starting from top to bottom, those are going to be your gateways. So those are going to be set up kind of in your public DMZ area. The bottom two boxes below those are going to be your MFT environment.
Now, the entire green square that we're looking at, that's your virtual private cloud. This is where I think it was your VPN, where all your infrastructure is going to be held within there. So everything within here is going to look very, very similar to what you have on-prem. You're going to have things within your enclosed environment. Your gateways are going to be sitting in your DMZ. One thing that we're not seeing here, and I apologize. Oh, here's my little pen here. We're going to have illustrated with this little guy here, we're going to have logical security groups or what we call network security groups within Amazon so that we can keep traffic only that's responsible or anything that we need to come into the DMZs and keep it separate from our backend private network here.
This is going to be very, very similar to you doing actual physical DMZ layer here and having gateway do what it does best, allows and brokers those connections within the private internal network without having to open up those internal ports as well as not having to stage files within the actual network. So some of the other things here, again, you'll also notice we do have availability zones. We have A as well as B. Just again, those that are familiar with AWS, what we're looking at here is we do have an active active cluster.
A couple of key things within AWS. You'll notice, just like on-prem, you have a responsibility to externalize your database. So that's what we're going to use the Amazon RDS service. In this case, it's going to be the MariaDB, that's externalized, the EFS file solution. These boxes are actually Linux boxes. So now we have our common network share, our common database, and now, we can go ahead and do an actual cluster in this instance here to increase that performance within here.
So this here, the reason why from the availability zones, if maybe you're thinking, "That seems kind of interesting for an active active." Because a true active active means if one goes down, one instance happens to go down, both of these gateways are going to know about both of these instances. So it's going to redirect traffic to the other one. Now, availability zones are technically geographic, different locations. But within AWS and Azure and things like that, the availability zones that they do, the latency is so low that they are able to do configurations like this. It's when you get to a different regions in AWS talk, and I apologize, drawn a blank on the Azure side, kind of how that works.
All right. One last thing. Let me see if I can erase these. Erase these little tools here, somewhere around here. Well, trying to erase these little buggers here. But in any case, we can go through and going to show you just real quick as far as the interface within AWS. There we go. Erase all drawings. I'll get there eventually. So here we can kind of go through and take a look at within... This is going to be the AWS console. So one of the things that we talked about, it really is the same as if you're standing up your virtual environment or if there are physical machines on your environment.
Well, what's nice too about the AWS as well as Azure is if you do navigate to the AWS marketplace. We do have windows and Linux AMI that are actually prebuilt out there for you. So you can just go to the AWS marketplace, click on that link there. Within here, now we can do a search and just type in GoAnywhere. Oops. I can spell, and those popups will... Oh, AWS marketplace. Let's get in the right area first, and those will actually pop up.
So as we see, we've got an MFT instance for Linux as well as for windows. This will get you those base installs. Then from there, it's very, very similar to what you see when you go through. You select your security group, the VPCs, all those types of things. Don't need to go through those things.
Similar for Microsoft Azure or Azure, I should say. At the very first kind of home screen here, we also have a marketplace down there as well. If you want to search for, again, GoAnywhere that'll pull up the different versions. You can always select... Doesn't look like it tells you the version here. But if you want to deselect and make sure you're getting the Linux version, you can kind of do that, and it'll let you know which version you're getting Linux or windows.
Again, just a quick way that we have those prebuilt versions of GoAnywhere so that you can get up and running launched in a secure cloud environment, whether you use an AWS or Azure in this instance. With that, I'm going to kind of pass the reigns over to Steve, and he's going to kind of dive a little bit more into what we've been developing and what the dev team has been developing on cloud connectors. So with further ado, Steve, give me a second. I'll pass you right.
Steve Luebbe: Okay. Thanks, Dan. Great job.
Dan Freeman: I think I did, hopefully.
Steve Luebbe: Yup, I believe so. Let me know if you can see my screen.
Dan Freeman: Yes, we can.
Cloud Connectors: What They Are and How to Use them
Steve Luebbe: Okay. Let me go ahead and say from current slide. There we go. All right. Thanks again, Dan. I'm going to be talking about cloud connectors. I do have a few slides to go through, and then the bulk of the remaining time I guess will be spent doing a live demo showing you cloud connectors in action. So let me page down here. Now, cloud connectors are a relatively new feature. It's something we added in the 5.7 release, which was towards the summer, this last summer. It offers out-of-the-box integration with popular applications like Salesforce, SharePoint, Dropbox, Google Drive, so forth.
Most of these cloud-based services do provide some type of restful or soap-based API. Then our cloud connectors and GoAnywhere reach out to them via web services to interact with those services. So with Salesforce, it might be working with accounts. With Dropbox, you're going to be working with file step or download and stuff. Now, we have I think about 22 on the marketplace today. One of the nice things about cloud connector technology is that you don't have to restart going anywhere to use new cloud connectors. So once we released cloud connectors, the functionality, then each individual cloud connector is an individual component that we publish to a marketplace, and you can download it as needed. So we have 22 currently in the marketplace. I'll show you some of those in a little bit.
We also have, let's see, about eight or so in the works. We are working on Azure data-like storage, several other Amazon AWS ones like CloudTrail, CloudWatch and ECS, and we're working on some bigger ones like SAP HANA and dynamics ERP. You can build your own cloud connectors with a drag and drop designer. If you are going to our customer, you're familiar probably with the project designer. I'll show you how you can create your own cloud connector, which is pretty cool, and you could submit it to us to publish on our marketplace.
Next slide. So how are customers using cloud connectors day? Well, the bulk of them are probably using it for file transfers. That's what we're seeing so far. We do have some working with it for CRM and other applications, but the bulk is moving files. Obviously, the most a use case of GoAnywhere is to move data. We specialize in that virtually to any file system. However, with services, it was always kind of difficult to interact with Dropbox or Box, and you could do it yourself. You could build a bunch of restful web service tasks. If you are a developer, you can figure out the JSON and how to authenticate and everything else, or you could just use the ones that we have out of the Box. We build these cloud connectors and publish them for just a small fee. So the bulk of our customers are using them to move files.
We also use it for Secure Forms. So with Secure Forms, you can build a user interface that prompts the user for certain data, and then that calls a project, and then that project can interact with the service. I'll show an example here later where you can submit support ticket information, calls a project, and then that project will submit a ticket to Jira. So kind of cool. We also have Avatara cloud connector which does disarming of files, basically removing malicious content. So I'll show you how we can scan files to remove content from a files and then create a kind of a scrub diversion, and then you can also create your own.
This picture here just kind of illustrates where cloud connectors fit into this. So projects are really the workflow definition and going where it defines all of your source data, where you want it to move them to, encryption, decryption, all that stuff. So projects kind of glue both the source and destination together. So then at the bottom, number three, you can use IBMI programs. You can kick it off via intranet sites or PHP or a command line actions or web services, ultimately calling a project, and then those projects can work with Box, Salesforce, Dropbox, and all the other cloud connectors that we have.
Okay. Then here's just a screenshot of the marketplace, which takes me into the [inaudible 00:25:08] the fun portion. Let's switch over to Chrome, and I get to get this dialogue out of the way. Just a sec here. There we go. Okay. So what you're seeing here is the dashboard to go on our MFT. I think my zoom is appropriate. Let me just make sure. So I'm going to zoom in just a little bit so you can see it better. Under the system menu we have a cloud connectors menu action that's available for project administrators. Project administrators are going to be kind of like the guide level access to work with the global settings and these cloud connectors.
Here you can see all the different cloud connectors that we have already installed. There's a difference between custom cloud connectors that you create or marketplace ones that we host for you. So you can see on the marketplace ones, there are different versions as we update them. If there was one at a date, let me scroll down here a little bit. There's a web docs cloud connector, and we can see that there's a new version of it. So you just click on update. It connects out to our marketplace, downloads the configuration file, updates it and you don't have to restart going to our MFT. So pretty cool technology.
If I scroll back up, go to add cloud connector. This is going to show our marketplace, and we're constantly adding new ones over time. We got, like I said, seven or eight currently in the works. So you'll see a few more published this week. At the top here, you can search for cloud connector based on name or I'll kind of just spend through here and illustrate some of them so you can see what they do. So we have quite a few with Amazon AWS. So with the EC2 connector, you can create instances. You can start and stop them and work with your EC2 servers out on Amazon.
You can also work with the serverless code functions lambda is what they call it. S&S and S&Q for kind of publishing messages and working with the Q. Some of the popular ones here are Box. We got quite a few working with that. So let's say you wanted to connect up to a Box users account, download a series of files and kind of zip them up and kind of archive them for just historical purposes, kind of make backups and stuff. You could. You can see that each one has individual price here. So this one's like 4.95. If you don't have it installed yet, you can easily click a button that just says free trial, which downloads it and puts it on your system.
All right. We have Google Translate. This one's kind of neat. If you had a website full of like HTML files, we can actually take your HTML files and going to pump them up to Google Translate and get them into different languages, which is neat. We have Jira. So if you have a Jira instance, whether that's a cloud or on-prem, you can work with it to create cases. I'll show an example of that here in a little bit. We have ShareFile, Trello. As you can see, there's just kind of... Kind of gets repetitive because there's so many of them.
But we have Viva CRM. We have Dropbox, see, GoAnywhere Command Connector. If you use GoAnywhere Commands, this is neat because it can add users, remove users, kickoff projects, do all sorts of stuff from GACD-like command line. But now you can kick those off from a project. That's maybe a little bit more intuitive. Other ones that we have, we have Google Cloud Storage, Google Drive, just quite a few, Jenkins Dynamics. Let's go ahead and show them off.
So once a cloud connector's installed, I'm going to show let's say Salesforce first. If I click on the cloud connector, you're going to see a list of actions. So with the CRM one, you're going to mainly be working with accounts, contacts contracts, cases, what not. So based on this cloud connector, I can go over to resources, and resources are a great way to define the connection information to your servers. So if it's going to be like an FTP server, SFTP or a cloud connector, most of them need some type of credentials to authenticate.
So you go to a resource, and you can say add cloud connector. You can see this drop down here. These are the cloud connectors that we have installed. If I scroll down in the list, there should be Salesforce, Salesforce connector. There we go and continue. It takes us to the add page where we can type in a name. So this would be our sales force cloud connector. It does require a URL, client ID secret and some other information. You can get that information from your Salesforce instance. So each one is going to prompt you for unique information. I'm going to go back to here, search for my Salesforce instance because we already defined this prior.
So we have this dev account that we have set up. The client ID, you want to authenticate with the client secret as well as the username, password, and security token. So Salesforce does require a little bit more information. Some of them are pretty simple, like just basic user password. Some of them are a little bit more complex. You can click on the test button. Basically, just test the resource to make sure that credentials are good, and then you have access to that server. So I'm going to say done.
Then from there, once you have your resources defined. So we'll just start off with Salesforce, but I'm going to show you the material Dropbox and a few others too. But then you'll go into projects. Now, projects are the workflow definition where you define your source, your destination, what do you want to do with the files, any parsing, encrypting, and so forth. So let's look at our Salesforce project that I set up.
Okay. I'm going to go into here. This is going to create an account and contact. So this is what we refer to as the project designer. There's multiple different kind of panes. On the left side, we have the component library. These are all the different actions that we can perform inside of our project. So if you wanted to search for, let's say SFTP, those are all the different actions for SFTP or just plain FTP, you could as well, or you can expand some of these different folders. So if you wanted to do a file transfer or maybe do a text message or a translation data, so forth, you just expand these different categories.
But at the top, there's a new category for cloud connectors. Under here is a listing of all the different ones that you have installed or your custom ones. For each one, you can expand it. So let's say Salesforce, expand it. From here, you can authenticate. You can add or update accounts. You can work with cases, contracts. The actions are pretty easy to kind of explain. But if you wanted to delete an account or something, you simply just drag it, put it over into the main module, or you can double click. So delete campaign. Double click adds it right to your project. Okay.
So let's go ahead and delete these two. Now, this project, it's pretty simple. I'm going to first authenticate. So keep in mind that all of the actions are defined inside the cloud connector. So the cloud connector exposed actions to authenticate and then work with the account and contact. So I'm going to say let's authenticate first to this Salesforce account. We're going to keep track of our authentication token. Most of these use auth tokens or some type of secret token values. So we're going to keep track of that and what we refer to as our auth token. We're going to pass that in in future actions. So we're going to say go ahead and use this auth token to this Salesforce instance. We want to add an account. Then on the account name, this is where you can specify any data.
Now, a lot of this data probably wouldn't be hard coded. It would be maybe something like a database value. So you'd have some type of value that maybe you're extracting from adjacent file or database or whatever you need to to work with it. But for now, I'm just going to simply hard coat it. So you have account name, and as you can see here, just a slew of different settings you can set on an account in Salesforce. But at the bottom here we're going to keep track of the account ID. So once we add an account to Salesforce, go ahead and refer to the account ID in the future. So like here, if I want to create a new contact for that account, so I'm going to say go ahead and add this user to this account, and then let's go ahead and execute this.
Okay. Takes just a second because my other tab up here, I have Salesforce currently authenticated. I don't see my cloud connector LLC test account. So once this runs, which did run successfully, if I view the job log, it's going to basically just illustrate that the Salesforce connector was able to authenticate, update account, and create the contact accordingly.
If I refresh, there's my new account. If I scroll down a little bit to the context section, I'm going to see my new contact added to that account. So that's a really simple example of showing how you can take something kind of complex because behind the scenes between going to MFT and Salesforce, there's a ton of JSON authentication and other values going back and forth. But to the end user, super simple to add accounts or work with files. The next one here is going to be Votiro.
So let's take a look at Votiro zero. I'm going to exit out of this project, and I've got quite a few projects here. So I'm going to just search or filter. Okay. If I click on edit there, takes me into Votiro. So this one down. Let's see, expand this section. We can check file status, download the file, get sanitation report, or mainly just sanitize and download file. So with Votiro, it's a service that allows you to scrub malicious contents from files. So if you want to send PDFs, or I don't know, word documents or whatever, it would scrub the malicious potential viruses out of them and then give you a clean version back.
On the sprint, we're just going to print out a report because Votiro actually gives us back a status report indicating the details of the scan. If I execute it. Now, for simplicity, I just dropped the file into this folder right afterwards right before this demo. But then I can see here that once I launched it, it didn't actually have the exe file. So all right. That's just showing another example.
Now, the bulk of our customers are doing it cloud connectors for uploading download files. So let's show Dropbox. All right. So Dropbox. We can create a workspace. This is just our typical workspace task. As you can see, cloud connectors do have a special cloud-like little icon here next to them. So we have a traditional task as well as the cloud connector. Cloud connector here is going to make directory. So we're going to connect up to our Dropbox instance. We're going to create a new folder. So I'm going to switch over to Firefox, go to Dropbox. As you can see, there's no new folder specified inside of here. Back over to Chrome.
I'm going to say, let's create this new folder, and then let's upload a file to it. So I'm going to take this audit log report, and I'm going to place it into that new folder just created. And then I'm going to connect that same Dropbox resource, pass in the file that I want to download and just download to the destination directory. This is just for quick illustration. Typically, this file would be placed on some other network or maybe sent off to an SFTP server or backed up or so forth. If I click on execute, it creates the directory, should upload it and download it and assuming everything worked. Go back over to Firefox, and you can see the new folder was just created. Click on this new folder, and this report was uploaded. So kind of cool.
Another one very similar that's also pretty popular is our SharePoint. So let's take a look at SharePoint. Yeah, and edit. Oops. SharePoint, it's a file system connector. So most of our file system connectors, they can upload, download, list directories, rename, delete and do your typical file actions. Most of those are going to be your 49 or 495 price tag. We also have the premium ones which are going to be 29.95. Those are for like CRM or ERP or the more elaborate type connectors.
But once you start working with a couple of file system ones, you'll see that they're kind of repetitive because this SharePoint one is also going to work with directories. So here we can authenticate to SharePoint, and then we're going to persist the session ID in the requests digest. So SharePoint actually their web service API is rather complex. So we have to keep track of two different variable types and we're going to pass that into each request after this to authenticate with that same session. So we're going to say, persist the session to this SharePoint server, and we're going to create a new folder, and we're going to upload the same file, basically, to this folder in SharePoint.
So execute this. Switch over to SharePoint. This is my SharePoint folder. I'm going to refresh. So let's go back to documents. There we go. They got this little icon next to the new folder so you can see that it was recently created. Click here, and then a few seconds ago, this file was uploaded. So pretty simple, but you kind of get in the point. Now, for cloud connectors, let me illustrate how you can create your own if you wanted to. So over here on the cloud connector management page, I can say add cloud connector, and let's create a new connector versus downloading one from the marketplace.
Let's say weather service. The weather service requires maybe a user and password to authenticate. So we're going to say text field, oops, text field, and also a password. This is going to be password. Required password is going to be the value that we're going to pass into the project, and then we need a user. So let's give the user a variable name and require, let's say yes, yes, password, yes. This isn't going to actually work, but I'm just kind of illustrating it here.
So this custom cloud connector has user and password that we're going to prompt and the resource, and then we can have different actions. So let's say get weather, and then this action is going to get called anytime the user drags and drops that into the project designer. From here, then it becomes a series of rest tasks. You might say rest, post. You need to post information to that service. For now, I'm going to just going to delete this because it's not going to actually work functionally, and I'm going to prompt them for one more variable. I'm going to say text field, get weather. On this text field, oops, it's going to be the zip code. Zip code.
All right. So you're kind of getting the idea of how you would build out these definitions. The resource test is what happens when you actually define it as a resource and click the test button. So if I go to resources and if I added that weather service, so if you were to build your own connector to maybe a different popular application, you would have that inside of your cloud connector definition, and then you can build a resource for it, and it's going to prompt you for whatever is defined. So here I prompted them for a user and a password, and oops, sorry, I think I saved that and click test.
It actually execute the resource tests. I can save and close that resource. Then under projects, if I could add a new one for the weather service under cloud connectors, there should be one here. Yep. There it is. Weather service. Get weather. So whatever action is defined becomes available to the designer and get weather is going to prompt me for the resource which has your credentials to connect up to the system as well as the zip code, which we can pass in some type of the zip code to check the weather.
That's just kind of illustrating how a cloud connector is built. If you build your own cloud connector, please submit them to sales and support. We'll work with you on that and possibly be able to get you published in our marketplace. It was designed so that each one can be published, and you might even be able to get some kickbacks, which would be pretty nice. All right. So that's a custom one.
The last example that I'm going to show you here is a little bit more elaborate. It's kind of like an actual use case of submitting a support ticket. So I'm going to go under the services menu and show off secure forms. So under secure forms, I have this custom form. If you haven't built these before, they interface with projects. They kind of give it a gooey front end where you can build custom fields that get passed into a project that the project can then use to submit tickets or whatever it needs to. So here's the form name. On the project tab, this is the project we're going to call when the secure form is submitted. So we got this juror project, which is going to submit a ticket to Jira. We have the user to authenticate as.
Now, on the access tab, this is how you want to access the form, and you can have it publicly available. You can remove public access and make it only authenticated for certain users. So if I give out this URL here, I'm going to copy this link, and went over to, let's say Firefox and new tab and clicked on that. There we go. So it's showing my custom form that I built. Back on the admin side, let me explain some of these fields, I'm also going to give them access to this specific user. In a component, this is where you can customize the screen.
So submit support Jira ticket. Let's change the title of it. You can customize the instructions with whatever you want it to here. Then as far as fields are concerned, on the left side, you can add different components. So if you wanted to add another text field to the screen, let's go ahead and select that there and we can say my custom... Oops, custom field, and then the label is label, whatever. You can see here that it kind of shows you what that form will look like and stuff.
But ultimately, this designer, once you save it and publish it out there, it's going to give a form that end users can fill out. So I'm going to go back over here. Now, each one of these fields is going to pass a variable to a project. So let's look at subject here. So I'm going to say take the subject. This variable is called description. This variable's called name. We have attachments which are actually uploading files to the form, and then those files get passed into the project because when somebody submits a support ticket, I want to optionally allow them to attach files that maybe are screenshots or log files or whatever they need to.
So here is the attachments, drag and drop kind of file area. I'm going to cancel all this and show you the project. All right. Over the projects, and then let's see. Jira is the one I defined for this. So a Jira cloud connector gives you actions for, let me expand that. You can add attachments. You can add comments. You can add votes, watchers. If you're familiar with Jira, you're probably going to see these actions and kind of get excited because there's a lot of... We work with comments and deleting issues and moving issues and transitioning and so forth. But I'm going to do a simple action just to create a new one.
So I'm going to say connect up to our sample Jira instance. We have a sample project with the project key of SAM. Our subject is going to be passed into us from the user. Our description is going to be passed in from the user. We're also going to append this to say it was reported by whoever that that user was. Then we have the issue type key, which is a story. This can be customized based on your JIRA instance.
All right. Now, at the bottom here, we have issue key, which is going to be our unique Jira ticket. Now, if the secure form has files, we want to go ahead and add attachment. So we're going to do the add attachment action to the Jira cloud connector, and we're going to pass in the Jira key or issue key for Jira that we want to associate the file to. So then we're going to... In the attachment field, we're going to say pass in the file, which may be a screenshot or a log or whatever it may be, and attach it to that Jira case.
We're going to take it a step further. If the user provides a phone number, we're also going to subscribe them to a notification list. We're going to use our Amazon SNS, which is simple notification service to publish a message to their phone, and the subject's going to be support case, and we're going to give them the issue key that we created and we'll just notify them that basically, we'll keep them updated. On secure forms, you can build a custom response. So we're going to say your support ticket was submitted successfully. Please refer to your issue key in future communication.
Okay. So this is just the project definition, and we got the secure form. Let's go back to the web client. I'm going to go ahead and log in here. Oops. Okay. What you're seeing here, this is the 6.0 beta version of GoAnywhere MFT. So the web client might look a little bit different if you haven't seen this before. But on the left side here, we've got forms or available forms, and then this is going to be that form that I created to submit the support ticket. Click on that.
Takes me into here, which my subject is going to be this webinar is awesome. The description is going to be whatever issue we are facing. Then your name. Let's go ahead and submit my name. Phone number, we'll leave that blank for now. But you could submit a phone number if you wanted to get a text message. Then once you attach a file, you can drag and drop just from your desktop or you can use the uploader there. Once I submit this, it's going to call it project. That project is going to create a Jira ticket with attachment and information. Well, it should. So we'll see. Live demo is always fun.
Okay, there we go. It ran successfully because they got the response of the JIRA ticket number. So it actually connected to JIRA, created the ticket, returned back the issue ID and then told the end user, here's your ticket for future reference. If I go over to our JIRA instance, and let's say refresh, there you go. This webinar's awesome. Click on that case. I can see whatever issue are facing. We have my name that was appended to the description as well as the attachment uploaded to JIRA with that same case number. So kind of cool. Just kind of illustrates the full cycle of what you can do.
Let's see. I think that kind of was the last example I was going to show off. I don't know what kind of questions we have out there, but maybe I can address some of those before we switch gears. Brooke, do you have any questions that I should address to the group?
Brooke: Yeah. A lot have been answered already. One that came in on clarification. The AWS AMIs, do those include both the gateway and MFT?
Steve Luebbe: The AMI is published on the marketplace. Those are only for going around MFT. So with the AWS and Azure marketplaces, we publish going to an MFT, AMIs, and stuff, but not going to gateway.
Brooke: Got it. All right. Then we got a couple of questions just around what cloud connectors are coming out. Can you give us any sneak peek ones that are in development now?
Steve Luebbe: Sure. Let me switch over because I got a list somewhere. Yeah. Because I made a list here. Azure Data Lake storage, that is very close. We're also working on Amazon AWS CloudTrail, CloudWatch, and ECS. So CloudTrail's for logging, and the CloudWatch is kind of like your budgeting, and then ECS is for your container service for like Docker containers and stuff. We're also working on SAP HANA as well as Dynamics 365 ERP. So we've got about seven that are in the works to be published within the next couple of weeks. That's in addition to the 22 that we offer today.
Brooke: Awesome. One more question that just came in. Can GoAnywhere MFT be hosted on Google Cloud?
Steve Luebbe: Yeah. Yeah. There's no problem with that. I know a couple of customers have talked about it. I've never actually worked with them directly. But yeah, it should be fine. So GoAnywhere MFT really just friends on any Windows or Linux platform and most cloud providers, whether it's Google Azure or Amazon support your typical Windows and Linux environments. Amazon has their own Amazon special flavor of Linux, which kind of optimizes some of the network configurations on it. We support that as well. It's pretty much a standard Linux system as far as going where it's concerned.
Brooke: Great. You mentioned the cost for cloud connectors. Someone just wanted to confirm, is that a one-time payment?
Steve Luebbe: Yeah. There is a maintenance. It's perpetual. I think Brian can kind of chime in on that one, but yeah, it is just a one time payment. Let me pull up the marketplace here. So 495 would be just a one-time fee for some of those. You can see the pricing list in here. Most of them are 495. The only other ones would be Jira because that has a ton of actions, a ton of things you can do with it and our Salesforce and our CRM type connectors.
Brooke: Awesome. Steve, if you want to go back to the PowerPoint, I can go through the last two slides, and we can let people weigh in with any other questions they have. We can answer a few more. All right. So before we do drop off, if anyone has had their questions answered and isn't able to stick around, just want to make sure everyone knows we do have other webinars in this series available on our website, and you can just type in that URL at the bottom of the screen to access those. So lots of good topics, lots of good demos, just like this one on. Make sure you check it out.
Brooke: Then next slide, just in terms of next steps, if you liked what you saw today, we do have more full custom demo available on our website, and you can just go to goanywhere.com/demo. If you're interested in seeing more of our cloud functionality or talking through cloud connectors at more length, you can just make a note on that form when you submit it. Then that next slide too also has our contact information too. If you have any questions that didn't get covered today or you want to talk to a sales rep in more detail, you certainly can.
Brooke: Great. So if you're not able to stick around for more questions, thanks for joining, and we hope you have a really good day. For those of you who are still with us, let me peek in at the questions we are getting. Steve, I know you're popping in here and answering a few. Are there any you want to answer verbally that maybe you already answered for one person but might be good for the group?
Steve Luebbe: Sure. When this came through not too long ago about Salesforce connector working with custom objects, I thought that was kind of an interesting one because we recently published a new version of the Salesforce connector that supports custom objects. So most objects are like accounts, contacts, cases, and so forth. But we do support custom objects as well in Salesforce.
Brooke: Awesome. Let's see here.
Steve Luebbe: Oh, we have one about migrating licenses between environments. Yes, we do support that. So if they wanted to move an on-prem copy over to a cloud-based environment, they can. We have a question about file size limits, which is we don't really have any limits built in. The only limits would be imposed by the service. So some of the services may have a limit, like maybe I think Amazon S3 buckets have like a five gig limit per file. So the limits that we would have are based on the service that we're connecting to, not built in to GoAnywhere.
Let's see, what else do we have that are good for the group? Oh, we have one asking about Votiro definitions being updated, how often that happens for data sanitizing. That is their service that they take care of. We can definitely put you in touch with the Votiro people that are kind of our liaisons to work on those type of questions. We just interface with them. So I'm not exactly sure how often their definitions are updated. Yeah. That looks like a lot of the general ones.
Brooke: Steve, do you want to go to the next slide just so people can see that contact information from us?
Steve Luebbe: Yeah, for sure.
Brooke: Perfect. All right. Well, it looks like most of the questions have come in, and we've gotten to them. But like we said in that demo, or sorry, the webinar questionnaire that's going to pop up, feel free to add any more questions that you had for us. Reach out at the contact info on the screen if you want to get in touch. Thank you guys for joining. Thank you, Steve and Dan, for presenting. Really appreciate it. All right. Have a great day everyone. Bye-bye.
Dan Freeman: Sure. Bye.