Product logo
DocsBlogPricing

@turbot/aws-vpc-core

The aws-vpc-core mod contains resource, control and policy definitions for AWS VPC service.

Version
5.17.1
Released On
Mar 04, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.17.1 (2024-03-04)

Bug fixes

  • Previously, Guardrails did not upsert DHCP Options into the CMDB while processing real-time CreateDefaultVpc events. This issue has been fixed, and DHCP Options will now be more reliably upserted into the Guardrails CMDB.

5.17.0 (2023-11-02)

What's new?

  • We've updated the runtime of the lambda functions to Node 18. You wouldn't notice any difference and things will continue to work smoothly and consistently as before.

Action Types

  • AWS > VPC > DHCP Options > Delete from AWS
  • AWS > VPC > DHCP Options > Set Tags
  • AWS > VPC > DHCP Options > Skip alarm for Active control
  • AWS > VPC > DHCP Options > Skip alarm for Active control [90 days]
  • AWS > VPC > DHCP Options > Skip alarm for Tags control
  • AWS > VPC > DHCP Options > Skip alarm for Tags control [90 days]
  • AWS > VPC > Route Table > Delete from AWS
  • AWS > VPC > Route Table > Set Tags
  • AWS > VPC > Route Table > Skip alarm for Active control
  • AWS > VPC > Route Table > Skip alarm for Active control [90 days]
  • AWS > VPC > Route Table > Skip alarm for Tags control
  • AWS > VPC > Route Table > Skip alarm for Tags control [90 days]
  • AWS > VPC > Subnet > Delete from AWS
  • AWS > VPC > Subnet > Set Tags
  • AWS > VPC > Subnet > Skip alarm for Active control
  • AWS > VPC > Subnet > Skip alarm for Active control [90 days]
  • AWS > VPC > Subnet > Skip alarm for Tags control
  • AWS > VPC > Subnet > Skip alarm for Tags control [90 days]
  • AWS > VPC > VPC > Delete from AWS
  • AWS > VPC > VPC > Set Tags
  • AWS > VPC > VPC > Skip alarm for Active control
  • AWS > VPC > VPC > Skip alarm for Active control [90 days]
  • AWS > VPC > VPC > Skip alarm for Tags control
  • AWS > VPC > VPC > Skip alarm for Tags control [90 days]

Renamed

  • AWS > VPC > VPC > Skip alarm for approved control to AWS > VPC > VPC > Skip alarm for Approved control
  • AWS > VPC > VPC > Skip alarm for approved control [90 days] to AWS > VPC > VPC > Skip alarm for Approved control [90 days]

5.16.0 (2023-06-06)

What's new?

  • README.md file is now available for users to check details about the resource types and service permissions that the mod covers.
  • Resource's metadata will now also include createdBy details in Guardrails CMDB.
  • We've added new Guardrails AKAs for AWS > VPC resource types that match their individual unique identifiers. E.g. VpcId will now also be a Guardrails AKA for AWS > VPC > VPC, SubnetId for AWS > VPC > Subnet etc.. Querying such resources in Guardrails will now be easier than before.

5.15.0 (2022-11-01)

Control Types

  • AWS > VPC > VPC > Stack

Policy Types

  • AWS > VPC > VPC > Stack
  • AWS > VPC > VPC > Stack > Secret Variables
  • AWS > VPC > VPC > Stack > Source
  • AWS > VPC > VPC > Stack > Terraform Version
  • AWS > VPC > VPC > Stack > Variables

Action Types

  • AWS > VPC > DHCP Options > Skip alarm for Approved control
  • AWS > VPC > DHCP Options > Skip alarm for Approved control [90 days]
  • AWS > VPC > Route Table > Skip alarm for Approved control
  • AWS > VPC > Route Table > Skip alarm for Approved control [90 days]
  • AWS > VPC > Subnet > Skip alarm for Approved control
  • AWS > VPC > Subnet > Skip alarm for Approved control [90 days]
  • AWS > VPC > VPC > Skip alarm for approved control
  • AWS > VPC > VPC > Skip alarm for approved control [90 days]

5.14.1 (2022-02-16)

Bug fixes

  • We've improved the process of deleting resources from Guardrails if their CMDB policy was set to Enforce: Disabled. The CMDB controls will now not look to resolve credentials via Guardrails' IAM role while deleting resources from Guardrails. This will allow the CMDB controls to process resource deletions from Guardrails more reliably than before.

