#AwsPrivatelink hashtag - Bluesky

@awsnews.bsky.social

3 months ago

Amazon Cognito identity pools now support private connectivity with AWS PrivateLink Amazon Cognito identity pools now support AWS PrivateLink, enabling you to securely exchange federated identities for AWS credentials through private connectivity between your virtual private cloud (VPC) and Cognito. This eliminates the need to route authentication traffic over the public internet, providing enhanced security for your workloads. Identity pools map authenticated and guest identities to your AWS Identity and Access Management (IAM) roles and provide temporary AWS credentials, with this new feature, through a secure and private connection. You can use PrivateLink connections in all AWS Regions where Amazon Cognito identity pools are available, except AWS China (Beijing) Region, operated by Sinnet, and AWS GovCloud (US) Regions. Creating VPC endpoints on AWS PrivateLink will incur additional charges; refer to https://aws.amazon.com/privatelink/pricing/ for details. You can get started by creating an AWS PrivateLink VPC interface endpoint for Amazon Cognito identity pools using the AWS Management Console, AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), AWS Cloud Development Kit (CDK), or AWS CloudFormation. To learn more, refer to the documentation on https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html and https://docs.aws.amazon.com/cognito/latest/developerguide/vpc-interface-endpoints.html.

Amazon Cognito identity pools now support private connectivity with AWS PrivateLink

Amazon Cognito identity pools now support AWS PrivateLink, enabling you to securely exchange federated identities for AWS credentials through private connectivity between yo...

#AWS #AmazonCognito #AwsPrivatelink

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

3 months ago

Amazon Cognito identity pools now support private connectivity with AWS PrivateLink Amazon Cognito identity pools now support AWS PrivateLink, enabling you to securely exchange federated identities for AWS credentials through private connectivity between your virtual private cloud (VPC) and Cognito. This eliminates the need to route authentication traffic over the public internet, providing enhanced security for your workloads. Identity pools map authenticated and guest identities to your AWS Identity and Access Management (IAM) roles and provide temporary AWS credentials, with this new feature, through a secure and private connection. You can use PrivateLink connections in all AWS Regions where Amazon Cognito identity pools are available, except AWS China (Beijing) Region, operated by Sinnet, and AWS GovCloud (US) Regions. Creating VPC endpoints on AWS PrivateLink will incur additional charges; refer to AWS PrivateLink pricing page for details. You can get started by creating an AWS PrivateLink VPC interface endpoint for Amazon Cognito identity pools using the AWS Management Console, AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), AWS Cloud Development Kit (CDK), or AWS CloudFormation. To learn more, refer to the documentation on creating a VPC interface endpoint and Amazon Cognito’s developer guide.

🆕 Amazon Cognito identity pools now support AWS PrivateLink for secure, private connectivity, eliminating public internet use. VPC endpoints are available in most regions, excluding AWS China and GovCloud, with additional charges. Use AWS tools to create endpoi…

#AWS #AmazonCognito #AwsPrivatelink

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

4 months ago

AWS PrivateLink now supports cross-region connectivity for AWS Services AWS PrivateLink now supports native cross-region connectivity to AWS services. Until now, Interface VPC endpoints only supported connectivity to AWS services in the same Region. This launch enables customers to connect to select AWS services hosted in other Regions of the same AWS https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/partitions.html#:~:text=AWS%20groups%20Regions%20into%20partitions,resources%20in%20a%20different%20partition.https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/partitions.html#:~:text=AWS%20groups%20Regions%20into%20partitions,resources%20in%20a%20different%20partition. over Interface endpoints. As a service consumer, you can access Amazon S3, Route53, Elastic Container Registry (ECR) and other services, privately without the need to setup cross-region peering or exposing your data over the public internet. These services can be accessed through Interface endpoints at a private IP address in your VPC, enabling simpler and more secure inter-region connectivity. This feature helps you build globally distributed private networks that comply with data residency requirements, while accessing supported AWS Services through PrivateLink To learn about pricing for this feature, please see the https://aws.amazon.com/privatelink/pricing/. For a complete list of supported AWS services and Regions, please refer to our https://docs.aws.amazon.com/vpc/latest/privatelink/aws-services-cross-region-privatelink-support.html and https://aws.amazon.com/blogs/networking-and-content-delivery/aws-privatelink-extends-cross-region-connectivity-to-aws-services/. To learn more, visit https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html in the Amazon VPC Developer Guide.

AWS PrivateLink now supports cross-region connectivity for AWS Services

AWS PrivateLink now supports native cross-region connectivity to AWS services. Until now, Interface VPC endpoints only supported connectivity to AWS services in the same Region. This launch enables cu...

#AWS #AwsPrivatelink

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

5 months ago

Amazon Cognito user pools now supports private connectivity with AWS PrivateLink Amazon Cognito user pools now supports AWS PrivateLink for secure and private connectivity. With AWS PrivateLink, you can establish a private connection between your virtual private cloud (VPC) and Amazon Cognito user pools to configure, manage, and authenticate against your Cognito user pools without using the public internet. By enabling private network connectivity, this enhancement eliminates the need to use public IP addresses or relying solely on firewall rules to access Cognito. This feature supports user pool management operations (e.g., list user pools, describe user pools), administrative operations (e.g., admin-created users), and user authentication flows (sign in local users stored in Cognito). OAuth 2.0 authorization code flow (Cognito managed login, hosted UI, sign-in via social identity providers), client credentials flow (Cognito machine-to-machine authorization), and federated sign-ins via SAML and OIDC standards are not supported through VPC endpoints at this time. You can use PrivateLink connections in all AWS Regions where Amazon Cognito user pools is available, except AWS GovCloud (US) Regions. Creating VPC endpoints on AWS PrivateLink will incur additional charges; refer to https://aws.amazon.com/privatelink/pricing/ for details. You can get started by creating an AWS PrivateLink interface endpoint for Amazon Cognito user pools using the AWS Management Console, AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), AWS Cloud Development Kit (CDK), or AWS CloudFormation. To learn more, refer to the documentation on https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.htmlhttps://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.htmland https://docs.aws.amazon.com/cognito/latest/developerguide/vpc-interface-endpoints.html.

