Product logo
DocsBlogPricing

@turbot/aws-vpc-connect

Version
5.9.1
Released On
Mar 18, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.9.1 (2024-03-18)

Bug fixes

  • Guardrails will now exclude upserting VPC resources that are shared from other accounts and only upsert resources that belong to the owner account.
  • Guardrails failed to filter out real-time events for resource types if their parent resource types' CMDB policy was set to Enforce: Disabled. This is now fixed.

5.9.0 (2023-10-31)

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.

5.8.0 (2023-06-06)

What's new?

  • Resource's metadata will now also include createdBy details in Turbot CMDB.

Action Types

  • AWS > VPC > Customer Gateway > Delete from AWS
  • AWS > VPC > Customer Gateway > Set Tags
  • AWS > VPC > Customer Gateway > Skip alarm for Active control
  • AWS > VPC > Customer Gateway > Skip alarm for Active control [90 days]
  • AWS > VPC > Customer Gateway > Skip alarm for Approved control
  • AWS > VPC > Customer Gateway > Skip alarm for Approved control [90 days]
  • AWS > VPC > Customer Gateway > Skip alarm for Tags control
  • AWS > VPC > Customer Gateway > Skip alarm for Tags control [90 days]
  • AWS > VPC > Peering Connection > Delete from AWS
  • AWS > VPC > Peering Connection > Set Tags
  • AWS > VPC > Peering Connection > Skip alarm for Active control
  • AWS > VPC > Peering Connection > Skip alarm for Active control [90 days]
  • AWS > VPC > Peering Connection > Skip alarm for Approved control
  • AWS > VPC > Peering Connection > Skip alarm for Approved control [90 days]
  • AWS > VPC > Peering Connection > Skip alarm for Tags control
  • AWS > VPC > Peering Connection > Skip alarm for Tags control [90 days]
  • AWS > VPC > Transit Gateway > Delete from AWS
  • AWS > VPC > Transit Gateway > Set Tags
  • AWS > VPC > Transit Gateway > Skip alarm for Active control
  • AWS > VPC > Transit Gateway > Skip alarm for Active control [90 days]
  • AWS > VPC > Transit Gateway > Skip alarm for Approved control
  • AWS > VPC > Transit Gateway > Skip alarm for Approved control [90 days]
  • AWS > VPC > Transit Gateway > Skip alarm for Tags control
  • AWS > VPC > Transit Gateway > Skip alarm for Tags control [90 days]
  • AWS > VPC > Transit Gateway Route Table > Delete from AWS
  • AWS > VPC > Transit Gateway Route Table > Set Tags
  • AWS > VPC > Transit Gateway Route Table > Skip alarm for Active control
  • AWS > VPC > Transit Gateway Route Table > Skip alarm for Active control [90 days]
  • AWS > VPC > Transit Gateway Route Table > Skip alarm for Approved control
  • AWS > VPC > Transit Gateway Route Table > Skip alarm for Approved control [90 days]
  • AWS > VPC > Transit Gateway Route Table > Skip alarm for Tags control
  • AWS > VPC > Transit Gateway Route Table > Skip alarm for Tags control [90 days]
  • AWS > VPC > VPN Connection > Delete from AWS
  • AWS > VPC > VPN Connection > Set Tags
  • AWS > VPC > VPN Connection > Skip alarm for Active control
  • AWS > VPC > VPN Connection > Skip alarm for Active control [90 days]
  • AWS > VPC > VPN Connection > Skip alarm for Approved control
  • AWS > VPC > VPN Connection > Skip alarm for Approved control [90 days]
  • AWS > VPC > VPN Connection > Skip alarm for Tags control
  • AWS > VPC > VPN Connection > Skip alarm for Tags control [90 days]
  • AWS > VPC > VPN Gateway > Delete from AWS
  • AWS > VPC > VPN Gateway > Set Tags
  • AWS > VPC > VPN Gateway > Skip alarm for Active control
  • AWS > VPC > VPN Gateway > Skip alarm for Active control [90 days]
  • AWS > VPC > VPN Gateway > Skip alarm for Approved control
  • AWS > VPC > VPN Gateway > Skip alarm for Approved control [90 days]
  • AWS > VPC > VPN Gateway > Skip alarm for Tags control
  • AWS > VPC > VPN Gateway > Skip alarm for Tags control [90 days]

5.7.1 (2022-04-08)

Bug fixes

  • The AWS > VPC > Peering Connection > DNS Resolution control would always remain in a TBD state for accepter peering connections. This is fixed and the control now works as expected.

5.7.0 (2022-02-16)

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

  • 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.

Policy Types

  • AWS > VPC > Customer Gateway > Approved > Custom
  • AWS > VPC > Peering Connection > Approved > Custom
  • AWS > VPC > Transit Gateway > Approved > Custom
  • AWS > VPC > Transit Gateway Route Table > Approved > Custom
  • AWS > VPC > VPN Connection > Approved > Custom
  • AWS > VPC > VPN Gateway > Approved > Custom

5.6.0 (2021-07-15)

What's new?

  • 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.5.1 (2021-05-25)

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.5.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.

