Product logo
DocsBlogPricing

@turbot/aws-vpc-internet

Version
5.11.2
Released On
Mar 07, 2024
Depends On

Resource Types

Control Types

Policy Types

Release Notes

5.11.2 (2024-03-07)

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.
  • In the previous version, we believed we had resolved an issue with Internet Gateways not being upserted into the CMDB while processing real-time CreateDefaultVpc events. However, we overlooked an edge case in the fix. We have now addressed this issue, ensuring that Internet Gateways will be reliably discovered and upserted into the Guardrails CMDB. We recommend updating the aws-vpc-core mod to version 5.17.1 or higher to enable Guardrails to correctly process real-time CreateDefaultVpc events for Internet Gateways.
  • 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.11.1 (2024-03-01)

Bug fixes

  • Previously, Guardrails did not upsert Internet Gateways into the CMDB while processing real-time CreateDefaultVpc events. This issue has been fixed, and Internet Gateways will now be more reliably upserted into the Guardrails CMDB. We recommend updating the aws-vpc-core mod to v5.17.1 or higher to allow Guardrails to process the CreateDefaultVpc event for Internet Gateways correctly.

5.11.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 > Egress Only Internet Gateway > Delete from AWS
  • AWS > VPC > Egress Only Internet Gateway > Set Tags
  • AWS > VPC > Egress Only Internet Gateway > Skip alarm for Active control
  • AWS > VPC > Egress Only Internet Gateway > Skip alarm for Active control [90 days]
  • AWS > VPC > Egress Only Internet Gateway > Skip alarm for Approved control
  • AWS > VPC > Egress Only Internet Gateway > Skip alarm for Approved control [90 days]
  • AWS > VPC > Egress Only Internet Gateway > Skip alarm for Tags control
  • AWS > VPC > Egress Only Internet Gateway > Skip alarm for Tags control [90 days]
  • AWS > VPC > Elastic IP > Delete from AWS
  • AWS > VPC > Elastic IP > Set Tags
  • AWS > VPC > Elastic IP > Skip alarm for Active control
  • AWS > VPC > Elastic IP > Skip alarm for Active control [90 days]
  • AWS > VPC > Elastic IP > Skip alarm for Approved control
  • AWS > VPC > Elastic IP > Skip alarm for Approved control [90 days]
  • AWS > VPC > Elastic IP > Skip alarm for Tags control
  • AWS > VPC > Elastic IP > Skip alarm for Tags control [90 days]
  • AWS > VPC > Endpoint > Delete from AWS
  • AWS > VPC > Endpoint > Set Tags
  • AWS > VPC > Endpoint > Skip alarm for Active control
  • AWS > VPC > Endpoint > Skip alarm for Active control [90 days]
  • AWS > VPC > Endpoint > Skip alarm for Approved control
  • AWS > VPC > Endpoint > Skip alarm for Approved control [90 days]
  • AWS > VPC > Endpoint > Skip alarm for Tags control
  • AWS > VPC > Endpoint > Skip alarm for Tags control [90 days]
  • AWS > VPC > Endpoint Service > Delete from AWS
  • AWS > VPC > Endpoint Service > Set Tags
  • AWS > VPC > Endpoint Service > Skip alarm for Active control
  • AWS > VPC > Endpoint Service > Skip alarm for Active control [90 days]
  • AWS > VPC > Endpoint Service > Skip alarm for Approved control
  • AWS > VPC > Endpoint Service > Skip alarm for Approved control [90 days]
  • AWS > VPC > Endpoint Service > Skip alarm for Tags control
  • AWS > VPC > Endpoint Service > Skip alarm for Tags control [90 days]
  • AWS > VPC > Internet Gateway > Delete from AWS
  • AWS > VPC > Internet Gateway > Set Tags
  • AWS > VPC > Internet Gateway > Skip alarm for Active control
  • AWS > VPC > Internet Gateway > Skip alarm for Active control [90 days]
  • AWS > VPC > Internet Gateway > Skip alarm for Approved control
  • AWS > VPC > Internet Gateway > Skip alarm for Approved control [90 days]
  • AWS > VPC > Internet Gateway > Skip alarm for Tags control
  • AWS > VPC > Internet Gateway > Skip alarm for Tags control [90 days]
  • AWS > VPC > NAT Gateway > Delete from AWS
  • AWS > VPC > NAT Gateway > Set Tags
  • AWS > VPC > NAT Gateway > Skip alarm for Active control
  • AWS > VPC > NAT Gateway > Skip alarm for Active control [90 days]
  • AWS > VPC > NAT Gateway > Skip alarm for Approved control
  • AWS > VPC > NAT Gateway > Skip alarm for Approved control [90 days]
  • AWS > VPC > NAT Gateway > Skip alarm for Tags control
  • AWS > VPC > NAT Gateway > Skip alarm for Tags control [90 days]

5.10.0 (2023-06-12)

What's new?

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

