How can I set env var or system property in managed flink

In Amazon Managed Service for Apache Flink, you cannot directly set environment variables or JVM system properties through the console or API in the same way you might with other compute services. The runtime properties feature you mentioned is specifically designed for application configuration and is accessed programmatically through the Flink application code itself, not as system-level environment variables or JVM properties.

Runtime properties in Managed Service for Apache Flink are accessed within your Java application using the KinesisAnalyticsRuntime.getApplicationProperties() method, which returns a Map<String, Properties> object. These are application-level configuration properties used to configure Flink sources, sinks, and other application components without recompilation - they don't translate to environment variables or system properties that would be visible to the AWS SDK.

For your specific use case of setting AWS_JAVA_V1_PRINT_LOCATION or aws.java.v1.printLocation, you would need to modify your application code to programmatically set the system property before the AWS SDK is initialized. You could do this in your application's main method or initialization code by adding:

System.setProperty("aws.java.v1.printLocation", "true");

Alternatively, you could set:

System.setProperty("aws.java.v1.disableDeprecationAnnouncement", "true");

This would need to be done early in your application startup, before any AWS SDK v1.x classes are loaded. Since you'll need to modify and redeploy your application code anyway, this is the appropriate approach for Managed Service for Apache Flink.
Sources
Use runtime properties in Managed Service for Apache Flink - Managed Service for Apache Flink

• Would you consider migrating to SDK 2.x The proper long-term solution is to ensure your application and all its dependencies use AWS SDK for Java 2.x. AWS provides a migration tool that can help automate this process, refer [1]:

    mvn org.openrewrite.maven:rewrite-maven-plugin:6.17.0:run \
   -Drewrite.recipeArtifactCoordinates=software.amazon.awssdk:v2-migration:2.34.0 \
   -Drewrite.activeRecipes=software.amazon.awssdk.v2migration.AwsSdkJavaV1ToV2
  

• Configuration Options Available in MSF

For reference, the configuration options you can control in Managed Service for Apache Flink include, refer [2]:

• Additionally, few more points, FYI:

1. Runtime properties: Application-specific parameters accessible via your code
2. Flink configuration properties: Limited set of Apache Flink settings (requires support case for most changes), refer [3]
3. Parallelism configuration: Application scaling parameters, refer [4]
4. Monitoring configuration: CloudWatch logging settings, refer [5]

But remember, none of these provide access to JVM system properties or OS environment variables.

[1] https://aws.amazon.com/blogs/developer/general-availability-release-of-the-migration-tool-for-the-aws-sdk-for-java-2-x/

[2] https://docs.aws.amazon.com/managed-flink/latest/apiv2/API_ApplicationConfiguration.html

[3] https://docs.aws.amazon.com/managed-flink/latest/java/reference-flink-settings.title.html

[4] https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/kinesisanalyticsv2/model/ParallelismConfiguration.html

[5] https://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/amazonaws/services/kinesisanalyticsv2/model/FlinkApplicationConfiguration.html