AWS cli medium security documentation change
Summary
Added VPC configuration details for Prometheus collector security groups and subnets when connecting to MSK clusters
Security assessment
Added documentation about security group configurations and VPC settings that enforce network isolation and access control for Prometheus collectors. Explicitly mentions secure private network connectivity requirements between components.
Diff
diff --git a/cli/latest/reference/amp/describe-scraper.md b/cli/latest/reference/amp/describe-scraper.md index 38b1bfad3..de92f6b5a 100644 --- a//cli/latest/reference/amp/describe-scraper.md +++ b//cli/latest/reference/amp/describe-scraper.md @@ -15 +15 @@ - * [AWS CLI 2.31.32 Command Reference](../../index.html) » + * [AWS CLI 2.31.35 Command Reference](../../index.html) » @@ -339 +339 @@ scraper -> (structure) ->> This is a Tagged Union structure. Only one of the following top level keys can be set: `eksConfiguration`. +>> This is a Tagged Union structure. Only one of the following top level keys can be set: `eksConfiguration`, `vpcConfiguration`. @@ -399,0 +400,50 @@ scraper -> (structure) +>> +>> vpcConfiguration -> (structure) +>> +>>> The Amazon VPC configuration for the Prometheus collector when connecting to Amazon MSK clusters. This configuration enables secure, private network connectivity between the collector and your Amazon MSK cluster within your Amazon VPC. +>>> +>>> securityGroupIds -> (list) [required] +>>> +>>>> The security group IDs that control network access for the Prometheus collector. These security groups must allow the collector to communicate with your Amazon MSK cluster on the required ports. +>>>> +>>>> Constraints: +>>>> +>>>> * min: `1` +>>>> * max: `5` +>>>> + +>>>> +>>>> (string) +>>>> +>>>>> ID of a VPC security group. +>>>>> +>>>>> Constraints: +>>>>> +>>>>> * min: `0` +>>>>> * max: `255` +>>>>> * pattern: `sg-[0-9a-z]+` +>>>>> + +>>> +>>> subnetIds -> (list) [required] +>>> +>>>> The subnet IDs where the Prometheus collector will be deployed. The subnets must be in the same Amazon VPC as your Amazon MSK cluster and have network connectivity to the cluster. +>>>> +>>>> Constraints: +>>>> +>>>> * min: `1` +>>>> * max: `5` +>>>> + +>>>> +>>>> (string) +>>>> +>>>>> ID of a VPC subnet. +>>>>> +>>>>> Constraints: +>>>>> +>>>>> * min: `0` +>>>>> * max: `255` +>>>>> * pattern: `subnet-[0-9a-z]+` +>>>>> + @@ -457 +507 @@ scraper -> (structure) - * [AWS CLI 2.31.32 Command Reference](../../index.html) » + * [AWS CLI 2.31.35 Command Reference](../../index.html) »