Confluence stack not able to generate backup using Atlassian Backup Machine

Enrique_7hi58t

Hi community,

We are using Atlassian Backup Machine (https://community.atlassian.com/t5/Data-Center-articles/Introducing-Atlassian-CloudFormation-Backup-Machine/ba-p/881556\) to perform backups/snapshots in our Confluence 6.15.2 stacks defined by AWS Cloudformation template (https://github.com/aws-quickstart/quickstart-atlassian-confluence\).

When backmac runs I'm getting the following error in DB nested stack:

An error occurred (ValidationError) when calling the DescribeStackResource operation: Resource ElasticFileSystem does not exist for stack conf-pr205-DB-xxxxxxxxxxxxx-MySQLDatabase-xxxxxxxxxxxxx: ClientError
Traceback (most recent call last):
File "/var/task/backmac_mount_efs.py", line 54, in lambda_handler
efs_id = backmac_utils.get_stack_resource_id(stack_name, 'ElasticFileSystem')
File "/opt/python/backmac_utils.py", line 50, in get_stack_resource_id
LogicalResourceId=logical_id, StackName=stack_name
File "/var/runtime/botocore/client.py", line 357, in _api_call
return self._make_api_call(operation_name, kwargs)
File "/var/runtime/botocore/client.py", line 661, in _make_api_call
raise error_class(parsed_response, operation_name)
botocore.exceptions.ClientError: An error occurred (ValidationError) when calling the DescribeStackResource operation: Resource ElasticFileSystem does not exist for stack conf-pr205-DB-xxxxxxxxxxxxx-MySQLDatabase-xxxxxxxxxxxxx

For some reason is complaining that mysql nested stack is not having a EFS, but that nested stack don't need one, EFS is defined at a root stack level.

Any suggestions/hints would be appreciated

 

BaM

Hi Enrique.

The "Atlassian CloudFormation Backup Machine" is an Atlassian Labs style tool provided without support and "as is".

It was not built to work with the AWS Quickstart style demo stacks, but with the templates that are closer to those we use for our internal Production stacks (at https://bitbucket.org/atlassian/atlassian-aws-deployment/src/master/templates/) .. These templates do not have nested stacks.

For any Confluence built with the "ConfluenceDataCenter.template.yaml" in that repo, Backmac would work and allow you to then use the "ConfluenceDataCenterClone.template.yaml" in the same repo to create clones for other environments (stg/dev) or DR instances of your Confluence.