Amazon Cognito user pools now supports private connectivity with AWS PrivateLink

Amazon Cognito user pools now supports AWS PrivateLink for secure and private connectivity. With AWS PrivateLink, you can establish a private connection between your virtual pr...

#AWS #AmazonCognito #AwsPrivatelink

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

5 months ago

Amazon Cognito user pools now supports private connectivity with AWS PrivateLink Amazon Cognito user pools now supports AWS PrivateLink for secure and private connectivity. With AWS PrivateLink, you can establish a private connection between your virtual private cloud (VPC) and Amazon Cognito user pools to configure, manage, and authenticate against your Cognito user pools without using the public internet. By enabling private network connectivity, this enhancement eliminates the need to use public IP addresses or relying solely on firewall rules to access Cognito. This feature supports user pool management operations (e.g., list user pools, describe user pools), administrative operations (e.g., admin-created users), and user authentication flows (sign in local users stored in Cognito). OAuth 2.0 authorization code flow (Cognito managed login, hosted UI, sign-in via social identity providers), client credentials flow (Cognito machine-to-machine authorization), and federated sign-ins via SAML and OIDC standards are not supported through VPC endpoints at this time. You can use PrivateLink connections in all AWS Regions where Amazon Cognito user pools is available, except AWS GovCloud (US) Regions. Creating VPC endpoints on AWS PrivateLink will incur additional charges; refer to AWS PrivateLink pricing page for details. You can get started by creating an AWS PrivateLink interface endpoint for Amazon Cognito user pools using the AWS Management Console, AWS Command Line Interface (CLI), AWS Software Development Kits (SDKs), AWS Cloud Development Kit (CDK), or AWS CloudFormation. To learn more, refer to the documentation on creating an interface VPC endpoint and Amazon Cognito’s developer guide.

🆕 Amazon Cognito user pools now support AWS PrivateLink for secure private connectivity, eliminating public internet use. VPC endpoints enable private access for management and user auth, excluding OAuth 2.0. Available in all regions except AWS GovCloud (US). A…

#AWS #AmazonCognito #AwsPrivatelink

2 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

5 months ago

Amazon VPC Lattice now supports custom domain names for resource configurations Starting today, VPC Lattice allows you to specify a custom domain name for a resource configuration. Resource configurations enable layer-4 access to resources such as databases, clusters, domain names, etc. across VPCs and accounts. With this feature, you can use resource configurations for cluster-based and TLS-based resources. Resource owners can use this feature by specifying a custom domain for a resource configuration and sharing the resource configuration with consumers. Consumers can then access the resource using the custom domain, with VPC Lattice managing a private hosted zone in the consumer’s VPC. This feature also provides resource owners and consumers control and flexibility over the domains they want to use. Resource owners can use a custom domain owned by them, or AWS, or a third-party. Consumers can use granular controls to choose which domains they want VPC Lattice to manage private hosted zones for. This feature is available at no additional cost in all AWS Regions where VPC Lattice resource configuration is available. For more information, please read our https://aws.amazon.com/blogs/networking-and-content-delivery/custom-domain-names-for-vpc-lattice-resources/or visit the https://aws.amazon.com/vpc/lattice/ andhttps://docs.aws.amazon.com/vpc-lattice/latest/ug/resource-configuration.html.

Amazon VPC Lattice now supports custom domain names for resource configurations

Starting today, VPC Lattice allows you to specify a custom domain name for a resource configuration. Resource configurations enable layer-4 access to resources such as databases, clusters, dom...

#AWS #AwsPrivatelink

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

5 months ago

Amazon VPC Lattice now supports custom domain names for resource configurations Starting today, VPC Lattice allows you to specify a custom domain name for a resource configuration. Resource configurations enable layer-4 access to resources such as databases, clusters, domain names, etc. across VPCs and accounts. With this feature, you can use resource configurations for cluster-based and TLS-based resources. Resource owners can use this feature by specifying a custom domain for a resource configuration and sharing the resource configuration with consumers. Consumers can then access the resource using the custom domain, with VPC Lattice managing a private hosted zone in the consumer’s VPC. This feature also provides resource owners and consumers control and flexibility over the domains they want to use. Resource owners can use a custom domain owned by them, or AWS, or a third-party. Consumers can use granular controls to choose which domains they want VPC Lattice to manage private hosted zones for. This feature is available at no additional cost in all AWS Regions where VPC Lattice resource configuration is available. For more information, please read our blog or visit the Amazon VPC Lattice product detail page and Amazon VPC Lattice documentation.

🆕 Amazon VPC Lattice now supports custom domain names for resource configurations, enabling resource owners to specify and share custom domains for cluster-based and TLS-based resources across VPCs and accounts, at no additional cost.

#AWS #AwsPrivatelink

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

5 months ago

