Disconnecting Your AWS Accounts

Jul 29, 2024

Disconnecting Your AWS Accounts

The following process outlines the steps necessary to remove Cloudsaver resources that were deployed in your AWS environment during the accounts connection period.

Requirements

The following are requirements for using the account removal tool:

StackSet names must have the following format: Cloudsaver-StackSet
Stack names must have the following format: Cloudsaver-<AWSAccountID>
- Example: Cloudsaver-123456789101

Disconnect Process

Navigate to Settings > Connections: This will bring up all accounts linked to the Cloudsaver platform.
Use the filter function to show all connected accounts:
1. Choose Field: Connected
2. Operator: is
3. Select the “Connected” check box
4. Apply the filter settings
For the accounts you wish to disconnect, navigate to the account list and select the trash can icon located to the right of the account.

Background Processes

Once an account is selected to be disconnected, the following changes will be made in your AWS environment:

The Cost and Usage Report (CUR) and CUR Bucket created when your accounts were connected will be deleted.
1. Typically, you can find the CUR Bucket labeled as: Cloudsaver-<accountID>-Billing-Files
The EventBridge connection and all rules created will be terminated.
CloudFormation Stacks and StackSets are deleted.
IAM roles and policies are deleted.

Customer Data Managed By CloudSaver

Cloudsaver will remove your account completely from the Cloudsaver application as well as any resources associated with the account. This also includes secondary accounts.

Frequently Asked Questions

Q. If I receive an error code while the disconnect process is running, will the entire process stop?

A. No. The process will continue to run even if an error code is received.

Q. If I didn’t create my CloudFormation Stacks and StackSets with the required naming convention, can I still use this tool?

A. No. The naming conventions for Stacks and StackSets must match those listed in the requirements.

Q. I ran the disconnect tool but StackSet shells still remain.

A. You will need to manually delete any StackSets not deleted by the tool.

Q. How do I disconnect accounts if I cannot run this tool?

A. You will need to manually delete all CloudFormation Stacks and StackSets on the accounts you wish to disconnect. It is also advised that you verify that IAM roles are also removed.

In this article

Disconnecting Your AWS Accounts
Requirements
Disconnect Process
Background Processes
Customer Data Managed By CloudSaver
Frequently Asked Questions

FEATURE	BENEFIT
Tag Automation & Batch Tag Processing	Employ powerful automation to quickly and accurately tag cloud resources minimizing manual tasks and saving valuable time and effort. Reduce security vulnerabilities and human errors with accurate and swift tagging.
Real-time, Native Cloud Sync	Tag changes are reflected in real-time in native cloud service provider environments. Data is timely and accurate and can be leveraged with additional CloudSaver and third-party tools.
Tag Explorer Query Engine	Utilize our patented filtering and search technology for rapid and efficient location of client data across resources, zones, accounts, and service providers. This capability drastically reduces mean-time-to-resolution by quickly identifying key cloud data. Its deep dive, robust exploration enables you to “find anything.”
Tag Intelligence Dashboards & Tools	Benefit from a guided tag health experience that automatically delivers valuable insights without the need for customized reports or dashboards. These insights cover both your entire tag environment and also specific categories.
Customizable Dashboards	Create customized dashboards to display data according to your specific needs, offering real-time visibility into cloud resources, tags and spend. Obtain timely, accurate, and relevant data for insightful analysis and to identify tagging gaps.
Efficient Tag Remediation	Benefit from suggested, spell-checked tag keys and values – detect and batch merge tag variations.
Legacy Tagging Solutions	Retroactively tag or modify tags on existing legacy resources during cloud migration, either individually or in bulk and eliminate time-consuming manual efforts for smooth integration into your cloud environment.
Multi-Tenant & Multi-Cloud	Manage every cloud data set from a single screen across resources, zones, accounts, and cloud service providers (AWS and Azure).
Tag Policy Compliance Monitoring	Ingest tag policies from native cloud environments to ensure consistent tag syntax and taxonomy.
User Role & Permission Console	Enhance security with Identity and Access Management features contained in the permissions assigned through tagging.
Configuration Management Database (CMDB) Integration	The CloudSaver platform seamlessly incorporates CMDB data related to known cloud infrastructure, offering precise control, efficient tagging, and enhanced visibility by viewing, filtering, and sorting cloud resources based on CMDB data.