Magento Enterprise Cloud Edition requirements

This topic lists requirements for using Magento Enterprise Cloud Edition. Review them carefully before you start developing.

Prerequisites

Following are requirements you should already have:

Magento Enterprise Cloud Edition does not support the split database performance solution at this time.

Required testing configurations

Before you test any custom code in your local Magento Enterprise Cloud Edition environment, you must do all of the following:

Development and testing

For development and testing, we require the following:

  • You must push code to the staging or production environment before the database is uploaded the first time
  • You should test using either the integration or the staging environment (or both) on a regular basis throughout the project

    You can enable and test individual features or extensions on different environments to make sure they are working before merging

  • You must make sure that magento setup:install and magento setup:upgrade work and that any extensions and customizations compile correctly in production mode
  • You must test the application, including any extensions and customizations, against Varnish and/or Fastly well in advance of going live

    In particular, verify that content is being cached as expected

  • You must make sure the Fastly VCL is uploaded to Fastly
  • You must make sure that the Fastly SSL certificate is setup for your domain(s)
  • If you have any custom deploy hooks in integration, open a Support ticket to have them added to the staging and production deployment process
  • You should profile key flows and customizations using Blackfire.io

Before you go live

Before you go live, you must:

  • Review our documentation about going live
  • Schedule the Go Live Preparation call with the support team
  • Adjust DNS TTL in advance
  • Change the default Magento Admin password
  • Optimize all images for the web
  • Enable minification for JS, CSS, and HTTP
  • Make sure that pages are being correctly cached in the page cache and Fastly

    • Make sure the Fastly Extension is up-to-date
    • Make sure the Fastly VCL is up-to-date
  • Make sure that the Fastly SSL certificate is setup for your domain(s)