Avahi Service Delivery Removal
Thank you for using Avahi's managed services. Follow these steps to cleanly remove
the Avahi Service Delivery automation tools and IAM roles from your AWS account.
Before You Begin
⚠️ Important Notice
Removing the Avahi Service Delivery stack will delete the cross-account IAM roles that
Avahi uses to manage your AWS workload. Ensure that any active services or automations
are no longer needed before proceeding.
Removal Steps
-
Open AWS Console:
Navigate to the AWS CloudFormation console in your web browser. Make sure you're logged
in as an administrator with permissions to delete CloudFormation stacks.
https://console.aws.amazon.com/cloudformation
-
Locate the Avahi Stack:
In the CloudFormation console, look for the stack named:
avahi-admin-access
-
Review Stack Resources:
Click on the stack name to view its details. Review the Resources
tab to see what will be deleted. This stack contains:
- IAM Role: AvahiAdminAccess
- IAM Policies attached to the role
- Trust relationship with Avahi's AWS account
-
Delete the Stack:
Select the stack and click the Delete button.
Confirm the deletion when prompted. CloudFormation will automatically remove all
resources created by this stack.
-
Monitor Deletion Progress:
The deletion process typically takes 1-3 minutes. You can monitor the progress in the
Events tab. The stack status will show
DELETE_IN_PROGRESS and eventually
DELETE_COMPLETE.
-
Verify Removal:
Once deleted, verify that the IAM role
AvahiAdminAccess
is no longer present in your IAM roles list.
https://console.aws.amazon.com/iam/home#/roles
Alternative: Using AWS CLI
If you prefer to use the command line, you can delete the stack with the AWS CLI:
# List stacks to verify
aws cloudformation list-stacks --stack-status-filter CREATE_COMPLETE UPDATE_COMPLETE
# Delete the Avahi stack
aws cloudformation delete-stack --stack-name avahi-admin-access
# Monitor deletion progress
aws cloudformation describe-stacks --stack-name avahi-admin-access
Troubleshooting
Stack Deletion Failed?
If the stack fails to delete, it's usually because of resource dependencies or
permission issues. Check the Events tab in CloudFormation for specific error messages.
Common issues include:
- IAM roles still in use by other AWS services
- Insufficient permissions to delete IAM resources
- Stack termination protection enabled (disable it first)
If you need additional resources removed or encounter issues, please contact Avahi support
for assistance.
Need Help?
If you have questions or need assistance with the offboarding process,
our team is here to help.