Using AWS Secrets Manager with Amazon RDS and AWS Fargate - Clean Up Phase
If you are at an AWS event where the Event Engine is being used, you are done! Clean up is handled automatically.
Click here if you are using your own account or at an AWS event and Event Engine is not being used.
Now that you have seen how AWS Secrets Manager can rotate the credentials for a private database and with AWS Fargate, please follow these steps to remove the resources you created, including the private database.
If you do not have a session open to the bastion host, then connect to the bastion host using AWS Systems Manager Session Manager. To do this:
- Go to the Systems Manager console.
- Click Session Manager.
- Click Start session.
- Select the radio button for the instance associated with the bastion host.
- Click Start session.
The scripts you will be using are owned by the ec2-user account. If you are not currently using ec2-user as your effective user id, then enter the command below to change your effective user id and directory to those of ec2-user:
sudo su - ec2-user
Run the command below to perform the Fargate clean up tasks.
The command will stop any Fargate Tasks, ungregister task definitions, and delete the Amazon ECS cluster and the Amazon ECR repository. The output will be similar to that shown in the figure below.
Delete the secret you created in Secrets Manager. When you go to the Secrets Manager console, you should check the region and make sure you are operating in the region in which the CloudFormation stack was deployed. Also when you delete a secret in the console, the deletion is scheduled for a minimum of seven days in the future.
When you enabled rotation on your secret, AWS Secrets Manager used AWS CloudFormation on your behalf to create an AWS Lambda function to do the rotation using the AWS Serverless Application Repository. Delete the CloudFormation stack whose name begins with the following string:
Look for a stack with this naming convention that was created at about the same time as you enabled rotation. Do not proceed to the next step until this stack has been deleted. The stack deletion process may take as much as one hour because of Lambda-related network activity.
Delete the main CloudFormation stack. The name of the stack is the name you chose during the Build Phase. The stack deletion process may take several minutes to complete. If the stack deletion process either pauses or fails, it may be because of an Elastic Network Interface that gets created when rotation is enabled. In this case, delete the Elastic Network Interface and try deleting the CloudFormation stack again.