5.14.0 (2022-02-09)

What's new?

  • Users can now create their own custom checks against resource attributes in the Approved control using the Approved > Custom policy. These custom checks would be a part of the evaluation of the Approved control. Custom messages can also be added which are then displayed in the control details table. See Custom Checks for more information.

Bug fixes

  • The AWS/VPC/Admin, AWS/VPC/Metadata and AWS/VPC/Operator grants would fail to show up on the Permissions tab while assigning access to users for an account when the AWS > VPC > Permissions policy was set to Enabled. This is now fixed.

Policy Types

  • AWS > VPC > DHCP Options > Approved > Custom
  • AWS > VPC > Route Table > Approved > Custom
  • AWS > VPC > Subnet > Approved > Custom
  • AWS > VPC > VPC > Approved > Custom

5.13.0 (2022-01-10)

What's new?

  • AWS/VPC/Admin and AWS/VPC/Metadata now include permissions for Carrier Gateway, Ipam, Network Insights Access Scope, Subnet Cidr Reservation, TransitGateway Connect, TransitGateway Prefix List Reference and Public Ipv4 Pool Cidr.

5.12.1 (2021-10-01)

Bug fixes

  • The AWS > VPC > Route > Discovery control would go into an error state when there were no routes to upsert. This is now fixed.

5.12.0 (2021-07-20)

What's new?

  • AWS/VPC/Admin now includes traffic mirror filter permissions.

  • We've improved the details tables in the Tags controls to be more helpful, especially when a resource's tags are not set correctly as expected. Previously, to understand why the Tags controls were in an Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

5.11.0 (2021-06-23)

What's new?

  • AWS/VPC/Admin now includes client VPN, network insights, traffic mirror filter, transit gateway, and VPC reachability analyzer permissions.

5.10.1 (2021-05-21)

Bug fixes

  • We’ve made a few improvements in the GraphQL queries for various controls, policies, and actions. You won’t notice any difference, but things should run lighter and quicker than before.

5.10.0 (2021-04-02)

Bug fixes

  • We've improved our event handling configuration and now filter which AWS events Guardrails listens for based on resources' CMDB policies. If a resource's CMDB policy is not set to Enforce: Enabled, the EventBridge rules will be configured to not send any events for that resource. This will greatly reduce the number of unnecessary events that Guardrails listens for and handles today.
  • Users can now configure the log record format in the AWS > VPC > VPC > Flow Logging control to specify the fields to include in the flow log record. To get started, set the AWS > VPC > VPC > Flow Logging > Log Record Format policy.

Policy Types

  • AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-vpc-core
  • AWS > VPC > VPC > Flow Logging > Log Record Format

5.9.0 (2021-02-18)

What's new?

  • We've improved the state reasons and details tables in various Approved and Active controls to be more helpful, especially when a resource is unapproved or inactive. Previously, to understand why one of these controls is in Alarm state, you would need to find and read the control's process logs. This felt like too much work for a simple task, so now these details are visible directly from the control page.

Bug fixes

  • The AWS > VPC > Subnet > CMDB control will now automatically re-run every 24 hours to update the AvailableIpAddressCount property in a subnet because AWS does not currently support real-time events for IP count updates.

5.8.3 (2021-01-13)

Bug fixes

  • The AWS > VPC > VPC > Discovery control would sometimes fail to upsert all VPCs in a region due to lack of paging support. This is now fixed.

5.8.2 (2021-01-08)

Bug fixes

  • We've improved the real-time event handling for tag events that update multiple resources at a time and now all resources in a tag event will be updated in CMDB consistently.
  • Controls run faster now when in the tbd and skipped states thanks to the new Guardrails Precheck feature (not to be confused with TSA PreCheck). With Guardrails Precheck, controls avoid running GraphQL input queries when in tbd and skipped, resulting in faster and lighter control runs.

5.8.1 (2020-12-08)

Bug fixes

  • We've optimized the GraphQL queries for various controls when they're in the tbd and skipped states. You won't notice any difference but they should run a lot lighter now.

5.8.0 (2020-10-19)

What's new?

  • Policy Types

    Added

  • AWS > VPC > Trusted Accounts [Default]

  • AWS > VPC > Trusted Organizations [Default]

  • AWS > VPC > Trusted Services [Default]