Amazon DynamoDB Streams expands AWS PrivateLink support to FIPS endpoints Amazon DynamoDB Streams now supports AWS PrivateLink for all available Amazon DynamoDB Streams Federal Information Processing Standard (FIPS) endpoints in US and Canada commercial AWS Regions. With this launch, you can establish a private connection between your virtual private cloud (VPC) and Amazon DynamoDB Streams FIPS endpoints instead of connecting over the public internet, helping you meet your organization's business, compliance, and regulatory requirements to limit public internet connectivity. Amazon DynamoDB Streams support for AWS PrivateLink FIPs endpoints is available with Amazon DynamoDB Streams in the US and Canada commercial AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), and Canada West (Calgary). To learn more about Amazon DynamoDB Streams support for AWS PrivateLink FIPs endpoints, visit thehttps://docs.aws.amazon.com/amazondynamodb/latest/developerguide/privatelink-streams.html. For more information about AWS PrivateLink and its benefits, visit the https://aws.amazon.com/privatelink/.

Amazon DynamoDB Streams expands AWS PrivateLink support to FIPS endpoints

Amazon DynamoDB Streams now supports AWS PrivateLink for all available Amazon DynamoDB Streams Federal Information Processing Standard (FIPS) endpoints in US and Canada commercial AW...

#AWS #AwsPrivatelink #AmazonDynamodb

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

5 months ago

Amazon DynamoDB Streams expands AWS PrivateLink support to FIPS endpoints Amazon DynamoDB Streams now supports AWS PrivateLink for all available Amazon DynamoDB Streams Federal Information Processing Standard (FIPS) endpoints in US and Canada commercial AWS Regions. With this launch, you can establish a private connection between your virtual private cloud (VPC) and Amazon DynamoDB Streams FIPS endpoints instead of connecting over the public internet, helping you meet your organization's business, compliance, and regulatory requirements to limit public internet connectivity. Amazon DynamoDB Streams support for AWS PrivateLink FIPs endpoints is available with Amazon DynamoDB Streams in the US and Canada commercial AWS Regions: US East (N. Virginia), US East (Ohio), US West (N. California), US West (Oregon), Canada (Central), and Canada West (Calgary). To learn more about Amazon DynamoDB Streams support for AWS PrivateLink FIPs endpoints, visit the Amazon DynamoDB Stream documentation. For more information about AWS PrivateLink and its benefits, visit the AWS PrivateLink product page.

🆕 Amazon DynamoDB Streams now supports AWS PrivateLink for FIPS endpoints in US and Canada, enabling private VPC connections to meet compliance and regulatory needs, available in select regions.

#AWS #AwsPrivatelink #AmazonDynamodb

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

5 months ago

AWS PrivateLink now supports cross-region connectivity for AWS Services AWS PrivateLink now supports native cross-region connectivity to AWS services. Until now, Interface VPC endpoints only supported connectivity to AWS services in the same Region. This launch enables customers to connect to select AWS services hosted in other Regions of the same AWS https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/partitions.html#:~:text=AWS%20groups%20Regions%20into%20partitions,resources%20in%20a%20different%20partition.https://docs.aws.amazon.com/whitepapers/latest/aws-fault-isolation-boundaries/partitions.html#:~:text=AWS%20groups%20Regions%20into%20partitions,resources%20in%20a%20different%20partition. over Interface endpoints. As a service consumer, you can access Amazon S3, Route53, Elastic Container Registry (ECR) and other services, privately without the need to setup cross-region peering or exposing your data over the public internet. These services can be accessed through Interface endpoints at a private IP address in your VPC, enabling simpler and more secure inter-region connectivity. This feature helps you build globally distributed private networks that comply with data residency requirements, while accessing supported AWS Services through PrivateLink To learn about pricing for this feature, please see the https://aws.amazon.com/privatelink/pricing/. For a complete list of supported AWS services and Regions, please refer to our documentation [link TBD]. To learn more, visit https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html in the Amazon VPC Developer Guide.

AWS PrivateLink now supports cross-region connectivity for AWS Services

AWS PrivateLink now supports native cross-region connectivity to AWS services. Until now, Interface VPC endpoints only supported connectivity to AWS services in the same Region. This launch enables cu...

#AWS #AwsPrivatelink

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

5 months ago

AWS PrivateLink now supports cross-region connectivity for AWS Services AWS PrivateLink now supports native cross-region connectivity to AWS services. Until now, Interface VPC endpoints only supported connectivity to AWS services in the same Region. This launch enables customers to connect to select AWS services hosted in other Regions of the same AWS partition over Interface endpoints. As a service consumer, you can access Amazon S3, Route53, Elastic Container Registry (ECR) and other services, privately without the need to setup cross-region peering or exposing your data over the public internet. These services can be accessed through Interface endpoints at a private IP address in your VPC, enabling simpler and more secure inter-region connectivity. This feature helps you build globally distributed private networks that comply with data residency requirements, while accessing supported AWS Services through PrivateLink To learn about pricing for this feature, please see the AWS PrivateLink pricing page. For a complete list of supported AWS services and Regions, please refer to our documentation [link TBD]. To learn more, visit AWS PrivateLink in the Amazon VPC Developer Guide.

🆕 AWS PrivateLink now supports cross-region connectivity for AWS services, enabling secure access to select services like S3 and Route53 without public internet exposure. Interface VPC endpoints now connect to services in different regions, simplifying global private networks.

#AWS #AwsPrivatelink

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

6 months ago

