Docker Compose Installation to AWS

1. Make sure you have an AWS account.

2. Open the AWS CloudFormation service in the AWS Management Console.

3. Click Create stack.

4. In Prepare template, select Template is ready.

5. In Template source, select Amazon S3 URL and specify the URL: https://on-premises-assets-eu-west-1.s3.eu-west-1.amazonaws.com/2024.2.2/aws-cfn-template.json

6. Click Next and specify the stack name and other parameters:

   Stack name	(Required) The name of the stack for your SpaceCode instance.
   AdminEmail	(Required) The email address of the SpaceCode administrator.
   AdminUsername	(Required) Administrator username.
   AdminPassword	(Required) Administrator password.
   HostedZoneName	The DNS name of an existing Amazon Route 53 hosted zone where you want to host your SpaceCode instance, for example, mycompany.com If you don't have a hosted zone, you can: Leave this parameter empty. In this case, the template will generate a URL for your SpaceCode instance automatically using the nip.io service. Note that HTTPS is not available for the auto-generated URLs. Register a new domain name in the Amazon Route 53 service. By default, when creating a domain, AWS will create a corresponding hosted zone for it. The hosted zone name is equal to the domain name.
   Size	(Optional) The size of the provided resources. Possible values are: Small: (Default) A t4g.xlarge instance for the main application and a db.t4g.medium instance for the database. 50GB of allocated storage for the database. Medium: A t4g.xlarge instance for the main application and a db.t4g.large instance for the database. 100GB of allocated storage for the database. Large: A t4g.2xlarge instance for the main application and a db.t4g.large instance for the database. 200GB of allocated storage for the database. See details about the T4g instances in the official AWS documentation.

7. Click Next.

8. Do not change any other options on all following pages and just skip them by clicking Next.

9. Before clicking Submit, make sure to select I acknowledge that AWS CloudFormation might create IAM resources. This is required as the template creates IAM roles for the SpaceCode instance.

10. AWS CloudFormation will start creating a stack with SpaceCode On-Premises. This may take a while. After your stack is created, you can see the SpaceCode URL on the stack's Outputs tab.

11. Perform post-installation administration activities:

    • Activate your SpaceCode On-Premises instance.

    • If you want to use SpaceCode on mobile clients, configure push notifications.

    • If you want to enable mail notifications in SpaceCode, configure the mail server. Note that your SpaceCode instance comes without a mail server. If you don't have an existing mail server, you can create one using the Amazon Simple Email Service.

1. Open the AWS CloudFormation service in the AWS Management Console.

2. Open the stack with SpaceCode On-Premises.

3. Click Update and change the required parameters.

   Note that you cannot change the AdminEmail, AdminUsername, and AdminPassword parameters once the stack is created. Even if you update the corresponding values, they will not be applied.

4. Do not change any other options and click Next.

5. Click Submit.

To back up your SpaceCode On-Premises instance

1. Create a backup of your SpaceCode data:

   1. Open your SpaceCode On-Premises instance in a browser.

   2. On the main menu, click Administration and choose Database Backups.

   3. Click Create backup.

2. Create a backup of your AWS CloudFormation stack.

   AWS lets you create on-demand backups or schedule them. Follow the official Amazon recommendations.

   As a result, you will get a composite backup that consists of:

   • A backup of your stack configuration.

   • A backup of S3 buckets that store the SpaceCode data backup you created in step 1.

To restore your SpaceCode On-Premises instance

1. Open your AWS account.

2. Open the AWS Backup console, then Protected resources.

3. In Recovery points, find your composite backup and unfold it.

4. Select the backup with the CloudFormation configuration. You can find this backup by the CloudFormation value in the Resource type column.

5. Click Restore. During the restore, you will be asked to provide the same settings you provided during the installation. After the restore is complete, you will get a new stack with a clean SpaceCode On-Premises instance.

6. Return to the Protected resources page and select the backup with the SpaceCode database. You can find this backup by the spacebucket word in its ID, for example, my-onprem-instance-spacebucket-1bdai-29239793114334-a04ca4e3.

7. Click Restore. During the restore, provide the following settings:

   • In Restore type, choose Restore entire bucket.

   • In Restore destination, choose Use existing bucket.

   • In Bucket name, choose the bucket created for your restored SpaceCode On-Premises instance. The bucket contains the spacebucket word in its ID, for example, my-restored-instance-spacebucket-n0ulpds2xcks.

   Wait until the restore is complete.

8. Return to the Protected resources page and in the same way as before, restore all other backups:

   • SpaceCode Packages backup: contains the packagesbucket word in its ID.

   • VCS backup: contains the vcssbucket word in its ID.

   • Automation backups: contain the automation word in their IDs.

9. In a browser, open the Database Backups page of your restored SpaceCode On-Premises instance, for example, https://my-instance.url/manage/db-backups

   Important: If you open the index page of your instance, you will be asked to provide your SpaceCode license key. Do not do this! Your license key is already stored in the database backup.

10. On the Database Backups page, click Restore next to the available backup.