5.7.2 (2020-10-08)

Bug fixes

  • The AWS > VPC > Default VPC > Approved control would sometimes go into an error state after deleting the default VPC in a region. This is now fixed.

5.7.1 (2020-09-29)

Bug fixes

  • We've made some improvements to our real-time event handling that reduces the risk of creating resources in CMDB with malformed AKAs. There's no noticeable difference, but things should run more reliably now.

5.7.0 (2020-09-07)

What's new?

  • Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.
  • We've renamed the service's default regions policy from Regions [Default] to Regions to be consistent with our other regions policies.

Bug fixes

  • Whenever a subnet was dissociated from a route table, AWS > VPC > Route Table > CMDB did not get updated automatically. This issue has now been fixed.

5.6.2 (2020-08-17)

Bug fixes

  • In various Active controls, we were outputting log messages that did not properly show how many days were left until we'd delete the inactive resources (we were still deleting them after the correct number of days). These log messages have been fixed and now contain the correct number of days.

5.6.1 (2020-08-07)

Bug fixes

  • In the AWS > VPC > Route > CMDB control, we now get route information directly from the AWS API instead of from the route table's CMDB entry. This prevents a race condition that resulted in routes created by the AWS > VPC > Stack control being immediately deleted if their route table information was outdated.

5.6.0 (2020-07-22)

What's new?

  • The AWS > VPC > Subnet > Auto Assign Public IP policy now includes the policy values Check: Enabled, Check: Disabled, Enforce: Enabled, and Enforce: Disabled. With the addition of these values, it is now possible to also disable a subnet's auto-assign public IP setting. We have also deprecated the policy values Check: Auto Assign Public IP and Enforce: Auto Assign Public IP (replaced by Check: Enabled and Enforce: Enabled respectively). These policy values will be removed in the next major version and any current policy settings using these values should be updated.

5.5.0 (2020-07-07)

What's new?

  • Updated AWS > VPC > Regions policy default value to now include af-south-1, cn-north-1, cn-northwest-1.

5.4.0 (2020-06-30)

Bug fixes

  • Sometimes when updating CMDB for resources with tags that have empty string values, e.g., [{Key: "Empty", Value: ""}, {Key: "Guardrails is great", Value: "true"}], we would not store all of the tags correctly. This has been fixed and now all tags are accounted for.

Policy Types

Removed

  • AWS > VPC > Subnet > Auto Assign Public IP > Subnet Auto Assign Public IP Types

5.3.0 (2020-06-25)

What's new?

  • IAM permissions pertaining to local gateways can now be managed by setting AWS > VPC > Enabled policy to Enabled.

5.2.1 (2020-06-01)

Bug fixes

  • The AWS > VPC > Stack control would fail when trying to create Route resources due to incorrect Terraform metadata for Routes. This has been resolved and now the stack control works smoothly.

5.2.0 (2020-05-08)

Resource Types

  • AWS > VPC > Route

Control Types

  • AWS > VPC > Route > CMDB
  • AWS > VPC > Route > Configured
  • AWS > VPC > Route > Discovery

Policy Types

  • AWS > VPC > Route > CMDB
  • AWS > VPC > Route > Configured
  • AWS > VPC > Route > Configured > Claim Precedence
  • AWS > VPC > Route > Configured > Source

5.1.0 (2020-05-06)

Control Types

  • AWS > VPC > Stack

Policy Types

  • AWS > VPC > Stack
  • AWS > VPC > Stack > Source
  • AWS > VPC > Stack > Variables

Renamed

  • AWS > VPC > DHCP Options > Configured > Precedence to AWS > VPC > DHCP Options > Configured > Claim Precedence
  • AWS > VPC > Route Table > Configured > Precedence to AWS > VPC > Route Table > Configured > Claim Precedence
  • AWS > VPC > Subnet > Configured > Precedence to AWS > VPC > Subnet > Configured > Claim Precedence
  • AWS > VPC > VPC > Configured > Precedence to AWS > VPC > VPC > Configured > Claim Precedence

5.0.2 (2020-04-24)

Bug fixes

  • The Default VPC > Approved control was not correctly identifying default VPCs in a region due to an invalid filter query. This has been fixed and the default VPCs are all accounted for.