You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
NB: Atlassian Cloudformation Forge has been renamed to Atlassian Labs DC Weaver
Atlassian Labs DC Weaver is a tool for the creation and administration of CloudFormation stacks of Atlassian products, for users without physical access to the underlying AWS services.
The IT Platform Engineering team at Atlassian built this tool internally, to allow product teams to manage their own instances of Confluence, Jira, and Crowd without having access to the AWS console itself.
Weaver can manage Cloudformation deployments of Jira Data Center, Confluence Data Center and Crowd Data Center.
Actions are split into three categories: Stack Actions, Node Management, and Application Management.
These are actions that are performed against a Cloudformation stack of an Atlassian product.
These are actions that are performed against an EC2 node, or all the EC2 nodes in the Cloudformation stack.
These are actions that are performed against Jira/Confluence/Crowd.
Weaver can be downloaded here: https://bitbucket.org/atlassian/atl-labs-dc-weaver/src
Weaver is deployed using the Cloudformation template in the Weaver repository.
The template creates:
Weaver currently stores configuration parameters in:
These are downloaded from S3, to persist settings across Weaver deployments. Once the files have been modified locally, you can upload them to S3 using the AWS CLI, eg:
aws s3 cp weaver/saml_auth/permissions.json s3://atl-labs-dc-weaver-<your-aws-account-id>/config/permissions.json
These will then be downloaded and applied to any new Weaver instance deployed in that AWS account.
We have enabled simple Google analytics to get an idea of how many people are using Weaver.
Analytics can be disabled in the Cloudformation template. If analytics are disabled after Weaver is created, spin down to 0 nodes using the template and back up to 1 to apply the change.
Weaver can use SAML authentication to define who can perform which actions, on which instances, in which regions.
For more information on how to enable SAML in Weaver, see: https://community.atlassian.com/t5/Data-Center-articles/Enabling-SAML-in-Atlassian-Labs-Data-Center-Weaver/ba-p/1781426
Weaver works with AWS Cloudformation templates. It automatically deploys the (now deprecated) public templates: https://bitbucket.org/atlassian/atlassian-aws-deployment/src/master/
These can be used as a reference, but they are no longer supported.
Weaver can be used with the Atlassian Quickstart templates, or these can be used as a reference to build your own templates.
You can deploy your own templates to Weaver by specifying the repository which contains the templates, in the Cloudformation template used to deploy Weaver.
Atlassian Labs DC Weaver is not supported by Atlassian. It is provided as is.
More detailed information about Weaver (previously called Forge), and migrating to AWS CloudFormation in general, is provided in this video.
Denise Unterwurzacher [Atlassian]