Yanhong Zhao
08/22/2024, 5:15 PMTimothy Kovacs
08/22/2024, 7:55 PMCaused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "{our EC2's IP address}", user "xxx", database "xxx", no encryption
Gideon
08/22/2024, 10:14 PMCannot end publishing: Cannot publish to S3: Unable to load AWS credentials from any provider in the chain: [EnvironmentVariableCredentialsProvider: Unable to load AWS credentials from environment variables (AWS_ACCESS_KEY_ID (or AWS_ACCESS_KEY) and AWS_SECRET_KEY (or AWS_SECRET_ACCESS_KEY)), SystemPropertiesCredentialsProvider: Unable to load AWS credentials from Java system properties (aws.accessKeyId and aws.secretKey), WebIdentityTokenCredentialsProvider: You must specify a value for roleArn and roleSessionName, com.amazonaws.auth.profile.ProfileCredentialsProvider@9a458c1: profile file cannot be null, com.amazonaws.auth.EC2ContainerCredentialsProviderWrapper@763b785: The full URI (<http://169.254.170.23/v1/credentials>) contained withing environment variable AWS_CONTAINER_CREDENTIALS_FULL_URI has an invalid host. Host should resolve to a loopback address or have the full URI be HTTPS.]
When I look at the pod it has the correct environment variable that the pod identity add-on adds based on the service account:
AWS_STS_REGIONAL_ENDPOINTS: regional
AWS_DEFAULT_REGION: us-west-2
AWS_REGION: us-west-2
AWS_CONTAINER_CREDENTIALS_FULL_URI: <http://X.X.X.X/v1/credentials>
AWS_CONTAINER_AUTHORIZATION_TOKEN_FILE: /var/run/secrets/pods.eks.amazonaws.com/serviceaccount/eks-pod-identity-token
It just appears that the airbyte code is not looking in the right place for the creds.
Anyone have experience with this?Himanshu Aggarwal
08/23/2024, 1:43 AM(<_InactiveRpcError of RPC that terminated with: status = StatusCode.INVALID_ARGUMENT details = "Request contains an invalid argument." debug_error_string = "UNKNOWN:Error received from peer ipv4:142.250.76.170:443 {created_time:"2024-08-23T01:34:42.395101391+00:00", grpc_status:3, grpc_message:"Request contains an invalid argument."}" >, <_InactiveRpcError of RPC that terminated with: status = StatusCode.INVALID_ARGUMENT details = "Request contains an invalid argument." debug_error_string = "UNKNOWN:Error received from peer ipv4:142.250.76.170:443 {created_time:"2024-08-23T01:34:42.395101391+00:00", grpc_status:3, grpc_message:"Request contains an invalid argument."}" >, errors { error_code { request_error: INVALID_PAGE_SIZE } message: "Page size is invalid." } request_id: "7K_BJPq9kI19ou7odxfJwA" , '7K_BJPq9kI19ou7odxfJwA')
Any help would be much appreciated
ThanksDean Lau
08/23/2024, 3:42 AMinstanceProfile
? referring this doc, i don't see it ask to specify the SM name for storing connector credentials