1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
Have you taken a look at this blog post that explains how to privately access S3 from on-prem servers - https://aws.amazon.com/blogs/networking-and-content-delivery/secure-hybrid-access-to-amazon-s3-using-aws-privatelink/
Contenus pertinents
- demandé il y a un an
- demandé il y a un mois
- AWS OFFICIELA mis à jour il y a 2 ans
- Pourquoi le plug-in CNI de mon VPC ne parvient-il pas à atteindre le serveur d'API dans Amazon EKS ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans
Following that guide I have created an inbound resolver and alias to my S3 endpoint for the s3.dualstack.us-east-1.amazonaws.com domain, but the payload is still failing to download.
When I test with wget it fails with a certificate error:
root@xxxx:/tmp# wget https://s3.dualstack.us-east-1.amazonaws.com/aws-ssm-us-east-1/patchbaselineoperations/linux/payloads/patch-baseline-operations-1.96.tar.gz --2022-10-19 14:41:48-- https://s3.dualstack.us-east-1.amazonaws.com/aws-ssm-us-east-1/patchbaselineoperations/linux/payloads/patch-baseline-operations-1.96.tar.gz Resolving s3.dualstack.us-east-1.amazonaws.com (s3.dualstack.us-east-1.amazonaws.com)... 10.x.x.x, 10.x.x.x Connecting to s3.dualstack.us-east-1.amazonaws.com (s3.dualstack.us-east-1.amazonaws.com)|10.x.x.x|:443... connected. ERROR: no certificate subject alternative name matches requested host name ‘s3.dualstack.us-east-1.amazonaws.com’. To connect to s3.dualstack.us-east-1.amazonaws.com insecurely, use `--no-check-certificate'.
Is there a way to bypass within the agent json config file?