This post introduces the decision to use DefaultCredentialsProvider instead of ProfileCredentialsProvider in AWS SDK for Java.

Background: DefaultCredentialsProvider is Recommended

I learned that using DefaultCredentialsProvider instead of ProfileCredentialsProvider in AWS SDK for Java is more convenient.

• 認証情報プロバイダーの変更 - AWS SDK for Java
• ProfileCredentialsProvider (AWS SDK for Java - 2.18.2)
• DefaultCredentialsProvider (AWS SDK for Java - 2.18.2)

Benefits of DefaultCredentialsProvider

It can be used on AWS without defining AWS_PROFILE.

Also, in local environments, it can be used if either of the following is set in environment variables:

• AWS_PROFILE
• AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY

That’s all about deciding to use DefaultCredentialsProvider instead of ProfileCredentialsProvider in AWS SDK for Java. That’s all from the Gemba.