Policy Types

  • AWS > Turbot > Event Handlers > Events > Rules > Custom Event Patterns > @turbot/aws-vpc-connect

5.4.1 (2021-03-23)

Bug fixes

  • The AWS > VPC > Transit Gateway Attachment > Discovery control will now remain in the skipped state for the ap-northeast-3 region since AWS does not support the creation of transit gateway attachments in this region.

5.4.0 (2021-02-22)

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.

5.3.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.3.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.3.0 (2020-11-05)

What's new?

  • We've made improvements to how Approved controls interact with CMDB policies and controls for more reliable approved checks. Now, if a resource's CMDB policy is set to Skip, its Approved control will move to invalid to prevent the Approved control from making a decision based on outdated information. Also, Approved controls will now wait until the resource's CMDB control has run at least once to ensure the required data is available.

5.2.3 (2020-10-28)

Bug fixes

  • The AWS > VPC > Transit Gateway Route Table > Approved control would fail to delete an unapproved transit gateway route table if it had any associations and the AWS > VPC > Transit Gateway Route Table > Approved policy was set to Enforce: Detach and delete unapproved if new. This issue has been fixed.

5.2.2 (2020-09-22)

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.2.1 (2020-09-10)

Bug fixes

  • In 5.2.0, we added the Transit Gateway Attachment [Cross-Account] resource type, which was meant to store information for transit gateway attachments from other AWS accounts; however, resources of this type were not functioning properly as they were not compatible with the existing Transit Gateway Attachment resource type and the AWS > VPC > Stack control.

    We've removed the Transit Gateway Attachment [Cross-Account] resource type along with its action, control, and policy types to prevent any conflicts with Transit Gateway Attachment resources.

    Any existing cross-account transit gateway attachments in CMDB will automatically be deleted and recreated as Transit Gateway Attachment resources by the AWS > VPC > Transit Gateway Attachment [Cross-Account] > Discovery control.

  • 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.

Resource Types

Removed

  • AWS > VPC > Transit Gateway Attachment [Cross-Account]

Control Types

  • AWS > VPC > Transit Gateway Attachment > Discovery [Cross-Account]

Removed

  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > CMDB
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Discovery
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Tags
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Usage

Policy Types

Removed

  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > CMDB
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured > Claim Precedence
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured > Source
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Regions
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Tags
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Tags > Template
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Usage
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Usage > Limit

Action Types

Removed

  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Router
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Update Tags

5.2.0 (2020-07-22)

Resource Types

  • AWS > VPC > Transit Gateway Attachment [Cross-Account]

Control Types

  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > CMDB
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Discovery
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Tags
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Usage

Policy Types

  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > CMDB
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured > Claim Precedence
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Configured > Source
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Regions
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Tags
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Tags > Template
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Usage
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Usage > Limit

Action Types

  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Router
  • AWS > VPC > Transit Gateway Attachment [Cross-Account] > Update Tags

5.1.4 (2020-07-08)

Bug fixes

  • Updated various resource configurations to provide better compatibility with AWS China regions.

5.1.3 (2020-06-23)

Bug fixes

  • Although the data validation errors, which appear in various CMDB and Discovery controls, are not blockers, they look ugly in the UI and should be cleaned up. These errors have now been fixed.

5.1.2 (2020-06-03)

Bug fixes

  • Changes made to the tags of Transit Gateway resources will now be automatically updated in its CMDB.

5.1.1 (2020-06-01)

Bug fixes

  • Links to documentation in the descriptions for several controls and policies were broken. These links have now been fixed.

5.1.0 (2020-05-06)

Resource Types

  • AWS > VPC > Transit Gateway Attachment

Control Types

  • AWS > VPC > Transit Gateway Attachment > CMDB
  • AWS > VPC > Transit Gateway Attachment > Configured
  • AWS > VPC > Transit Gateway Attachment > Discovery

Policy Types

  • AWS > VPC > Transit Gateway Attachment > CMDB
  • AWS > VPC > Transit Gateway Attachment > Configured
  • AWS > VPC > Transit Gateway Attachment > Configured > Claim Precedence
  • AWS > VPC > Transit Gateway Attachment > Configured > Source
  • AWS > VPC > Transit Gateway Attachment > Regions

Renamed

  • AWS > VPC > Customer Gateway > Configured > Precedence to AWS > VPC > Customer Gateway > Configured > Claim Precedence
  • AWS > VPC > Peering Connection > Configured > Precedence to AWS > VPC > Peering Connection > Configured > Claim Precedence
  • AWS > VPC > Transit Gateway > Configured > Precedence to AWS > VPC > Transit Gateway > Configured > Claim Precedence
  • AWS > VPC > Transit Gateway Route Table > Configured > Precedence to AWS > VPC > Transit Gateway Route Table > Configured > Claim Precedence
  • AWS > VPC > VPN Connection > Configured > Precedence to AWS > VPC > VPN Connection > Configured > Claim Precedence
  • AWS > VPC > VPN Gateway > Configured > Precedence to AWS > VPC > VPN Gateway > Configured > Claim Precedence

Action Types

  • AWS > VPC > Transit Gateway Attachment > Router