Amazon VPC Lattice now supports configurable IP addresses for Resource Gateways Starting today, Amazon VPC Lattice lets you configure the number of IPv4 addresses assigned to resource gateway elastic network interfaces (ENIs). This enhancement builds on VPC Lattice's capability of providing access to resources on Layer-4 such as databases, clusters, domain names, etc. across multiple VPCs and accounts. When configuring a resource gateway, you can now specify the number of IPv4 addresses per ENI, which becomes immutable after setting. The IPv4 addresses are used for network address translation and determine the maximum number of concurrent IPv4 connections to a resource. You should consider your expected connection volume when configuring the IPv4 address count. By default, VPC Lattice assigns 16 IPv4 addresses per ENI. For IPv6, VPC Lattice always assigns a /80 CIDR per ENI. This feature is available at no additional cost in all AWS Regions where VPC Lattice is offered. For more information, visit the https://aws.amazon.com/vpc/lattice/ and https://docs.aws.amazon.com/vpc-lattice/latest/ug/resource-gateway.html#ipv4-address-type-per-eni.

Amazon VPC Lattice now supports configurable IP addresses for Resource Gateways

Starting today, Amazon VPC Lattice lets you configure the number of IPv4 addresses assigned to resource gateway elastic network interfaces (ENIs). This enhancement b...

#AWS #AmazonVirtualPrivateCloud #AwsPrivatelink

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

6 months ago

Amazon VPC Lattice now supports configurable IP addresses for Resource Gateways Starting today, Amazon VPC Lattice lets you configure the number of IPv4 addresses assigned to resource gateway elastic network interfaces (ENIs). This enhancement builds on VPC Lattice's capability of providing access to resources on Layer-4 such as databases, clusters, domain names, etc. across multiple VPCs and accounts. When configuring a resource gateway, you can now specify the number of IPv4 addresses per ENI, which becomes immutable after setting. The IPv4 addresses are used for network address translation and determine the maximum number of concurrent IPv4 connections to a resource. You should consider your expected connection volume when configuring the IPv4 address count. By default, VPC Lattice assigns 16 IPv4 addresses per ENI. For IPv6, VPC Lattice always assigns a /80 CIDR per ENI. This feature is available at no additional cost in all AWS Regions where VPC Lattice is offered. For more information, visit the Amazon VPC Lattice product detail page and Amazon VPC Lattice documentation.

🆕 Amazon VPC Lattice now allows configuring IPv4 addresses for resource gateway ENIs, enhancing Layer-4 access across VPCs. Specify IPv4 count per ENI, default 16, with no extra cost. Available in all VPC Lattice regions.

#AWS #AmazonVirtualPrivateCloud #AwsPrivatelink

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

6 months ago

Amazon Detective now supports AWS PrivateLink for private API access Amazon Detective now supports Amazon Virtual Private Cloud (VPC) endpoints via AWS https://aws.amazon.com/privatelink/, enabling you to securely initiate API calls to Detective from within your VPC without requiring Internet traversal. AWS PrivateLink support for Detective is available in all AWS Regions where Detective is available (see the https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ table). To try the new feature, you can create a VPC endpoint for Detective through the VPC console, API, or SDK. This creates an elastic network interface in your specified subnets. The interface has a private IP address that serves as an entry point for traffic destined for Detective. You can read more about Detective's integration with PrivateLink https://docs.aws.amazon.com/detective/latest/userguide/detective-security-vpc-endpoints-privatelink.htmlhttps://docs.aws.amazon.com/detective/latest/userguide/detective-security-vpc-endpoints-privatelink.html. Amazon Detective automatically collects log data from your AWS resources and uses machine learning, statistical analysis, and graph theory to build interactive visualizations that enable you to conduct faster and more efficient security investigations. Detective analyzes trillions of events from multiple data sources like Amazon Virtual Private Cloud (Amazon VPC) Flow Logs, AWS CloudTrail logs, Amazon Elastic Kubernetes Service (Amazon EKS) audit logs, and findings from multiple AWS security services to create a unified, interactive view of security events. Detective also automatically groups related findings from Amazon GuardDuty, AWS Security Hub and Amazon Inspector to show you combined threats and vulnerabilities to help security analysts identify and prioritize potential high-severity security risks. To get started, see the https://docs.aws.amazon.com/detective/latest/userguide/what-is-detective.html

Amazon Detective now supports AWS PrivateLink for private API access

Amazon Detective now supports Amazon Virtual Private Cloud (VPC) endpoints via AWS https://aws.amazon.com/privatelink/ enabling you to securely initiate API calls to Dete...

#AWS #AmazonDetective #AwsGovcloudUs #AwsPrivatelink

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

6 months ago

Amazon Detective now supports AWS PrivateLink for private API access Amazon Detective now supports Amazon Virtual Private Cloud (VPC) endpoints via AWS PrivateLink, enabling you to securely initiate API calls to Detective from within your VPC without requiring Internet traversal. AWS PrivateLink support for Detective is available in all AWS Regions where Detective is available (see the AWS Region table). To try the new feature, you can create a VPC endpoint for Detective through the VPC console, API, or SDK. This creates an elastic network interface in your specified subnets. The interface has a private IP address that serves as an entry point for traffic destined for Detective. You can read more about Detective's integration with PrivateLink here. Amazon Detective automatically collects log data from your AWS resources and uses machine learning, statistical analysis, and graph theory to build interactive visualizations that enable you to conduct faster and more efficient security investigations. Detective analyzes trillions of events from multiple data sources like Amazon Virtual Private Cloud (Amazon VPC) Flow Logs, AWS CloudTrail logs, Amazon Elastic Kubernetes Service (Amazon EKS) audit logs, and findings from multiple AWS security services to create a unified, interactive view of security events. Detective also automatically groups related findings from Amazon GuardDuty, AWS Security Hub and Amazon Inspector to show you combined threats and vulnerabilities to help security analysts identify and prioritize potential high-severity security risks. To get started, see the Amazon Detective User Guide

