Forge: using custom CloudFormation templates

Cross Product Knowledge

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

You can now use your own custom CloudFormation templates in Forge, along with the Atlassian provided templates.

Configuring your template repository

You can host your repository anywhere, so long as it can be accessed over SSH by the Forge server.

Repositories should contain the following nested folders:

-repository-root
	-templates
		-product-name (eg 'confluence' or 'jira')

Template files should be YAML (JSON is not supported).

Filenames should contain the product name, and end in .yaml, eg 'MyConfluenceTemplate.yaml'.

Clone templates should specify 'Clone' in the filename, eg 'MyConfluenceCloneTemplate.yaml'.

Enabling your custom templates

  1. Clone the latest Forge source code.
  2. Update your Forge stack with the new template.
  3. Enter your template repository in the format 'git@bitbucket.org:atlassian/custom-templates.git'.
  4. If your custom template repository is private, provide a AWS Systems Manager Parameter Store key name that holds an ssh private key that can access the repository.

  5. Select 0 Forge nodes, so your current node is destroyed, and Update.

  6. Once the update is complete, update the stack again and select 1 Forge node. This will create a new Forge server with your custom templates.
Last modified on Sep 18, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.