Magento

Sign in to the AWS Management Console, open the EC2 service, and select Launch instance. Under Application and OS Images, choose AWS Marketplace AMIs and search for Magento Open Source. Select the SecureAnyCloud listing and choose Select, then Continue on the subscription summary.

Pick an instance type of m5.large or larger. Magento is a heavy stack, with PHP, MariaDB and OpenSearch running side by side. Choose your EC2 key pair under Key pair (login).

Under Network settings, select your VPC and subnet. Create or select a security group that allows inbound port 22 from your management network and inbound ports 80 and 443 from the networks your shoppers use. Leave the root volume at the default size or larger.

Select Launch instance. First-boot initialisation takes approximately two minutes after the instance state becomes Running and the status checks pass. The longest step is the cache:flush that Magento runs after rotating the database password on first boot.

The following command launches an instance from the SecureAnyCloud Magento Marketplace AMI into an existing subnet and security group. Replace the values in angle brackets as follows:

• Replace <ami-id> with the AMI ID shown on the Marketplace listing.
• Replace <key-name> with your EC2 key pair name.
• Replace <subnet-id> with your subnet ID.
• Replace <security-group-id> with a security group that opens ports 22, 80 and 443 as described above.

aws ec2 run-instances \
  --image-id <ami-id> \
  --instance-type m5.large \
  --key-name <key-name> \
  --subnet-id <subnet-id> \
  --security-group-ids <security-group-id> \
  --block-device-mappings '[{"DeviceName":"/dev/sda1","Ebs":{"VolumeSize":30,"VolumeType":"gp3"}}]' \
  --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=magento-store-01}]'

On success, the command prints a JSON document. Note the instance ID. Once the instance is running, retrieve its public address with aws ec2 describe-instances --instance-ids <instance-id> --query "Reservations[].Instances[].PublicIpAddress" --output text.

Connect over SSH with the key pair you selected and the public IP address from step 2. The SSH login user depends on the operating system of the AMI variant you launched. For Magento Open Source 2.4 on Ubuntu 24.04, the login user is ubuntu.

The first-boot service rotates credentials and reconfigures Magento before Apache accepts customer requests. The credentials file is therefore always in place when you log in for the first time.

ssh <login-user>@<public-ip>
sudo cat /root/magento-credentials.txt

The file is plain text. It contains the storefront URL, the administrator URL (which is /admin), the administrator username (admin), the administrator password, and the MariaDB database name, user and password. Copy these values somewhere secure, such as a password manager or encrypted vault. Do not commit them to source control.

From the same SSH session, confirm that the deployment is healthy:

HOST=$(sudo awk -F/ '/^magento.storefront.url=/ {print $3; exit}' /root/magento-credentials.txt)
curl -fsS -o /dev/null -w 'storefront HTTP %{http_code}\n' -H "Host: ${HOST}" http://127.0.0.1/

A storefront HTTP 200 response confirms that the full stack (Apache, PHP, MariaDB and OpenSearch) is serving Magento.

Open a web browser and navigate to the storefront URL from the credentials file. Magento shows the Luma demo theme home page to anonymous visitors.

Navigate to /admin. The administrator URL is also in the credentials file. Magento shows the administrator sign-in form.

Enter the administrator username (admin) and the administrator password from /root/magento-credentials.txt. Select Sign in. On a fresh deployment, Adobe shows a one-time usage data collection prompt. Select Don't Allow unless your organisation has opted in.

After you sign in, the Magento administrator opens at the Dashboard. The dark left rail gives you every management area:

• Dashboard for the home overview
• Sales for orders and invoices
• Catalog for products and categories
• Customers for shoppers
• Marketing for promotions and email
• Content for storefront pages and blocks
• Reports for analytics and lifecycle reports
• Stores for store configuration, multi-store setup and tax
• System for permissions, integrations and import/export

The footer of every admin page shows the Magento version number.

On a fresh install, a yellow banner at the top of the dashboard reminds you to refresh the Configuration cache. Navigate to System, then Cache Management. Tick Configuration, choose Refresh from the action dropdown, and select Submit.

For a production deployment, rotate the administrator password that first boot generated. Choose your account in the top right corner, then choose Account Setting. Enter your current password and set a new password in the Password and Password Confirmation fields. Select Save Account.

Select Catalog, then Products in the left rail. Magento opens the Products grid, which is empty on a fresh install.

