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 Project Web Interface and developer tools to fully manage all aspects of your project. You, as the account owner, have full access to all environments.
The Project Web Interface provides features to create, manage, and deploy code in Integration, Staging, and Production environments for Starter and Pro plans.
To access your projects and environments:
The View Project Page link displays for Account Owners only. If you are not an Account Owner, go to the user login instead.
If you do not see any projects, you must contact the Account Owner or Super User associated with the project and request access.
When you log in to the Project Web interface, you see your accessible projects. As an Account Owner, you can only see projects for your company. An Adobe Solutions Partner may see multiple projects for clients that they support. Click on a project to see a hierarchy of environments.
For Starter projects, there is a hierarchy of branches starting from
master (Production). Any branches you create display as children from the
master branch. Adobe recommends creating a staging branch, then branching from
staging for your Integration development. See Starter architecture.
For Pro, there is a hierarchy of branches starting from Production to Staging to Integration. The icon indicates that these branches deploy to a dedicated server, used by Staging and Production. Any branches you create display as children from Integration. See Pro architecture.
To access an environment store and admin, select a branch and click Access Site. A list of store URLs and SSH command display. Select the URL to view the store in that environment.
The Web Access URL may include the following:
The Pro Production and Staging environments include three nodes that you can access using the following links:
Load balancer URLs:
Direct access to one of the three redundant servers:
The production URL is used by the content delivery network (CDN).
If you have inactive Git branches of code, you can toggle displaying the branches in the hierarchy.
Click configure icon to display users and deploy keys and variables associated with the project. You can modify access and permissions across the entire project. See Manage user access.
You can set the following configuration options for each project:
|Users||Manage user access to project using roles and environments types. See Manage user access.|
|Domains||Add a domain name to the project. See Manage domains.|
|Certificates||View a list of the SSL certificates associated with the project.|
|Deploy Key||Add and view the public key to the project code repository.|
|Variables||Add project-level variables that are available at build and runtime in all environments. See Variable levels.|
You can manage variables and settings for Production, Staging, and Integration environments through this interface, configuration files, or with CLI commands. Select an environment in the environment list and click Configure environment to update the settings, add variables, routes, and users.
You can set the following configuration options for each environment:
|Settings||Toggle different environment settings:|
|Status: An environment can be
|Outgoing emails: Setting this option to
|Indexing by search engines: Setting this option to
|HTTP access control: Setting this option to
|Variables||View, create, and manage environment variables available for the environment at runtime. See Variable levels.|
|Routes||View a list of configured routes. See Configure routes.|
|Users||View a list of users granted environment level access. It is best to Manage users with the CLI.|
DO NOT use the HTTP access control method for securing Pro Staging and Production environments. This breaks Fastly caching. Instead, use the Blocking feature available in the Fastly CDN for Adobe Commerce.
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.
To review your integration tokens, IDs, and more:
Log in to your account
In the upper right corner, click your name and Account settings.
On the Projects tab, click View Details for your project to open general settings and plan details.
On your project details page, scroll to and expand the New Relic and Fastly sections to review service credentials.