AWS guardduty: Fix VPC CIDR blocks documentation link
Summary
Updated URL by removing double slash in VPC CIDR reference.
Security assessment
Non-security URL correction.
Evidence
+If there is an issue while restricting the in-bound permissions to your VPC (or instance), you can the in-bound 443 port from any IP address `(0.0.0.0/0)`. However, GuardDuty recommends using IP addresses that matches the CIDR block for your VPC. For more information, see [VPC CIDR blocks](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html) in the _Amazon VPC User Guide_.
Diff
diff --git a/guardduty/latest/ug/eksrunmon-prereq-deploy-security-agent.md b/guardduty/latest/ug/eksrunmon-prereq-deploy-security-agent.md index aa74f93cb..b5422aaf3 100644 --- a//guardduty/latest/ug/eksrunmon-prereq-deploy-security-agent.md +++ b//guardduty/latest/ug/eksrunmon-prereq-deploy-security-agent.md @@ -99 +99 @@ For more information, see [ResourceOrgID](https://docs.aws.amazon.com/IAM/latest -If there is an issue while restricting the in-bound permissions to your VPC (or instance), you can the in-bound 443 port from any IP address `(0.0.0.0/0)`. However, GuardDuty recommends using IP addresses that matches the CIDR block for your VPC. For more information, see [VPC CIDR blocks](https://docs.aws.amazon.com//vpc/latest/userguide/vpc-cidr-blocks.html) in the _Amazon VPC User Guide_. +If there is an issue while restricting the in-bound permissions to your VPC (or instance), you can the in-bound 443 port from any IP address `(0.0.0.0/0)`. However, GuardDuty recommends using IP addresses that matches the CIDR block for your VPC. For more information, see [VPC CIDR blocks](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-cidr-blocks.html) in the _Amazon VPC User Guide_.