Spring Boot多Profile失效及AWS DynamoDB连接双问题求助

Hey there, let's tackle these two tricky issues you're running into with your Spring Boot + DynamoDB setup. I've broken down each problem with root causes and actionable fixes below.

1. Production Profile Keeps Loading Local Configuration #

It sounds like your Spring Boot app is ignoring the prod profile you're trying to activate, and sticking to application-local.properties instead. Here's why that might be happening and how to fix it:

Possible Causes & Fixes #

• Check for hardcoded active profiles: Double-check your main application class or any configuration classes for an @ActiveProfiles("local") annotation. If this is present, it will override any command-line profile activation—remove it or adjust it to be dynamic (like @ActiveProfiles("${spring.profiles.active:local}") to fall back to local only when no profile is specified).
• Verify Maven Profile Setup: If you're using mvn spring-boot:run -Pprod, make sure your pom.xml has a properly configured prod profile that sets the Spring profile. Add this if it's missing:

  <profiles>
      <profile>
          <id>prod</id>
          <properties>
              <spring.profiles.active>prod</spring.profiles.active>
          </properties>
      </profile>
  </profiles>
  

• Check for IDE Configuration Overrides: If you're running the app from an IDE (like IntelliJ or Eclipse), make sure your run configuration isn't forcing the local profile. Look in the VM options or program arguments for -Dspring.profiles.active=local and remove it if present.
• Debug Configuration Loading: Run the app with debug logs enabled to see exactly which config files are being loaded:

  mvn spring-boot:run -Dspring.profiles.active=prod -X
  

  Look for lines starting with Loaded property source to confirm if application-prod.properties is being picked up.

2. Placeholder Error When Using application.properties #

When you renamed application-prod.properties to application.properties, Spring threw an error about missing ${AWS_SECRET_ACCESS_KEY}. The root issue here is that Spring Boot doesn't automatically load credentials from ~/.aws/credentials into its environment—those are only read by the AWS SDK by default. Here are your options to fix this:

Option 1: Let AWS SDK Handle Credentials (Recommended) #

This is the AWS best practice—let the SDK automatically find credentials from multiple sources (environment variables, ~/.aws/credentials, IAM roles if running on EC2/EKS, etc.). Modify your DynamoDbConfig to remove the hardcoded credential loading:

First, update the config class:

@Configuration
class DynamoDbConfig {
    @Value("${amazon.dynamodb.region}")
    private String awsDynamoDBRegion;

    public AWSCredentialsProvider amazonAWSCredentialsProvider() {
        // SDK will auto-load credentials from default sources
        return DefaultAWSCredentialsProviderChain.getInstance();
    }

    @Bean
    public DynamoDB dynamoDB() {
        AmazonDynamoDB amazonDynamoDB = AmazonDynamoDBClientBuilder.standard()
                .withRegion(awsDynamoDBRegion)
                .withCredentials(amazonAWSCredentialsProvider())
                .build();
        return new DynamoDB(amazonDynamoDB);
    }
}

Then simplify your application.properties (you can remove the credential lines entirely):

amazon.dynamodb.region=${AWS_DEFAULT_REGION:us-east-1}

The ${AWS_DEFAULT_REGION:us-east-1} syntax means it will use the AWS_DEFAULT_REGION environment variable if set, or fall back to us-east-1 if not.

Option 2: Pass Credentials as Environment Variables/JVM Arguments #

If you still want to use @Value for credentials, you need to make those AWS variables available to Spring's environment:

• Environment Variables: Start the app with the variables set directly:

  AWS_ACCESS_KEY_ID=MyKeyId AWS_SECRET_ACCESS_KEY=MySecretKey AWS_DEFAULT_REGION=us-east-1 mvn spring-boot:run
  

• JVM Arguments: Pass them as VM options:

  mvn spring-boot:run -DAWS_ACCESS_KEY_ID=MyKeyId -DAWS_SECRET_ACCESS_KEY=MySecretKey -DAWS_DEFAULT_REGION=us-east-1
  

• Server Environment: On your production server, set these environment variables permanently (e.g., in /etc/profile or your deployment script).

内容的提问来源于stack exchange，提问作者Julio