Getting started with the Spryker Cloud Commerce OSEdit on GitHub
This document is a starting point of development with the Spryker Cloud Commerce OS(SCCOS).
SCCOS is a fully-managed solution. Before you start developing, we set up environments, tools, and services based on your Onboarding Questionnaire. If you didn’t request something in the questionnaire, you can always do it via support.
After the initial setup, the following is configured and available:
- Environments: staging and production
- Services: RDS database, RDS backup, logs, SMTP, etc.
- Access to AWS, internal resources and services
- CD pipelines for staging and production environments
- Domain names and SSL certificates
You can access SCCOS via:
- IAM account - provides access to AWS Management Console. See Accessing AWS Management Console for more details.
- SSH - provides access to internal services via bastion host. See Connecting to services via SSH for more details.
- VPN - provides access to internal services via bastion host. We provide the access details during the onboarding.
- SFTP - provides access to the SFTP folder mounted inside the Jenkins container.
For security purposes, VPN and SSH access are available only for the IP addresses in the security group. Provide your public IPs via support to get the access. Additionally, for SSH access, provide your public SSH keys.
If you didn’t request SFTP access for the initial setup, you can request it via support later.
The following CD pipelines are configured in CodePipeline:
|DESTRUCTIVE||You can configure the installation stage of this pipeline in
|NORMAL||You can configure the installation stage of this pipeline in
|Build||Compiles images and pushes them into the Amazon Elastic Container Registry. Starts automatically when a new commit is detected.|
|Rollout Scheduler||Deploys the scheduler.|