Search result for 'VPC'

This script creates a VPC, subnets, and security groups required for the EKS cluster in the us-west-2 region, ensuring no conflicts with existing resources.

This script checks for existing VPCs to avoid conflicts and creates a new VPC in the us-west-2 region if it doesn't already exist.

This script creates new subnets within the specified VPC in the us-west-2 region for the EKS cluster, finding non-conflicting CIDRs dynamically by iterating through potential CIDR blocks starting from a higher range to avoid conflicts.

This script checks if the security group already exists within the specified VPC in the us-west-2 region for the EKS cluster. If it doesn't exist, it creates the security group and authorizes inbound traffic.

The script lists all VPCs in the us-east-2 region using boto3 with credentials.

The script checks each VPC in the list to verify if VPC Flow Logs are enabled and returns their compliance status.

The script determines the overall compliance status for each VPC based on whether Flow Logs are enabled and marks as NON_COMPLIANT if any VPC does not have Flow Logs enabled.

The script tabulates the compliance results for all VPCs based on their Flow Logs status.

The script evaluates all VPCs in the us-east-2 region to check if VPC Flow Logs are enabled and tabulates the compliance status.

Lists all VPCs in the AWS account across all regions.

Lists all default security groups for each VPC across all regions.

Evaluates each default security group to verify that they do not allow any inbound or outbound traffic and tabulates the compliance results.

Evaluates default security groups in all VPCs across all regions for compliance and tabulates the results.

The script lists AWS security groups and checks if SSH access is open to the world, marking them as NON_COMPLIANT or COMPLIANT.

The workflow involves evaluating all Amazon VPCs within the AWS region us-east-2 to ensure that VPC Flow Logs are enabled. Each VPC is checked for compliance, and if any VPC lacks Flow Logs, it is marked as NON_COMPLIANT. The results of this compliance check are then tabulated for further analysis. This process helps in maintaining security and monitoring standards across the network infrastru...

The workflow involves assessing all default security groups within each Amazon VPC to ensure they do not permit any inbound or outbound traffic. If any default security group is found to have one or more inbound or outbound rules, it is marked as NON_COMPLIANT. The results of this evaluation are then organized into a tabulated format for easy review and analysis. This process helps maintain th...

The workflow involves identifying AWS security groups that have incoming SSH traffic (port 22) open to the public, specifically to IP addresses 0.0.0.0/0 or ::/0. These security groups are flagged as NON_COMPLIANT due to the potential security risk of unrestricted access. Conversely, security groups that do not have such open access are marked as COMPLIANT. This process ensures that security g...

The workflow involves analyzing AWS security groups across different regions to identify those that are non-compliant with security policies. Specifically, it focuses on security groups that allow inbound TCP traffic from unrestricted sources, such as 0.0.0.0/0 or ::/0. The process includes listing these non-compliant security groups along with the open ports and CIDR ranges that pose a securi...

This script lists the number of AWS security groups by region and identifies non-compliant groups allowing unrestricted inbound TCP traffic.