- Newest
- Most votes
- Most comments
Hello.
If the private DNS name of the VPC endpoint is enabled, I think there is no need to set "endpoint_url" when creating a boto3 client.
If you enable the private DNS name of the VPC endpoint, the name resolution of the AWS service endpoint from within the VPC will be the private IP address of the VPC endpoint, so there should be no need to explicitly access it with "endpoint_url".
https://docs.aws.amazon.com/vpc/latest/privatelink/privatelink-access-aws-services.html#interface-endpoint-private-dns
If you enable private DNS for your interface VPC endpoint, and your VPC has both DNS hostnames and DNS resolution enabled, we create a hidden, AWS-managed private hosted zone for you. The hosted zone contains a record set for the default DNS name for the service that resolves it to the private IP addresses of the endpoint network interfaces in your VPC. Therefore, if you have existing applications that send requests to the AWS service using a public Regional endpoint, those requests now go through the endpoint network interfaces, without requiring that you make any changes to those applications.
Bella Riku!!
It bloody works, mate! Thank you very much, it works like a charm; i just reverted back to my previous code and it just worked.
Have a good weekend!
answered 2 years ago