5.9.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 > Egress Only Internet Gateway > Approved > Custom
  • AWS > VPC > Elastic IP > Approved > Custom
  • AWS > VPC > Endpoint > Approved > Custom
  • AWS > VPC > Endpoint Service > Approved > Custom
  • AWS > VPC > Internet Gateway > Approved > Custom
  • AWS > VPC > NAT Gateway > Approved > Custom

5.8.0 (2021-07-22)

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.

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.7.0 (2021-04-05)

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

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

5.6.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.6.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.6.0 (2020-11-05)

What's new?

  • The AWS > VPC > Elastic IP > Active control can now check if an Elastic IP is attached to any resource or not. To enable this active check, please set the AWS > VPC > Elastic IP > Active > Attached policy.

Policy Types

  • AWS > VPC > Elastic IP > Active > Attached

5.5.0 (2020-10-30)

What's new?

  • The AWS > VPC > NAT Gateway > Active control can now check if the NAT Gateway is used by any VPC route table or not. To enable this active check, please set the AWS > VPC > NAT Gateway > Active > In use policy.

Policy Types

  • AWS > VPC > NAT Gateway > Active > In Use

5.4.0 (2020-10-16)

What's new?

  • Cross-account trust is not only important for complex enterprise and application scenarios but is also a critical area for security controls. We now support controlling cross-account access for VPC endpoints to provide automatic protection against unexpected cross-account access.

    A common set of trusted AWS account IDs can be defined in the AWS > Account > Trusted Accounts [Default] policy. Trusted accounts can also be defined at any level, even down to the specific VPC endpoint resource.

    To get started with these new controls, please see the AWS > VPC > Endpoint > Policy > Trusted Access policy.

Control Types

  • AWS > VPC > Endpoint > Policy
  • AWS > VPC > Endpoint > Policy > Trusted Access

Policy Types

  • AWS > VPC > Endpoint > Policy
  • AWS > VPC > Endpoint > Policy > Trusted Access
  • AWS > VPC > Endpoint > Policy > Trusted Access > Accounts
  • AWS > VPC > Endpoint > Policy > Trusted Access > Organization Restrictions
  • AWS > VPC > Endpoint > Policy > Trusted Access > Services

Action Types

  • AWS > VPC > Endpoint > Set Policy Trusted Access

5.3.1 (2020-10-16)

Bug fixes

  • The AWS > VPC > Elastic IP > Approved control would fail to delete an unapproved elastic IP if it was associated to an instance or network interface and the AWS > VPC > Elastic IP > Approved policy was set to Enforce: Detach and delete unapproved if new. This issue has been fixed.

5.3.0 (2020-10-09)

What's new?

  • The AWS > VPC > Internet Gateway > Active control can now check if an internet gateway is attached to any resource or not. To enable this active check, please set the AWS > VPC > Internet Gateway > Active > Attached policy.

Policy Types

  • AWS > VPC > Internet Gateway > Active > Attached

5.2.3 (2020-09-25)

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.2 (2020-09-14)

Bug fixes

  • VPC endpoint services created by AWS > VPC > Stack failed to get upserted to our database due to an invalid Terraform mapping. This issue has now been fixed.

5.2.1 (2020-09-06)

Bug fixes

  • Discovery controls of Egress Only Internet Gateway, Elastic IP, Endpoint, Endpoint Service, Internet Gateway and NAT Gateway resources remained in an error state due to an invalid reference to AWS > VPC > Regions policy. This issue has now been fixed.

5.2.0 (2020-09-04)

What's new?

  • Discovery controls now have their own control category, CMDB > Discovery, to allow for easier filtering separately from other CMDB controls.

Bug fixes

  • PolicyDocument field of VPC endpoint resources is now properly and consistently sorted.

  • 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.1.0 (2020-07-28)

What's new?

  • The AWS > VPC > Elastic IP > Approved control can now be used to disassociate unapproved elastic IPs from instances and network interfaces. To use this new feature, you can set the AWS > VPC > Elastic IP > Approved policy to Enforce: Detach unapproved or Enforce: Detach and delete unapproved if new.

5.0.4 (2020-07-08)

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.

5.0.3 (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.0.2 (2020-05-06)

Policy Types

Renamed

  • AWS > VPC > Egress Only Internet Gateway > Configured > Precedence to AWS > VPC > Egress Only Internet Gateway > Configured > Claim Precedence
  • AWS > VPC > Elastic IP > Configured > Precedence to AWS > VPC > Elastic IP > Configured > Claim Precedence
  • AWS > VPC > Endpoint > Configured > Precedence to AWS > VPC > Endpoint > Configured > Claim Precedence
  • AWS > VPC > Endpoint Service > Configured > Precedence to AWS > VPC > Endpoint Service > Configured > Claim Precedence
  • AWS > VPC > Internet Gateway > Configured > Precedence to AWS > VPC > Internet Gateway > Configured > Claim Precedence
  • AWS > VPC > NAT Gateway > Configured > Precedence to AWS > VPC > NAT Gateway > Configured > Claim Precedence