Uninstalling the blueprint

prerequesties before uninstalling hosty blueprint, you need to destroy the eks clusters created by it (how to) make sure that hosty cli is properly configured and tofu plan doesn't display any possible changes to the infrastructure preparation steps temporary user uninstalling hosty entails deleting all the iam users created by the hosty this includes all the iam users with administrator access, one of which you are most likely currently using in order for the operation to finish successfully, you need to create and use a temporary iam user with admin access visit the iam users page on aws console and click create user button set any username (i e org temp ) check provide user access to the aws management console checkbox and configure console password section as nedded (autopassord or custom password, etc ) click next button on the set permissions page, set permissions options to attach policies directly select administratoraccess in permission policies section click next button then create user button logout from current iam user and sign in as the temporary user go to security credentials page and in the access keys section click create access key button select other for use case and click next button set description tag value to anything (i e hosty) and click create access key button in the hosty cli execute rm /src/ aws/credentials to remove currently used credentails then execute aws configure profile=hosty user then copy and paste access key and secret access key from the previous step iam users iam users created by hosty, that were actively used will contain login profiles (aws console access), mfa and access keys those must be deleted prior to executing terraform command to avoid failure terraform state hosty stores the terraform (tofu) state in aws s3 bucket and and uses aws dynamodb table to manage state locks as we are planning to destroy these resources, we must move to the local state management open main tf file and comment out terraform resource block execute tofu init migrate state and follow the instructions once successfully completed visit dynamodb tables page on aws console select the tf remote state lock table, click actions , then select turn off deletion protection s3 buckets terraform wouldn't delete the s3 buckets stored objects within those buckets this is an intended behavior to prevent data loss if you have successfully backed up objects in the s3 buckets and no longer need them, you can empty s3 buckets via aws console prior to uninstalling hosty blueprint uninstall hosty blueprint to uninstall the hosty blueprint execute tofu destroy , this will perform planning and show you number of resources to be destroyed confirm by typing yes and pressing enter key cleanup after successfully uninstalling hosty, you can log into aws console using the root user and remove the temporary iam user