🆕 Amazon Detective now supports AWS PrivateLink for private API access within VPC, eliminating internet traversal. Available in all regions, create a VPC endpoint via console, API, or SDK for secure Detective API calls.

#AWS #AmazonDetective #AwsGovcloudUs #AwsPrivatelink

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

7 months ago

AWS Certificate Manager supports AWS PrivateLink AWS Certificate Manager (ACM) now supports https://aws.amazon.com/privatelink/ so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public internet. This feature can help you meet compliance requirements by allowing you to access and use ACM APIs entirely within the AWS network. ACM simplifies the process of provisioning and managing public and private TLS certificates, wherever you need to securely terminate traffic; Whether it’s with integrated AWS services such as Amazon CloudFront, Load Balancing or with hybrid workloads. You can now create interface endpoints in AWS Private Link to connect your VPC to ACM. Communication between your VPC and ACM is then conducted entirely within the AWS network, providing a secure pathway for your data. To get started, you can create an AWS PrivateLink to connect to ACM using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands or AWS CloudFormation. This new feature is available in all https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/ including AWS GovCloud (US) and China Regions where AWS Certificate Manager Service and AWS PrivateLink are available. For more information, please refer to the AWS PrivateLink https://docs.aws.amazon.com/vpc/latest/privatelink/create-interface-endpoint.html.

AWS Certificate Manager supports AWS PrivateLink

AWS Certificate Manager (ACM) now supports https://aws.amazon.com/privatelink/ so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public...

#AWS #AwsPrivatelink #AwsGovcloudUs #AwsCertificateManager

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

7 months ago

AWS Certificate Manager supports AWS PrivateLink AWS Certificate Manager (ACM) now supports AWS PrivateLink so that you can access ACM APIs from your Amazon Virtual Private Cloud (VPC) without traversing the public internet. This feature can help you meet compliance requirements by allowing you to access and use ACM APIs entirely within the AWS network. ACM simplifies the process of provisioning and managing public and private TLS certificates, wherever you need to securely terminate traffic; Whether it’s with integrated AWS services such as Amazon CloudFront, Load Balancing or with hybrid workloads. You can now create interface endpoints in AWS Private Link to connect your VPC to ACM. Communication between your VPC and ACM is then conducted entirely within the AWS network, providing a secure pathway for your data. To get started, you can create an AWS PrivateLink to connect to ACM using the AWS Management Console or AWS Command Line Interface (AWS CLI) commands or AWS CloudFormation. This new feature is available in all AWS Regions including AWS GovCloud (US) and China Regions where AWS Certificate Manager Service and AWS PrivateLink are available. For more information, please refer to the AWS PrivateLink documentation.

🆕 AWS ACM now supports AWS PrivateLink for secure, private access to ACM APIs within your VPC, avoiding public internet. Available everywhere, create endpoints via console, CLI, or CloudFormation.

#AWS #AwsPrivatelink #AwsGovcloudUs #AwsCertificateManager

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

9 months ago

Amazon WorkSpaces Personal now supports PrivateLink for streaming traffic Amazon WorkSpaces Personal now allows you to route streaming traffic privately between your Amazon Virtual Private Cloud (VPC) and WorkSpaces virtual desktops using https://docs.aws.amazon.com/vpc/latest/privatelink/what-is-privatelink.html, without the data ever traversing the public internet. With this new capability, you can now stream your WorkSpaces through private IP addresses within your VPC, or from on-premises environments using AWS VPN or AWS Direct Connect. The feature helps you to meet your compliance requirements by keeping streaming traffic within the trusted networks. To get started using PrivateLink with WorkSpaces, create a WorkSpaces VPC endpoint for DCV streaming protocol in the chosen Amazon VPC, then specify the VPC endpoint when creating a new WorkSpaces Personal directory or modifying an existing one. Your users will then use the VPC endpoint when they stream their DCV WorkSpaces. The feature is available for WorkSpaces Personal running DCV protocol in all AWS Regions https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/, except China (Ningxia) Region. You can configure this feature through the AWS Management Console, AWS Command Line Interface (CLI), or Amazon WorkSpaces APIs. For detailed configuration instructions and requirements, please refer to the https://docs.aws.amazon.com/workspaces/latest/adminguide/creating-streaming-vpc-endpoints.html.

Amazon WorkSpaces Personal now supports PrivateLink for streaming traffic

Amazon WorkSpaces Personal now allows you to route streaming traffic privately between your Amazon Virtual Private Cloud (VPC) and WorkSpaces virtual desktops using ...

#AWS #AwsPrivatelink #AwsGovcloudUs #AmazonWorkspaces

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

9 months ago

