AWS OpsWorks is a configuration management service that provides managed instances of Chef and Puppet.
N/A
DocuSign
Score 8.7 out of 10
N/A
DocuSign supports transactions with document sharing and electronic signature, as well as automated and guided data collection and entry, record updating across disparate systems and payment collection upon agreement, as well as analytics and reporting.
Where you already have some Chef recipes to build your application boxes and are happy to run directly on VMs, OpsWorks really shines. It won't do anything too complex for you, so it only really works well for simple stacks (load balancers, application layers, database layers). If you want to do more complex infrastructure, Cloudformation or Terraform are probably worth looking at.
This product is well suited in the use case that I provided before: when it comes to onboarding employees and providing a clear channel for decision making for human resources, this is an excellent tool to accomplish that. I would say the weak points is when you have back and forth communication with users that it might seem a little redundant to have that back and forth communication in that scenario.
Getting up and running with OpsWorks is a very technical and potentially time-consuming process. You need to know the ins and outs of Chef/Puppet if you really want to get into it and there isn't a convenient way to test out the environment locally so debugging can be time-consuming.
To take advantage of some of the newer AWS instance types you need to be running on a VPC, which again is a pain if you don't have a DevOps team.
The error logs and monitoring metrics in OpsWorks are pretty basic and haven't changed much over the years.
Tracking, particularly when collecting signatures through connected applications, such as an ATS, is not always clean or easily traceable.
Formatting documents to handle electronic signature types (signatures, initials, etc.) is not always easy, and highly dependent on the partner's technology.
It is not convenient to have to use DocuSign as a stand alone product if the signatures are required for 3rd party applications. It definitely excels on its own, but the scope of that usage, at least for us, is slim.
I can't imagine doing business without DocuSign now. I would never want to go back to the way we used to do things. The "new way" is "the way" is "the right way." We can honestly be proud of a "one right way" process and not have to suffer through "5 ways for 5 days."
Generally user-friendly once you have command of the basics, but also has a lot of nuances that can make it difficult to train others on. DocuSign University is a helpful tool, but understandably a lot of content to get through to become a well-versed user. A lot of different functionalities but only a few I use on a weekly basis.
Unless you pay for a pricey support package getting support on OpsWorks will be pretty slow. Documentation is also relatively limited and sometimes hard to follow when compared to competitors. Generally, we've been able to get the answers we need from OpsWorks support when we run into problems but don't expect rapid responses.
I'd give them a 10, but there has been 1 or 2 small cases that seemed to fall to the wayside, but I was able to call them up and get them resolved. We were having a bad implementation night (after midnight) and we needed assistance from Docusign. They were able to get an engineer to help us in the early morning hours
Docusign is super easy to use, and apart from a few administration details, there was really nothing to train on. Post implementation, there were issues with configuration of auto-filled documents with the integrating 3rd party. That training required some time, because the DocuSign expert took the time to walk me through the 3rd party's configuration (how often does that happen?) so I could see how DocuSign should be best used to overcome weaknesses in the 3rd party platform. 10/10 expert care.
Until you get the hang of it, I recommend doing several internal tests before sending a document to a client. As I mentioned earlier, you have to go through a bit of trial and error at first to verify that the workflow works as expected.
OpsWorks isn't really a direct competitor to Terraform/Cloudformation, but it does allow you to do some of the more simple things on offer quite quickly and effectively. Opsworks was used for this reason, along with existing internal knowledge of Chef. Along with some of the other services on offer from AWS, it is good to use as a stepping stone along the way when building your systems - or perhaps it would be entirely suitable for a fairly simple project.
There has never been anything that we could really compare to Docusign. We have tried sending documents in a PDF version, but that was not nearly as efficient. DocuSign saves your signature in the system and uses that as it goes through your documents.