-
**Is your feature request related to a problem? Please describe.**
All IAM users created through LZA userSet has access to the console, with login credentials saved in Secrets Manager. More often tha…
-
**Is your feature request related to a problem? Please describe.**
Currently you cannot bypass the KMS default key policy, which is very broad (allow all for same account). Which means that I cannot …
-
**Is your feature request related to a problem? Please describe.**
In my case, the issue is with the AWS backup cross-account copy. Ref [Encryption for backups in AWS Backup
](https://docs.aws.amazo…
-
### Check for previous/existing GitHub issues/module proposals
- [X] I have checked for previous/existing GitHub issues/module proposals
### Check this module doesn't already exist in another pr…
-
### Check for previous/existing GitHub issues/module proposals
- [X] I have checked for previous/existing GitHub issues/module proposals
### Check this module doesn't already exist in another pr…
-
**Is your feature request related to a problem? Please describe.**
I updated the LZA from version `1.3.2` to `1.5.1`. After the update, there are some failed controls in SecurityHub related to LZA. …
-
**Is your feature request related to a problem? Please describe.**
LZA currently does not natively support the creation of TLS Inspection configuration resource.
As a work around we deployed it by …
-
**Is your feature request related to a problem? Please describe.**
Similar to the support for Tag and Backup policies, we would like to be able to manage our ChatBot policies from the `organizations-…
-
**Is your feature request related to a problem? Please describe.**
For customers leveraging a single LZA environment for both sensitive/protected and innovation/exploratory workloads, it would be gre…
-
**Is your feature request related to a problem? Please describe.**
Is there any way to improve the "feedback loop" when making LZA configuration changes. We are just starting to utilize the LZA an…