When you have completed deployment and testing in Integration and Staging environments, you can begin site launch preparation. First, you should complete all development and testing before working in the Production environment. Feel ready to launch? Review our checklists, best practices, and final steps to launch your site.
If you checked this information before deploying and testing in Staging, consider reviewing the benefits of testing in Staging first in the next section. Staging is a near-production environment running on similar hardware, configurations, architecture, and services. It can reduce your downtime and make your extension, service, custom configurations, and merchant User Acceptance Testing vital components to releasing your sites and stores.
Why test fully in Integration, Staging, and Production?
We strongly recommend testing in the Integration, Staging, and Production environments due to the complexity of ensuring that your custom code, themes, extensions, and third-party integrations all work together to operate your stores. The following are common issues you can discover and resolve when you complete testing in the Integration and Staging environments before updating your Production environment:
Staging supports all Production services, features, database data, technology stack, architecture, and more. It mirrors Production, which means if errors occur in Staging, you have a warning before they occur in Production.
Code that works in your local integration environment might not work in Staging and Production environments.
Integration environments do not support some services that are available in Staging and Production, like Fastly and New Relic.
Fully test your site with a variety of tools in Staging for load, stress, performance, and site assets.
Because Integration environments may only have databases populated with test data, not matching a production-like environment, you might find additional errors or unexpected behavior when testing in Staging or Production environments.
Prerequisites for site launch
You need the following information and resources to prepare for site launch:
- CNAME record information for configuring the DNS
- List of all storefront domains to add to the certificate
- SSL/TLS certificate
As part of Adobe Commerce on cloud infrastructure subscription, Adobe provides a Domain-Validated SSL/TLS certificate issued by Let’s Encrypt. Each Pro Production, Staging, and Starter Production (
master) environment has a unique certificate that covers all domains and subdomains in that environment. These certificates are provisioned and uploaded to your site automatically after you update your DNS configuration for development and production. See Provision SSL/TLS certificates.
If you want to deploy your own Extended Validation SSL certificate for your company instead of using the Let’s Encrypt certificate, contact your CTA or submit a Support ticket.
Set up the Security Scan Tool
The security scan tool uses the following public IP addresses:
1 2 3 184.108.40.206 220.127.116.11 18.104.22.168
You must add these IP addresses to an allowlist in your network firewall rules to allow the tool to scan your site. The tool posts requests to ports 80 and 443 only.
The Security Scan Tool enables you to regularly monitor your store websites and receive updates for known security risks, malware, and out-of-date software. This is a free service available for all implementations and versions of Adobe Commerce on cloud infrastructure. You access the tool through your Commerce Marketplace account.
- Monitor your sites security status and applied security updates
- Receive security updates and site-specific notifications
See the User Guide for information about setting up and using the security scan tool. Typically, you start using this tool when you begin user acceptance testing (UAT).
Each site you scan must be registered through the Security Scan tab. During the registration process, you must accept the disclaimer before you can begin scanning. You control both the schedule and authorizing the user to receive notifications when each scan is complete. You can schedule scans for a specific, recurring date and time, or run a scan on demand as needed.
The Security Scan Tool uses several user agent strings to simulate real-life malware activity. You might see the following user agents in your analytics or access logs:
1 2 3 4 Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0 GuzzleHttp/6.3.3 curl/7.29.0 PHP/7.1.18 Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/37.0.2062.120 Safari/537.36 Visbot/2.0 (+http://www.visvo.com/en/webmasters.jsp;email@example.com)
Scan your site
To scan your site:
- Access your Commerce Marketplace account.
- Click the Security Scan tab and select Go to Security Scan.
- In the Actions column for the site, select Run Scan. A notification status displays the scheduled scan.
To review the report:
- When the report completes, a notification displays.
- In the site row, select the report you want to view from the Reports column. The order is latest to oldest.
The report lists issues including Failed Scans, Unidentified Results, and Successful Scans. Each entry provides detailed information for the scan, a list of issues to investigate, and actions to take. Some of these actions may require downloading and installing security patches. You can add those to a development branch on your local workstation.
Scan results include a label that describes scan pass or fail status with detailed information about the checks performed:
- “Failed” indicates that the website contains a serious vulnerability.
- “Unidentified” suggests that a deeper review is required by your team or hosting provider to determine if further action is required.
The scan results also provide suggested remediation steps for each failed security test. Security scan results are protected and viewable only by the registered user. Only users designated in the site registration process receive scan completion notifications.
Ready to launch your site
When you are ready to begin the site launch process, see the following: