Skip to main content

How can we help you?

Druva Documentation

How to create or update the CloudFormation stack

 

Overview

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

Update CloudFormation stack

Update the CloudFormation stack from the AWS console as follows:

  1. Log into the CloudRanger console, and navigate to your Account Settings.

    CF1.png

     
  2. Under AWS Access section click Configure, and copy the CloudFormation URL.

    Update2.png

    For step-by-step instructions on CloudFormation, you may click help me with Cloudformation.
     
  3. Login to your AWS Console and navigate to the CloudFormation page.

    Update3.png
  4. Select the stack that you previously created when configuring CloudRanger, and then click Update.

    Update4.png
     
  5. On the Specify template page, select Replace current template. Then paste the CloudFormation URL into the Amazon S3 URL text box. Click Next.

    Update5.png
     
  6. Click Next on the Specify stack details and Configure stack options pages.
    You will be able to preview the changes before you click Update stack to confirm the CloudFormation changes to resources.

    Update6.png
     
  7. Once the stack update is complete, navigate back to CloudRanger and click Save under Save AWS Access Role.

    Your IAM role and AWS account access should now be updated with the latest permissions, allowing you to take advantage of any new functionality that is released.

Troubleshooting

This section provides the troubleshooting steps for any unexpected issues that may cause failure in the CloudFormation stack:

Create_Failed - AWS:S3:Bucket
Create_Failed - AWS:IAM:ManagedPolicy
Create_Failed - CRFileLevelSearchBucket
ROLLBACK_IN_PROGRESS - CloudRanger-Access

Update9.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 an 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 the 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.