Amazon WorkSpaces Personal now supports PrivateLink for streaming traffic Amazon WorkSpaces Personal now allows you to route streaming traffic privately between your Amazon Virtual Private Cloud (VPC) and WorkSpaces virtual desktops using AWS PrivateLink, without the data ever traversing the public internet. With this new capability, you can now stream your WorkSpaces through private IP addresses within your VPC, or from on-premises environments using AWS VPN or AWS Direct Connect. The feature helps you to meet your compliance requirements by keeping streaming traffic within the trusted networks. To get started using PrivateLink with WorkSpaces, create a WorkSpaces VPC endpoint for DCV streaming protocol in the chosen Amazon VPC, then specify the VPC endpoint when creating a new WorkSpaces Personal directory or modifying an existing one. Your users will then use the VPC endpoint when they stream their DCV WorkSpaces. The feature is available for WorkSpaces Personal running DCV protocol in all AWS Regions where Amazon WorkSpaces is supported, except China (Ningxia) Region. You can configure this feature through the AWS Management Console, AWS Command Line Interface (CLI), or Amazon WorkSpaces APIs. For detailed configuration instructions and requirements, please refer to the Amazon WorkSpaces documentation.

🆕 Amazon WorkSpaces Personal now supports AWS PrivateLink for private streaming, keeping data secure within trusted networks. Available in all regions except China (Ningxia), it uses VPC endpoints for DCV streaming. Configure via console, CLI,…

#AWS #AwsPrivatelink #AwsGovcloudUs #AmazonWorkspaces

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

10 months ago

AWS Resource Groups adds support AWS PrivateLink AWS Resource Group APIs now come with https://aws.amazon.com/privatelink/ support, allowing you to invoke AWS Resource Group APIs from within your Amazon Virtual Private Cloud (VPC) without traversing the public internet. AWS Resource Groups enables you to model, manage and automate tasks on large numbers of AWS resources by using tags to logically group your resources. You can create logical collections of resources such as applications, projects, and cost centers, and manage them on dimensions such as cost, performance, and compliance in AWS services such as myApplications, AWS Systems Manager and Amazon CloudWatch. AWS PrivateLink support for AWS Resource Groups is available in all AWS Regions where AWS Resource Groups is available. To get started, follow the directions provided in the https://docs.aws.amazon.com/en_us/vpc/latest/privatelink/privatelink-access-aws-services.html or visit https://docs.aws.amazon.com/ARG/latest/userguide/vpc-interface-endpoints.html.

AWS Resource Groups adds support AWS PrivateLink

AWS Resource Group APIs now come with https://aws.amazon.com/privatelink/ support, allowing you to invoke AWS Resource Group APIs from within your Amazon Virtual Private Cloud (VPC) without...

#AWS #AwsPrivatelink #AwsGovcloudUs #AwsResourceGroups

1 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

10 months ago

AWS Resource Groups adds support AWS PrivateLink AWS Resource Group APIs now come with AWS PrivateLink support, allowing you to invoke AWS Resource Group APIs from within your Amazon Virtual Private Cloud (VPC) without traversing the public internet. AWS Resource Groups enables you to model, manage and automate tasks on large numbers of AWS resources by using tags to logically group your resources. You can create logical collections of resources such as applications, projects, and cost centers, and manage them on dimensions such as cost, performance, and compliance in AWS services such as myApplications, AWS Systems Manager and Amazon CloudWatch. AWS PrivateLink support for AWS Resource Groups is available in all AWS Regions where AWS Resource Groups is available. To get started, follow the directions provided in the AWS PrivateLink documentation or visit AWS Resource Groups.

🆕 AWS Resource Groups now support AWS PrivateLink for private API calls within VPCs, no public internet. Manage groups by tags for apps, projects, and cost centers across services, available in all regions.

#AWS #AwsPrivatelink #AwsGovcloudUs #AwsResourceGroups

1 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

10 months ago

Amazon Lightsail now supports IPv6 connectivity over AWS PrivateLink Amazon Lightsail now supports IPv6-only and dual-stack PrivateLink interface VPC endpoints. AWS PrivateLink is a highly available, scalable service that allows you to privately connect your VPC to services and resources as if they were in your VPC. Previously, Lightsail supported private connectivity over PrivateLink using IPv4-only VPC endpoints. With today’s launch, customers can use IPv6-only, IPv4-only, or dual-stack VPC endpoints to create a private connection between their VPC and Lightsail, and access Lightsail without traversing the public internet. Lightsail supports connectivity using PrivateLink in all AWS Regions supporting Lightsail. To learn more about accessing Lightsail using PrivateLink, https://docs.aws.amazon.com/lightsail/latest/userguide/vpc-interface-endpoints.html.

Amazon Lightsail now supports IPv6 connectivity over AWS PrivateLink

Amazon Lightsail now supports IPv6-only and dual-stack PrivateLink interface VPC endpoints. AWS PrivateLink is a highly available, scalable service that allows you to privately connect y...

#AWS #AwsPrivatelink #AmazonLightsail

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

10 months ago

Amazon Lightsail now supports IPv6 connectivity over AWS PrivateLink Amazon Lightsail now supports IPv6-only and dual-stack PrivateLink interface VPC endpoints. AWS PrivateLink is a highly available, scalable service that allows you to privately connect your VPC to services and resources as if they were in your VPC. Previously, Lightsail supported private connectivity over PrivateLink using IPv4-only VPC endpoints. With today’s launch, customers can use IPv6-only, IPv4-only, or dual-stack VPC endpoints to create a private connection between their VPC and Lightsail, and access Lightsail without traversing the public internet. Lightsail supports connectivity using PrivateLink in all AWS Regions supporting Lightsail. To learn more about accessing Lightsail using PrivateLink, please see documentation.

