Skip to content

GMADLA/terraform-aws-cloudwatch-flow-logs

 
 

Repository files navigation

README Header

Cloud Posse

terraform-aws-cloudwatch-flow-logs Build Status Latest Release Slack Community

Terraform module for enabling flow logs for vpc and subnets.


This project is part of our comprehensive "SweetOps" approach towards DevOps.

Terraform Open Source Modules

It's 100% Open Source and licensed under the APACHE2.

We literally have hundreds of terraform modules that are Open Source and well-maintained. Check them out!

Usage

IMPORTANT: The master branch is used in source just as an example. In your code, do not pin to master because there may be breaking changes between releases. Instead pin to the release tag (e.g. ?ref=tags/x.y.z) of one of our latest releases.

module "flow_logs" {
  source    = "git::https://github.com/cloudposse/terraform-aws-cloudwatch-flow-logs.git?ref=master"
  vpc_id    = "${var.vpc_id}"
  namespace = "${var.namespace}"
  stage     = "${var.stage}"
}

Makefile Targets

Available targets:

  help                                Help screen
  help/all                            Display help for all targets
  help/short                          This help short screen
  lint                                Lint terraform code

Inputs

Name Description Type Default Required
attributes Additional attributes (e.g. policy or role) list <list> no
delimiter Delimiter to be used between name, namespace, stage, etc. string - no
enabled Set to false to prevent the module from creating anything string true no
encryption_type GUID for the customer-managed KMS key to use for encryption. The only acceptable values are NONE or KMS string NONE no
eni_ids IDs of ENIs list <list> no
filter_pattern Valid CloudWatch Logs filter pattern for subscribing to a filtered stream of log events string [version, account, eni, source, destination, srcport, destport, protocol, packets, bytes, windowstart, windowend, action, flowlogstatus] no
kms_key_id ID of KMS key string `` no
name Name (e.g. bastion or db) string `` no
namespace Namespace (e.g. cp or cloudposse) string - yes
region AWS region string `` no
retention_in_days Number of days you want to retain log events in the log group string 30 no
retention_period Length of time data records are accessible after they are added to the stream string 48 no
shard_count Number of shards that the stream will use string 1 no
shard_level_metrics List of shard-level CloudWatch metrics which can be enabled for the stream list <list> no
stage Stage (e.g. prod, dev, staging) string - yes
subnet_ids IDs of subnets list <list> no
tags Additional tags (e.g. map(BusinessUnit,XYZ) map <map> no
traffic_type Type of traffic to capture. Valid values: ACCEPT,REJECT, ALL string ALL no
vpc_id ID of VPC string - yes

Outputs

Name Description
eni_flow_ids Flow Log IDs of ENIs
kinesis_arn Kinesis Stream ARN
kinesis_id Kinesis Stream ID
kinesis_name Kinesis Stream name
kinesis_shard_count Kinesis Stream Shard count
log_group_arn ARN of the log group
subnet_flow_ids Flow Log IDs of subnets
vpc_flow_id VPC Flow Log ID

Share the Love

Like this project? Please give it a ★ on our GitHub! (it helps us a lot)

Are you using this project or any of our other projects? Consider leaving a testimonial. =)

Related Projects

Check out these related projects.

Help

Got a question? We got answers.

File a GitHub issue, send us an email or join our Slack Community.

README Commercial Support

DevOps Accelerator for Startups

We are a DevOps Accelerator. We'll help you build your cloud infrastructure from the ground up so you can own it. Then we'll show you how to operate it and stick around for as long as you need us.

Learn More

Work directly with our team of DevOps experts via email, slack, and video conferencing.

We deliver 10x the value for a fraction of the cost of a full-time engineer. Our track record is not even funny. If you want things done right and you need it done FAST, then we're your best bet.

  • Reference Architecture. You'll get everything you need from the ground up built using 100% infrastructure as code.
  • Release Engineering. You'll have end-to-end CI/CD with unlimited staging environments.
  • Site Reliability Engineering. You'll have total visibility into your apps and microservices.
  • Security Baseline. You'll have built-in governance with accountability and audit logs for all changes.
  • GitOps. You'll be able to operate your infrastructure via Pull Requests.
  • Training. You'll receive hands-on training so your team can operate what we build.
  • Questions. You'll have a direct line of communication between our teams via a Shared Slack channel.
  • Troubleshooting. You'll get help to triage when things aren't working.
  • Code Reviews. You'll receive constructive feedback on Pull Requests.
  • Bug Fixes. We'll rapidly work with you to fix any bugs in our projects.

Slack Community

Join our Open Source Community on Slack. It's FREE for everyone! Our "SweetOps" community is where you get to talk with others who share a similar vision for how to rollout and manage infrastructure. This is the best place to talk shop, ask questions, solicit feedback, and work together as a community to build totally sweet infrastructure.

Newsletter

Sign up for our newsletter that covers everything on our technology radar. Receive updates on what we're up to on GitHub as well as awesome new projects we discover.

Office Hours

Join us every Wednesday via Zoom for our weekly "Lunch & Learn" sessions. It's FREE for everyone!

zoom

Contributing

Bug Reports & Feature Requests

Please use the issue tracker to report any bugs or file feature requests.

Developing

If you are interested in being a contributor and want to get involved in developing this project or help out with our other projects, we would love to hear from you! Shoot us an email.

In general, PRs are welcome. We follow the typical "fork-and-pull" Git workflow.

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. Submit a Pull Request so that we can review your changes

NOTE: Be sure to merge the latest changes from "upstream" before making a pull request!

Copyright

Copyright © 2017-2020 Cloud Posse, LLC

License

License

See LICENSE for full details.

Licensed to the Apache Software Foundation (ASF) under one
or more contributor license agreements.  See the NOTICE file
distributed with this work for additional information
regarding copyright ownership.  The ASF licenses this file
to you under the Apache License, Version 2.0 (the
"License"); you may not use this file except in compliance
with the License.  You may obtain a copy of the License at

  https://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing,
software distributed under the License is distributed on an
"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
KIND, either express or implied.  See the License for the
specific language governing permissions and limitations
under the License.

Trademarks

All other trademarks referenced herein are the property of their respective owners.

About

This project is maintained and funded by Cloud Posse, LLC. Like it? Please let us know by leaving a testimonial!

Cloud Posse

We're a DevOps Professional Services company based in Los Angeles, CA. We ❤️ Open Source Software.

We offer paid support on all of our projects.

Check out our other projects, follow us on twitter, apply for a job, or hire us to help with your cloud strategy and implementation.

Contributors

Vladimir
Vladimir

README Footer Beacon

About

Terraform module for enabling flow logs for vpc and subnets.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • HCL 96.0%
  • Makefile 4.0%