Choose Add Product and select a product type (Simple, Configurable, Grouped, Virtual, Bundle or Downloadable). Magento opens the product editor with sections for the product name, SKU, price, quantity, attributes, images, related products, search engine optimisation and storefront visibility.

Enter the basic fields, set Enable Product to Yes and set Stock Status to In Stock. Then select Save. Magento reindexes the product into the OpenSearch catalog automatically, and your product appears on the storefront within a minute.

Magento ships unconfigured for payment and shipping. Configure them under Stores, then Configuration:

• Sales, then Tax: set the merchant origin country and add tax rules and rates for the jurisdictions you sell into.
• Sales, then Shipping Methods: enable a flat rate or table rate shipping method, or integrate with a carrier provider such as UPS or FedEx.
• Sales, then Payment Methods: enable a built-in payment method such as Check / Money Order for testing, or install a payment integration extension for a card processor such as Stripe, Braintree or PayPal.

After every Configuration change, Magento prompts you to refresh the Configuration cache. Use System, then Cache Management.

The image ships with the Luma sample theme, so the storefront has a real layout and example category pages out of the box. Replace it for production:

• Install a third-party theme with Composer by running cd /var/www/magento && sudo -u www-data composer require <vendor>/<theme-package>. Then enable it under Content, then Design, then Configuration.
• Or build a custom theme by creating app/design/frontend/<Vendor>/<theme> and registering it.

Manage CMS content (the home page, About Us and the static blocks down the homepage) under Content, then Pages and Content, then Blocks. Replace the default sample content before launch.

For any production Magento deployment, serve the storefront and admin over HTTPS. Admin sessions, customer login cookies and payment form data must not be exposed to interception. The image ships with Apache, which certbot can configure automatically.

The following steps assume that you have a DNS record pointing your fully qualified domain name at the instance's public IP address.

sudo apt-get update && sudo apt-get install -y certbot python3-certbot-apache
sudo certbot --apache -d shop.your-domain.example \
  --non-interactive --agree-tos -m you@your-domain.example \
  --redirect

After certbot finishes, update Magento's secure base URL to the new HTTPS endpoint:

sudo -u www-data /var/www/magento/bin/magento config:set web/secure/base_url 'https://shop.your-domain.example/'
sudo -u www-data /var/www/magento/bin/magento config:set web/secure/use_in_frontend 1
sudo -u www-data /var/www/magento/bin/magento config:set web/secure/use_in_adminhtml 1
sudo -u www-data /var/www/magento/bin/magento cache:flush

Magento has three data sources that you must back up together:

• The MariaDB database
• The Magento code tree (/var/www/magento), including Composer dependencies, app/etc/env.php and uploaded media under pub/media
• The OpenSearch indices, which bin/magento indexer:reindex rebuilds if they are lost

sudo mysqldump --single-transaction magento > /var/backups/magento-db-$(date +%F).sql
sudo tar --acls --xattrs -czf /var/backups/magento-files-$(date +%F).tgz -C /var/www magento

Ship both backup files to an Amazon S3 bucket or another object store.

The Magento cron entry installed with the image runs every minute. It dispatches indexer reindexing, mail dispatch, order lifecycle hooks and other scheduled jobs.

For kernel and package updates, Ubuntu's unattended-upgrades is enabled by default, so security patches apply automatically. To update Magento itself, use Composer. Run cd /var/www/magento && sudo -u www-data composer update --no-dev, followed by sudo -u www-data bin/magento setup:upgrade && sudo -u www-data bin/magento setup:di:compile && sudo -u www-data bin/magento setup:static-content:deploy -f && sudo -u www-data bin/magento cache:flush.

For larger deployments, decouple Magento from the single-instance pattern:

• Move MariaDB to Amazon RDS for MariaDB and update db.connection.default in /var/www/magento/app/etc/env.php
• Put the Magento web tier behind an Application Load Balancer and scale horizontally with an Auto Scaling group, with pub/media on Amazon EFS shared storage
• Move OpenSearch to Amazon OpenSearch Service and update the search engine configuration under Stores, then Configuration, then Catalog, then Catalog, then Catalog Search
• Offload session and full page cache to Amazon ElastiCache for Redis by setting the cache.frontend.default.backend and session.save keys in env.php
• Push static assets to Amazon CloudFront in front of pub/static and pub/media

The Adobe Commerce Operations guide documents each of these steps at https://experienceleague.adobe.com/docs/commerce-operations/.