🆕 Amazon Lightsail now supports IPv6 connectivity via AWS PrivateLink, allowing IPv6-only, IPv4-only, or dual-stack VPC endpoints for private VPC connections, eliminating public internet traversal. Available in all Lightsail-supporting regions.

#AWS #AwsPrivatelink #AmazonLightsail

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

11 months ago

Amazon ElastiCache now supports AWS PrivateLink in the AWS Europe (Spain) Region You can now use https://aws.amazon.com/privatelink/ to privately access https://aws.amazon.com/elasticache/ from your Amazon Virtual Private Cloud (Amazon VPC) in the AWS Europe (Spain) Region. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises networks, without exposing traffic to the public internet and securing your network traffic. To use AWS PrivateLink with Amazon ElastiCache, you create an https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html for Amazon ElastiCache in your VPC using the Amazon VPC console, AWS SDK, or AWS CLI. With an interface VPC endpoint, you can privately access the Amazon ElastiCache APIs from applications inside your Amazon VPC. You can also access the VPC endpoint from other VPCs using VPC Peering or your on-premises environments using AWS VPN or AWS Direct Connect. To learn more, read the http://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/elasticache-privatelink.html, or get started in the https://console.aws.amazon.com/vpc/home.

Amazon ElastiCache now supports AWS PrivateLink in the AWS Europe (Spain) Region

You can now use https://aws.amazon.com/privatelink/ to privately access https://aws.amazon.com/elasticache/ from your Amazon Virtual Private Cloud (Amazon VPC) in the AWS Europe (Spain) Regio...

#AWS #AwsPrivatelink

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

11 months ago

Amazon ElastiCache now supports AWS PrivateLink in the AWS Europe (Spain) Region You can now use AWS PrivateLink to privately access Amazon ElastiCache from your Amazon Virtual Private Cloud (Amazon VPC) in the AWS Europe (Spain) Region. AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises networks, without exposing traffic to the public internet and securing your network traffic. To use AWS PrivateLink with Amazon ElastiCache, you create an interface VPC endpoint for Amazon ElastiCache in your VPC using the Amazon VPC console, AWS SDK, or AWS CLI. With an interface VPC endpoint, you can privately access the Amazon ElastiCache APIs from applications inside your Amazon VPC. You can also access the VPC endpoint from other VPCs using VPC Peering or your on-premises environments using AWS VPN or AWS Direct Connect. To learn more, read the documentation, or get started in the Amazon VPC Console.

🆕 Amazon ElastiCache now supports AWS PrivateLink in the AWS Europe (Spain) Region, enabling private access from your VPC without exposing traffic to the public internet, enhancing security. Use the VPC console, SDK, or CLI to create an interface endpoint.

#AWS #AwsPrivatelink

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

11 months ago

Amazon Route 53 Profiles now supports VPC endpoints Today, AWS announced support for VPC endpoints in Amazon Route 53 Profiles, allowing you to create, manage, and share private hosted zones (PHZs) for interface VPC endpoints across multiple VPCs and AWS accounts within your organization. With this enhancement, Amazon Route 53 Profiles simplifies the management of VPC endpoints by streamlining the process of creating and associating interface VPC endpoint managed PHZs with VPCs and AWS accounts, and without requiring you to manually associate them. Route 53 Profiles makes it easy for you to create one or more configurations for VPC-related DNS settings, such as private hosted zones and Route 53 Resolver rules, and share them across VPCs and AWS accounts. The new capability helps you centralize the management of PHZs associated with interface VPC endpoints, reducing administrative overhead and minimizing the risk of configuration errors. This feature eliminates the need for creation and manual association of PHZs for VPC endpoints with individual VPCs and accounts, saving time and effort for network administrators. Additionally, it improves security and consistency by providing a centralized approach to managing DNS resolution for VPC endpoints across an organization's AWS infrastructure. Route 53 Profiles support for VPC endpoints is now available in the AWS Regions mentioned https://docs.aws.amazon.com/general/latest/gr/r53.html. To learn more about the capability and how it can benefit your organization, visit the Amazon Route 53 https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/profiles.html. You can get started by accessing the Amazon Route 53 console in your AWS Management Console or through AWS CLI. To learn more about pricing of Route 53 Profiles, see https://aws.amazon.com/route53/pricing/.

Amazon Route 53 Profiles now supports VPC endpoints

Today, AWS announced support for VPC endpoints in Amazon Route 53 Profiles, allowing you to create, manage, and share private hosted zones (PHZs) for interface VPC endpoints acros...

#AWS #AwsGovcloudUs #AmazonVpc #AmazonRoute53 #AwsPrivatelink

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

11 months ago

Amazon Route 53 Profiles now supports VPC endpoints Today, AWS announced support for VPC endpoints in Amazon Route 53 Profiles, allowing you to create, manage, and share private hosted zones (PHZs) for interface VPC endpoints across multiple VPCs and AWS accounts within your organization. With this enhancement, Amazon Route 53 Profiles simplifies the management of VPC endpoints by streamlining the process of creating and associating interface VPC endpoint managed PHZs with VPCs and AWS accounts, and without requiring you to manually associate them. Route 53 Profiles makes it easy for you to create one or more configurations for VPC-related DNS settings, such as private hosted zones and Route 53 Resolver rules, and share them across VPCs and AWS accounts. The new capability helps you centralize the management of PHZs associated with interface VPC endpoints, reducing administrative overhead and minimizing the risk of configuration errors. This feature eliminates the need for creation and manual association of PHZs for VPC endpoints with individual VPCs and accounts, saving time and effort for network administrators. Additionally, it improves security and consistency by providing a centralized approach to managing DNS resolution for VPC endpoints across an organization's AWS infrastructure. Route 53 Profiles support for VPC endpoints is now available in the AWS Regions mentioned here. To learn more about the capability and how it can benefit your organization, visit the Amazon Route 53 documentation. You can get started by accessing the Amazon Route 53 console in your AWS Management Console or through AWS CLI. To learn more about pricing of Route 53 Profiles, see here.

