-
### Steps to Reproduce
Running prowler on AWS, sending findings to aggregate to SecHub.
The following finding is triggered with HIGH.
[Ensure no security groups allow ingress from wide-open non…
-
### Terraform Core Version
1.9.1
### AWS Provider Version
5.64.0
### Affected Resource(s)
Affected Resource:
aws_vpc (within the terraform-aws-modules/vpc/aws module)
aws_vpc_ipam_poo…
-
import ipaddress
import networkx as nx
import matplotlib.pyplot as plt
import pandas as pd
# Read data from CSV
df = pd.read_csv('network_locations.csv')
# Create a graph
G = nx.DiGraph()
…
-
### Documentation Link
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/security_group#ingress
### Description
### Terraform Version
```shell
NA
```
### A…
-
### Related Problem
I am using AWS CodeBuild to build a .NET 8 project which relies on some public NuGet packages. I'd like to lock down the Security Group on my CodeBuild project to ONLY allow outbo…
-
### Terraform Core Version
1.4.2, OpenTofu 1.6.2
### AWS Provider Version
5.61.0
### Affected Resource(s)
* aws_mq_broker
* aws_mq_configuration
### Expected Behavior
The plan fr…
-
### Is your feature request related to a problem?
No- its a simplification
instead of defining the CIDR then doing all the NACL's, security groups before the subnets are defined. define the CIDR…
-
I can list all `destination_cidr_block` values:
```
> select destination_cidr_block from aws_vpc_route limit 5;
+------------------------+
| destination_cidr_block |
+------------------------+
|…
-
/kind bug
**What steps did you take and what happened:**
Create a VPC with 3 CIDR blocks (A, B, and C), each containing 2 subnets, 1 private and 1 public. During cluster creation, specify the su…
-
### Describe the feature
Referencing #28480 the Amazon provided IPv6 CIDR block (/56) should be able to be referenced to use it on egress records or Security Groups. Currently this is only possible f…