Skip to main content
Druva Documentation

How to recreate or update CloudFormation stack for a CloudRanger account

 

This article applies to:

  • Product edition: CloudRanger

Overview

This article provides the steps to recreate or update a CloudFormation stack if it has been incorrectly updated/removed/deleted either inadverntently or deliberately.

Create CloudFormation stack

  1. Update the CloudFormation stack from the AWS console as follows:
    1. From the CloudRanger application, go to your Account Settings and in the AWS Access section, click Configure.

      CreateAWSAccessRole1.png
    2. On the CREATE AWS ACCESS ROLE page, click COPY TO CLIPBOARD. The link to the CloudFormation script gets copied to the clipboard.
    3. Navigate to the CloudFormation from the AWS console click the stack you had created earlier for your CloudRanger credentials.
    4. Update the existing stack using the steps provided under Making updates to existing AWS credentials in  CloudRanger.
    5. If the update fails and you are stuck, contact Druva Support.
  2. Recreate the CloudFormation stack in case it was deleted.  This process is similar to creating your AWS access credentials when you initially set up your CloudRanger account. 
    1. From the CloudRanger application, go to your Account Settings and click Configure in the AWS  Access section. 

      AWSAccess.png
    2. Copy the URL.

      CreateAWSAccessRole1.png
    3. Click Create Stack.
    4. Copy the URL into the field under Specify an Amazon  S3 template URL and click Next.

      UpdateLocalTestCrossAcct.png
    5. On the Specify Details page click Next.

      SpecifyDetails.png
    6. Instead of stack name as ‘localtestcrossacct’ we can keep it to something like : ‘cloudranger-<Account:ID> to segregate CR accounts if you have multiple CR accounts in place i.e.
    7. Rename the default stack name to some thing like cloudranger-<Account:ID> to segregate CR accounts if you have multiple CR accounts configured.

      CreateStack.png
    8. Select the checkbox labeled I acknowledge that AWS CloudFormation might create  IAM resources with custom names.
    9. Click Create to generate a CloudFormation stack.

Complications

This section provides the troubleshooting steps for complications that may cause failure in CloudFormation stack:

Create_Failed - AWS:S3:Bucket
Create_Failed - AWS:IAM:ManagedPolicy

Complications.png

Causes

  • The CF stack has S3 bucket already associated with it ( created by old CF stack ).
  • The CF stack has IAM Policy associated with it, which was created by old CF stack ( which has been deleted ).

Resolution

Perform the following preliminary steps before deleting the concerned IAM Policy and S3 bucket associated with it:

  1. If S3 bucket is empty, delete it.
  2. If S3 storage has data, copy the data to another temporary bucket as follows:
    1. Create a new temporary bucket.
    2. Copy the data from the S3 bucket to the temporary bucket.
    3. Delete the S3 bucket.
    4. Again run the CF script. This again creates a new S3 bucket.
    5. Copy the data from the temp bucket into the newly created S3 bucket.