Running a service on your customer’s AWS account has many aspects. We needed to learn to handle: security, privacy, cost, billing, and more.
In this session, we will touch on each of these topics and more, presenting our road map to a production level SaaS, and the lessons we learned along the way.
In the beginning, it may look like a trivial thing. All you need is remote access via SSH and credentials to your customer's AWS account. As you start developing the service you’ll understand there are many small details you need to take into consideration.
Security: The level of security needed is much higher. As a traditional SaaS service, you need to be concerned about someone stealing information from your servers, but in this case, your servers now have credentials to your customer’s AWS account, leaving them vulnerable as well. You need to be not only concerned with your own managed data but also other applications that may be running on your customer’s account.
How do you protect your own data? While running a service on your servers you can put sensitive information on them such as your SMTP username for sending emails, tokens for 3rd party services, etc. Now that you will be running on your customer servers, customers can potentially have access to them as well.
While running on your customer’s AWS account have the benefit of appealing to a new range of customers it also has a lot of aspects that need to be considered. We will cover the one we had to handle.
Running SaaS on your Customer’s AWS Account
Full Talk (40 Minutes)
Food & Swag Sponsors
Learn more about each of our Event Sponsors.