🆕 AWS now supports VPC endpoints in Route 53 Profiles, easing private hosted zone management for interface endpoints across VPCs and accounts, cutting manual tasks, and boosting security and consistency. Available in select regions.

#AWS #AwsGovcloudUs #AmazonVpc #AmazonRoute53 #AwsPrivatelink

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

11 months ago

AWS Security Incident Response now supports integration with AWS PrivateLink AWS announces AWS Security Incident Response with AWS PrivateLink integration, enabling customers to manage their service membership directly from their Amazon Virtual Private Cloud (VPC). Now, together with AWS PrivateLink, customers can access AWS Security Incident Response APIs while keeping their traffic off the public internet, adding an extra layer of security when managing and recovering from sensitive security events. This integration offers several benefits to AWS customers. First, it can improve the security perimeter of incident response processes by keeping all traffic within AWS-supported private networks. Second, it simplifies network architecture by removing the requirement for internet gateways, NAT devices, or firewall rules. Lastly, it helps meet compliance requirements that mandate private connectivity for sensitive security response and recovery, making it easier for organizations in regulated industries to adopt and use AWS Security Incident Response. AWS Security Incident Response with AWS PrivateLink integration is now available in all https://docs.aws.amazon.com/security-ir/latest/userguide/supported-configs.html. To get started with this new feature, visit the AWS Security Incident Response console or refer to the AWS Security Incident Response https://docs.aws.amazon.com/security-ir/latest/userguide/what-is.html. For more information about AWS PrivateLink, please visit the https://docs.aws.amazon.com/vpc/latest/userguide/endpoint-services-overview.html.

AWS Security Incident Response now supports integration with AWS PrivateLink

AWS announces AWS Security Incident Response with AWS PrivateLink integration, enabling customers to manage their service membership directly from their Amazon Virtual Private Cloud (VPC). Now, t...

#AWS #AwsPrivatelink

0 0 0 0

AWS News Feed on 🦋

@awsrecentnews.bsky.social

11 months ago

AWS Security Incident Response now supports integration with AWS PrivateLink AWS announces AWS Security Incident Response with AWS PrivateLink integration, enabling customers to manage their service membership directly from their Amazon Virtual Private Cloud (VPC). Now, together with AWS PrivateLink, customers can access AWS Security Incident Response APIs while keeping their traffic off the public internet, adding an extra layer of security when managing and recovering from sensitive security events. This integration offers several benefits to AWS customers. First, it can improve the security perimeter of incident response processes by keeping all traffic within AWS-supported private networks. Second, it simplifies network architecture by removing the requirement for internet gateways, NAT devices, or firewall rules. Lastly, it helps meet compliance requirements that mandate private connectivity for sensitive security response and recovery, making it easier for organizations in regulated industries to adopt and use AWS Security Incident Response. AWS Security Incident Response with AWS PrivateLink integration is now available in all service supported regions. To get started with this new feature, visit the AWS Security Incident Response console or refer to the AWS Security Incident Response documentation. For more information about AWS PrivateLink, please visit the AWS PrivateLink page.

🆕 AWS Security Incident Response now integrates with AWS PrivateLink, keeping traffic off the public internet for enhanced security, simplifying network architecture, and aiding compliance in regulated industries. Available in all supported regions.

#AWS #AwsPrivatelink

0 0 0 0

AWS News(Unofficial)

@awsnews.bsky.social

1 year ago

Amazon ElastiCache now supports AWS PrivateLink in AWS Asia Pacific (Jakarta) and Asia Pacific (Hyderabad) Regions You can now use https://aws.amazon.com/privatelink/ to privately access https://aws.amazon.com/elasticache/ from your Amazon Virtual Private Cloud (Amazon VPC). AWS PrivateLink provides private connectivity between VPCs, AWS services, and on-premises networks, without exposing traffic to the public internet and securing your network traffic. The Amazon ElastiCache API supports AWS PrivateLink in AWS Asia Pacific (Jakarta) and Asia Pacific (Hyderabad) Regions. To use AWS PrivateLink with Amazon ElastiCache, you create an https://docs.aws.amazon.com/vpc/latest/userguide/vpce-interface.html for Amazon ElastiCache in your VPC using the Amazon VPC console, AWS SDK, or AWS CLI. With an interface VPC endpoint, you can privately access the Amazon ElastiCache APIs from applications inside your Amazon VPC. You can also access the VPC endpoint from other VPCs using VPC Peering or your on-premises environments using AWS VPN or AWS Direct Connect. To learn more, read the http://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/elasticache-privatelink.html, or get started in the https://console.aws.amazon.com/vpc/home.

Amazon ElastiCache now supports AWS PrivateLink in AWS Asia Pacific (Jakarta) and Asia Pacific (Hyderabad) Regions

You can now use https://aws.amazon.com/privatelink/ to privately access https://aws.amazon.com/elasticache/ from your Amazon Virtual Priv...

#AWS #AwsPrivatelink #AmazonElasticache

0 0 0 0