spring-cloud / spring-cloud/spring-cloud-config

Add support for setting proxy on aws client

Open
#1,632 9 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement help wanted
Dominant language
Java
Stars
2k
Forks
1.3k
Avg merge
2d 59m
Merged PRs (30d)
16

Description

Describe the bug
Trying to use spring cloud config server with s3 as backend and using proxy credentials to connect to AWS s3. And got this exception when I have .credentials file in /.aws/ directory. I have embedded config server in one application.

bootstrap.yml

spring:
  profiles:
      active: awss3
  cloud:
    config:
      server:
        awss3:
          region: us-east-1
          bucket: sample-bucket
        default-label: sample-config
        default-profile: test
        default-application-name: awss3-demo
        bootstrap: true

application.yml

server:
  port: 8080

Sample
Got below exception in AwsS3EnvironmentRepository.java class when finding the config file in s3 with the default credentials
eYaml = {SdkClientException@5620)com.amazonaws.SdkClientException: Unable to execute HTTP request: Connection reset

Any Help will be great. Thank you.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading AwsS3EnvironmentRepository.java and how its AWS client is constructed, using the supplied bootstrap.yml and application.yml as the reproduction context. Investigate how proxy credentials could be supplied for the S3 connection; done means the config server can retrieve configuration from S3 through the proxy without the connection-reset exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, java, spring
Domain
backend, cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.