AWS controlcatalog documentation change
Summary
Updated service name references from 'AWS Control Catalog' to 'Control Catalog' throughout the documentation
Security assessment
The changes are branding/naming adjustments rather than security fixes. The documentation continues to describe security-relevant PrivateLink configuration, but no specific vulnerabilities or security incidents are addressed. The security implications remain unchanged - PrivateLink endpoint configuration remains a security best practice for network isolation.
Diff
diff --git a/controlcatalog/latest/userguide/vpc-interface-endpoints.md b/controlcatalog/latest/userguide/vpc-interface-endpoints.md index add49f854..18c260ba2 100644 --- a//controlcatalog/latest/userguide/vpc-interface-endpoints.md +++ b//controlcatalog/latest/userguide/vpc-interface-endpoints.md @@ -7 +7 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -# Access AWS Control Catalog using an interface endpoint (AWS PrivateLink) +# Access Control Catalog using an interface endpoint (AWS PrivateLink) @@ -9 +9 @@ ConsiderationsCreate an interface endpointCreate an endpoint policy -You can use AWS PrivateLink to create a private connection between your VPC and AWS Control Catalog. You can access AWS Control Catalog as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access AWS Control Catalog. +You can use AWS PrivateLink to create a private connection between your VPC and Control Catalog. You can access AWS Control Catalog as if it were in your VPC, without the use of an internet gateway, NAT device, VPN connection, or AWS Direct Connect connection. Instances in your VPC don't need public IP addresses to access Control Catalog. @@ -11 +11 @@ You can use AWS PrivateLink to create a private connection between your VPC and -You establish this private connection by creating an _interface endpoint_ , powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for AWS Control Catalog. +You establish this private connection by creating an _interface endpoint_ , powered by AWS PrivateLink. We create an endpoint network interface in each subnet that you enable for the interface endpoint. These are requester-managed network interfaces that serve as the entry point for traffic destined for Control Catalog. @@ -17 +17 @@ For more information, see [Access AWS services through AWS PrivateLink](https:// -Before you set up an interface endpoint for AWS Control Catalog, review [Considerations](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the _AWS PrivateLink Guide_. +Before you set up an interface endpoint for Control Catalog, review [Considerations](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#considerations-interface-endpoints) in the _AWS PrivateLink Guide_. @@ -19 +19 @@ Before you set up an interface endpoint for AWS Control Catalog, review [Conside -AWS Control Catalog supports making calls to all of its API actions through the interface endpoint. +Control Catalog supports making calls to all of its API actions through the interface endpoint. @@ -21 +21 @@ AWS Control Catalog supports making calls to all of its API actions through the -## Create an interface endpoint for AWS Control Catalog +## Create an interface endpoint for Control Catalog @@ -23 +23 @@ AWS Control Catalog supports making calls to all of its API actions through the -You can create an interface endpoint for AWS Control Catalog using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Create an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint-aws) in the _AWS PrivateLink Guide_. +You can create an interface endpoint for Control Catalog using either the Amazon VPC console or the AWS Command Line Interface (AWS CLI). For more information, see [Create an interface endpoint](https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html#create-interface-endpoint-aws) in the _AWS PrivateLink Guide_. @@ -25 +25 @@ You can create an interface endpoint for AWS Control Catalog using either the Am -Create an interface endpoint for AWS Control Catalog using the following service name: +Create an interface endpoint for Control Catalog using the following service name: @@ -30 +30 @@ Create an interface endpoint for AWS Control Catalog using the following service -If you enable private DNS for the interface endpoint, you can make API requests to AWS Control Catalog using its default Regional DNS name. For example, `service-name.us-east-1.amazonaws.com`. +If you enable private DNS for the interface endpoint, you can make API requests to Control Catalog using its default Regional DNS name. For example, `service-name.us-east-1.amazonaws.com`. @@ -34 +34 @@ If you enable private DNS for the interface endpoint, you can make API requests -An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy allows full access to AWS Control Catalog through the interface endpoint. To control the access allowed to AWS Control Catalog from your VPC, attach a custom endpoint policy to the interface endpoint. +An endpoint policy is an IAM resource that you can attach to an interface endpoint. The default endpoint policy allows full access to Control Catalog through the interface endpoint. To control the access allowed to Control Catalog from your VPC, attach a custom endpoint policy to the interface endpoint. @@ -49 +49 @@ For more information, see [Control access to services using endpoint policies](h -###### Example: VPC endpoint policy for AWS Control Catalog actions +###### Example: VPC endpoint policy for Control Catalog actions