2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
If you want VPC A accesses the private IPv4 addresses of VPC B through VPC peering, you can enable DNS resolution support for a VPC peering connection. After that, you can resolve to the private DNS IP address of redshift
link:https://docs.aws.amazon.com/vpc/latest/peering/modify-peering-connections.html#vpc-peering-dns
répondu il y a 3 ans
0
Now that Amazon Redshift supports cross-VPC access using Amazon Redshift-managed VPC endpoints, you can configure Amazon Redshift clusters to expose additional endpoints running on public or private subnets within the same VPC, different VPC, or different AWS accounts, which enables you to add an additional layer of security to access your clusters regardless of where they run, with no infrastructure to manage
répondu il y a 7 mois
Contenus pertinents
- demandé il y a un an
- demandé il y a 6 mois
- demandé il y a 2 mois
- AWS OFFICIELA mis à jour il y a 9 mois
- AWS OFFICIELA mis à jour il y a un an
- AWS OFFICIELA mis à jour il y a 2 ans