Cloud infrastructure project
The Adobe Commerce on cloud infrastructure project includes all code in Git branches, associated environments, and scripts to deploy the Commerce application. Environments contain services to support the Commerce application, including a database, web server, and caching server.
Adobe provides a Cloud Console and developer tools to fully manage all aspects of your project. You, as the account owner, have full access to all environments.
Cloud Console
The Cloud Console provides interactive methods to build, manage, and deploy Commerce code in a user-friendly format. Log in to the Cloud Console to view your project list. You can only see projects that you have permission to access as an admin or for specific environment types. If you are an Adobe Solutions Partner, you may see multiple projects for clients that you support.
The All projects view lists all projects that you have permission to access. You can click Show filters and filter your project list by type, region, or plan.
Project overview
Selecting a project from the All projects list opens the project overview. The project overview always displays a project navigation bar, which includes an environment selector and a configuration button:
The project overview, as long as you do not have an environment selected, shows a summary of project details in the preview area:
- Project name
- Region, Project ID
- Plan, allotted storage, environments, users
- Storefront URL with Set a custom domain button
And in the main project overview:
-
Environments view shows a list or tree view of
img-md w-32 (active) and
img-md w-32 (inactive) environments.
-
Activity stream shows running, pending, and recent activities for the project.
For Starter projects, there is a hierarchy of branches starting from master
(Production). Any branch that you create display as children from the master
branch. Adobe recommends creating a staging
branch, then create an integration
branch for development. See Starter architecture.
For Pro, there is a hierarchy of branches starting from production
to staging
to integration
. The
icon indicates that the branch deploys to a dedicated environment. Any branches that you create display as children of the integration
branch. See Pro architecture.
Environment overview
Selecting an environment from the project navigation bar changes the overview and the navigation bar to focus on the selected environment. The navigation bar includes branch controls (Branch, Merge, and Sync) and a configuration button:
The environment overview shows a summary of environment details in the preview area:
- Environment name, type
- Region, Project ID
- Date and time of last activity, including backup
- HTTP access and search engine status
- Machine name assigned to environment
- Environment status (Active or Inactive)
- Storefront URL with Set a custom domain button
And in the main environment overview:
- Activity stream makes up the main environment overview and shows running, pending, and recent activities for the selected environment.
- Backups tab provides a list of stored backups, history of backup actions, and the Backup button.
Access storefront
Each active environment has a storefront. Select an environment from the top navigation and click the URL in the environment overview. Also, there is a URLs list on the right-hand side above the Activity list.
The Web Access URL may include the following:
https://<branch>-<unique-ID>-<project-ID>.<region>.magentosite.cloud/
- Unique ID = 7 random alpha-numeric characters
- Project ID = 13-character project ID
- Region = AWS or Azure region name, see Regional IP addresses
The Pro Production and Staging environments include three nodes that you can access using the following links:
-
Load balancer URLs:
http[s]://<your-domain>.c.<project-ID>.ent.magento.cloud
http[s]://<your-staging-domain>.c.<project-ID>.ent.magento.cloud
-
Direct access to one of the three redundant servers:
http[s]://<your-domain>.{1|2|3}.<project-ID>.ent.magento.cloud
http[s]://<your-staging-domain>.{1|2|3}.<project-ID>.ent.magento.cloud
The production URL is used by the content delivery network (CDN).
Settings
Open the Settings panel by clicking the
(configure) icon on the right side of the project navigation.
Project settings
Project Settings expands a menu of project-level controls to manage users, variables, and more:
Environment settings
Click Environments and select a specific environment from the list for controls to manage site settings, environment variables, and more:
Toggle different environment settings:
active
or inactive
. Most of your work is in an active environment. You can deactivate or delete the environment.Fastly and New Relic credentials
Your project includes Fastly and New Relic. The project details display information for your project plan and important licenses and tokens for these integrations. Only the License Owner has initial access to the credentials and services. Provide these credentials to technical and developer resources as needed.
-
Fastly provides content delivery (CDN), image optimization, and security services (DDoS and WAF) for your Adobe Commerce on cloud infrastructure projects. See Get Fastly credentials.
-
New Relic provides application metrics and performance information for Staging and Production environments.
Use the Cloud CLI to review your integration tokens, IDs, and more:
magento-cloud subscription:info services