Infrastructure & Domain
Included in the FastEditor service is the setup, maintenance, and updating of all infrastructure required to run your white label. This ensures a fast and safe user experience.
All of our infrastructure is hosted at Amazon Web Services and is constantly updated with the latest improvements in the software. You will be provided with a staging and a production environment.
The staging environment is there to try product configurations and settings before they make it to production. Once configured on the staging environment and approved, these changes can be synced to the production environment, which is the environment your customers will be visiting.
Environments
The different environments will be available at the following locations:
Staging Environment
Web app: {{your_brand}}.staging.fasteditor.com
API domain: api.{{your_brand}}.staging.fasteditor.com
Order Fulfillment domain: fulfillment.staging.fasteditor.com
Production Environment
There are two locations your labelled version of the software can run:
https://{{your_brand}}.fasteditor.com – This is provided out of the box <https://subdomain.yourdomain.com> – This is recommended to build trust with customers and provides maximum brand value.
Custom Domain
To use your custom domain you will need to create a CNAME record within your DNS provider's administration panel and configure it to point to FastEditor.
When you create the record, the CNAME host will be your new subdomain (i.e. fasteditor.yourdomain.com) and the CNAME value will be {{your_brand}}.fasteditor.com
SSL Certificate
We will request and manage the SSL certificate for your subdomain. These certificates are issued by Amazon Web Services. In case you want to use your own issued SSL certificate please contact your account manager.
Security
FastEditor has implemented many industry best practices to make sure the infrastructure is safe and reliable:
- Each label and environment is hosted in a completely isolated AWS account.
- All critical resources are running in a Virtual Private Cloud (VPC) and cannot be accessed from outside that VPC.
- Our infrastructure is constantly monitored by AWS GuardDuty on suspicious behaviour.
- We setup a wide range of CloudWatch monitors to scan resource performance and utilization.
- We have extensive escalation policies for incident management
- We have implemented the principle of least privilege and are enforcing separation of duties within the development team.