Skip to content

Commit

Permalink
fix tags page
Browse files Browse the repository at this point in the history
  • Loading branch information
ana-cozma committed Jun 30, 2024
1 parent d1bfaeb commit 0991e21
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 2 deletions.
3 changes: 2 additions & 1 deletion config/_default/params.toml
Original file line number Diff line number Diff line change
Expand Up @@ -90,7 +90,8 @@ showTableOfContents = false
cardView = "cardView"

[term]
showHero = false
showHero = true
heroStyle = "background"
showBreadcrumbs = false
showViews = false
showLikes = false
Expand Down
2 changes: 1 addition & 1 deletion content/posts/aws-iam-deleting-users/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ By enabling it, it will allow Terraform to delete the user even if it has non-Te

While it does seem a convenient option, be very careful with this argument, as it can lead to accidental deletion of users that are still active. So I would advise you to use it only if you are sure that the user is not active (maybe have a check in place that runs before the destruction of the resources), that you are aware of the security implications and lastly check the access of the team members that can run the Terraform code.

### Conclusion
## Conclusion

If Terraform cannot delete your AWS IAM users remember to check the user's Security credentials and look for any active access keys or MFA devices. If they are active, deactivate and remove them. How you handle it in your Terraform code is up to you, but remember to be careful with the `force_destroy` option.

Expand Down

0 comments on commit 0991e21

Please sign in to comment.