Displaying 1 to 20 from 24 results

terraform-aws-vpc - Terraform module which creates VPC resources on AWS

  •    HCL

Terraform module which creates VPC resources on AWS. By default this module will provision new Elastic IPs for the VPC's NAT Gateways. This means that when creating a new VPC, new IPs are allocated, and when that VPC is destroyed those IPs are released. Sometimes it is handy to keep the same IPs even after the VPC is destroyed and re-created. To that end, it is possible to assign existing IPs to the NAT Gateways. This prevents the destruction of the VPC from releasing those IPs, while making it possible that a re-created VPC uses the same IPs.

aws_rancher - Rancher cluster in AWS under 2 minutes

  •    HCL

Go ahead and edit content of terraform.tfvars to match your cluster configuration and nodes. When the deployment complete, you can access rancher cluster on http://server_ip:8080. You can see agent hosts under Infrastructure -> Host.

aws-map - Make a network graph of an AWS region

  •    Perl

The generated graph attempts to show you your AWS region from a networking perspetive. It shows you what can talk to what, at an IP level. Network Hosts and Network Ranges.




serverless-vpc-discovery - Serverless plugin for discovering VPC / Subnet / Security Group configuration by name

  •    Javascript

The vpc discovery plugin takes the given vpc, subnet, and security group names in the serverless file to setup the vpc configuration for the lambda. Amplify builds innovative and compelling digital educational products that empower teachers and students across the country. We have a long history as the leading innovator in K-12 education - and have been described as the best tech company in education and the best education company in tech. While others try to shrink the learning experience into the technology, we use technology to expand what is possible in real classrooms with real students and teachers.

aws-lambda-vpc - Setting up Lambda to access both VPC resources and also make calls to the internet

  •    

AWS Lambda is revolutionizing the cloud. Developers are creating interesting use cases day-by-day with the Lambda. In our use case, we are using Lambda as the Web backend. Lambdas and APIGateway together form a scalable, highly available and cost-efficient backend for your web application. When we use Lambda as our backend, we need our Lambda to talk to the databases. Usually databases reside inside an VPC, so that they are secured and not exposed to public world. Initially, if you want your Lambda to talk to an RDS(Relational Database Service), then you need to expose the RDS with the publicIP which helps Lambda to perform CRUD operations with the database. This exposing of database to the internet will be vulnerable. So, the obvious solution will be adding the Lambda inside an VPC. Lets see how we can add the Lambda within the VPC.

vpc-free - Find free IP address blocks in AWS EC2.

  •    Python

This script searches for the largest available IP subnets within the unallocated spaces between your VPC subnets, or between VPCs for a given CIDR block. The script uses the Amazon AWS SDK (boto3) to connect to AWS. The SDK must be configured with credentials to connect to the AWS APIs. Please see the Boto3 documentation for instruction.


tf_aws_vpc_only - A Terraform module to provide only VPC (without subnets) in AWS.

  •    HCL

A Terraform module to provide only VPC (without subnets) in AWS. If you want to create public and private subnets using single module you can use tf_aws_vpc module.

terraform-aws-security-group - Terraform module which creates EC2-VPC security groups on AWS

  •    HCL

Terraform module which creates EC2 security group within VPC on AWS. Ingress and egress rules can be configured in a variety of ways. See inputs section for all supported arguments and complete example for the complete use-case.

terraform-aws-named-subnets - Terraform module for named subnets provisioning.

  •    HCL

Terraform module for named subnets provisioning. This project is part of our comprehensive "SweetOps" approach towards DevOps.

terway - CNI plugin for alibaba cloud VPC/ENI

  •    Go

After setup kubernetes cluster. Change iptables Forward default policy to ACCEPT on every node of cluster: iptables -P FORWARD ACCEPT. Make sure cluster up and healthy by kubectl get cs.

terraform-aws-kops-metadata - Terraform module to lookup resources within a Kops cluster for easier integration with Terraform

  •    HCL

This project is part of our comprehensive "SweetOps" approach towards DevOps. It's 100% Open Source and licensed under the APACHE2.

terraform-aws-vpc-peering-multi-account - Terraform module to provision a VPC peering across multiple VPCs in different accounts by using multiple providers

  •    HCL

Terraform module to create a peering connection between any two VPCs existing in different AWS accounts. This module supports performing this action from a 3rd account (e.g. a "root" account) by specifying the roles to assume for each member account.

terraform-aws-dynamic-subnets - Terraform module for public and private subnets provisioning in existing VPC

  •    HCL

Note: this module is intended for use with an existing VPC and existing Internet Gateway. To create a new VPC, use terraform-aws-vpc module. This project is part of our comprehensive "SweetOps" approach towards DevOps.

terraform-aws-vpc - Terraform Module that defines a VPC with public/private subnets across multiple AZs with Internet Gateways

  •    HCL

Terraform module to provision a VPC with Internet Gateway. This project is part of our comprehensive "SweetOps" approach towards DevOps.

terraform-aws-vpc-peering - Terraform module to create a peering connection between two VPCs

  •    HCL

This project is part of our comprehensive "SweetOps" approach towards DevOps. It's 100% Open Source and licensed under the APACHE2.

vpc-peering-operator - A Kubernetes Operator to manage the lifecycle of AWS VPC Peering Connections

  •    Go

The VPC Peering operator for Kubernetes provides a way to natively define a vpc peering as a Kubernetes object and handles the lifecycle around the Peering and Routing for a VPC. The premise of this operator is to serve as a self service tool to allow users running in a multi tenant cluster to manage peerings to other AWS VPC's for consumption of their resources.