Question: Running stream manager component behind proxy

"I am using stream manager v2.1.3 with Greengrass Nucleus v2.9.4 on Windows PC behind a proxy.I set JVM_ARGS parameter of stream manager as follows, but stream manager failed to start.How should I configure stream manager component to work properly behind a proxy?"JVM_ARGS": "-Dhttp.proxyHost=<MyProxyHost> -Dhttp.proxyPort=8080 -Dhttp.proxyUser=<MyProxyUser> -Dhttp.proxyPassword=<MyProxyPassword> -Dhttps.proxyHost=<MyProxyHost> -Dhttps.proxyPort=8080 -Dhttps.proxyUser=<MyProxyUser> -Dhttps.proxyPassword=<MyProxyPassword>"Following is startup log of stream manager component.shell-runner-start. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING, command=["java -Djdk.http.auth.tunneling.disabledSchemes=\u0022\u0022 -Dhttp.proxyHost=<MyProxyHost>..."]}stdout. 2023 3・ｽ・ｽ 29 13:17:42,547 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKWrapper: Socket file path: \\.\pipe\NucleusNamedPipe-Cgreengrassv2. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 29, 2023 1:17:42 ・ｽﾟ鯉ｿｽ software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onConnectionSetup. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Socket connection \\.\pipe\NucleusNamedPipe-Cgreengrassv2:8033 to server result [AWS_ERROR_SUCCESS]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 29, 2023 1:17:42 ・ｽﾟ鯉ｿｽ software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onProtocolMessage. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Connection established with event stream RPC server. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 29 13:17:43,078 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.utils.FileChannelCache: FileChannelCache not initialized! Using defaults. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 29 13:17:44,328 [INFO] (main) com.amazonaws.http.AmazonHttpClient: Configuring Proxy. Proxy Host:  Proxy Port: 8080. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 29 13:17:44,328 [ERROR] (main) com.amazonaws.iot.greengrass.streammanager.StreamManagerService: StreamManagerService: Error initializing. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. java.lang.IllegalArgumentException: Host name may not be empty. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at org.apache.http.util.Args.containsNoBlanks(Args.java:84) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at org.apache.http.HttpHost.<init>(HttpHost.java:80) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.http.apache.SdkProxyRoutePlanner.<init>(SdkProxyRoutePlanner.java:43) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory.addProxyConfig(ApacheHttpClientFactory.java:94) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory.create(ApacheHttpClientFactory.java:75) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.http.apache.client.impl.ApacheHttpClientFactory.create(ApacheHttpClientFactory.java:38) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.http.AmazonHttpClient.<init>(AmazonHttpClient.java:339) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.http.AmazonHttpClient.<init>(AmazonHttpClient.java:323) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.AmazonWebServiceClient.<init>(AmazonWebServiceClient.java:239) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.AmazonWebServiceClient.<init>(AmazonWebServiceClient.java:225) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.services.iotanalytics.AWSIoTAnalyticsClient.<init>(AWSIoTAnalyticsClient.java:303) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.services.iotanalytics.AWSIoTAnalyticsClient.<init>(AWSIoTAnalyticsClient.java:289) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.services.iotanalytics.AWSIoTAnalyticsClientBuilder.build(AWSIoTAnalyticsClientBuilder.java:61) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.services.iotanalytics.AWSIoTAnalyticsClientBuilder.build(AWSIoTAnalyticsClientBuilder.java:27) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.client.builder.AwsSyncClientBuilder.build(AwsSyncClientBuilder.java:46) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.AWSClientFactory.createIotAnalyticsClient(AWSClientFactory.java:56) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule.awsIoTAnalytics(ExportModule.java:80) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule_AwsIoTAnalyticsFactory.get(ExportModule_AwsIoTAnalyticsFactory.java:29) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule_AwsIoTAnalyticsFactory.get(ExportModule_AwsIoTAnalyticsFactory.java:10) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at dagger.internal.DoubleCheck.get(DoubleCheck.java:47) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule_ExportStreamFactoryFactory.get(ExportModule_ExportStreamFactoryFactory.java:68) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule_ExportStreamFactoryFactory.get(ExportModule_ExportStreamFactoryFactory.java:16) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at dagger.internal.DoubleCheck.get(DoubleCheck.java:47) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule_ExportManagerFactory.get(ExportModule_ExportManagerFactory.java:90) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.ExportModule_ExportManagerFactory.get(ExportModule_ExportManagerFactory.java:20) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at dagger.internal.DoubleCheck.get(DoubleCheck.java:47) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.StreamServerModule_StreamServerFactory.get(StreamServerModule_StreamServerFactory.java:70) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.StreamServerModule_StreamServerFactory.get(StreamServerModule_StreamServerFactory.java:16) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at dagger.internal.DoubleCheck.get(DoubleCheck.java:47) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.dagger.DaggerStreamManagerServiceComponent.streamServer(DaggerStreamManagerServiceComponent.java:284) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. at com.amazonaws.iot.greengrass.streammanager.StreamManagerService.main(StreamManagerService.java:44) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 29 13:17:44,531 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Stream Manager reporting the state: ERRORED. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STOPPING}FollowComment"

Answer: "1Mmm it seems like when the nucleus starts the stream manager process it already sets those environment variables from the configuration See code. So if you are configuring the proxy on the nucleus it seems like you shouldn't need to pass all those properties as JVM args so you could remove the JVM ARGS related to the proxy configuration from the SM. Regardless, it seems like the issue you are now seeing isjava.net.UnknownHostExceptionwhich would point to a DSN resolution problemPS: When removing configuration you will have to use resetCommentShareochoanelanswered 2 months agorePost-User-1680648 2 months agoThank you for response. Indeed, I could see proxy settings loaded without JVM_ARG parameter. Eventually it failed with a similar error...In our environment DNS name resolution is done by proxy server. So I think root cause is stream manager could not access S3 endpoint via proxy server.Shareochoanel 2 months agoThe java.net.UnknownHostException exception doesn't mean the stream manager can not access S3, it means that it could not resolve the IP address of the S3 endpoint provided through the proxy. I think the issue is with the network or proxy configuration that fails to resolve the S3 address.Share1Stream Manager configuration file reference: https://docs.aws.amazon.com/greengrass/v2/developerguide/configure-stream-manager.htmlTroubleshooting AWS IoT Greengrass V2: https://docs.aws.amazon.com/greengrass/v2/developerguide/troubleshooting.htmlCommentSharerePost-User-5208427answered 2 months ago1If AWS IoT Greengrass is configured with proxy settings, then the Stream Manager component will use it too. See here for configuring the proxy.CommentShareGavin_Aanswered 2 months ago1Try usingFor https"JVM_ARGS": "-DHTTPS_PROXY=https://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>"For http"JVM_ARGS": "-DHTTP_PROXY=http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>"If that doesn't work and you get an error post the error you seen on the Stream Manager logsCommentShareochoanelanswered 2 months ago0"JVM_ARGS": "-DHTTPS_PROXY=http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>"shell-runner-start. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING, command=["java -DHTTPS_PROXY=http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>..."]}stdout. 2023 3・ｽ・ｽ 30 14:43:12,750 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKWrapper: Socket file path: \\.\pipe\NucleusNamedPipe-Cgreengrassv2. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 30, 2023 2:43:12 ・ｽﾟ鯉ｿｽ software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onConnectionSetup. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Socket connection \\.\pipe\NucleusNamedPipe-Cgreengrassv2:8033 to server result [AWS_ERROR_SUCCESS]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 30, 2023 2:43:12 ・ｽﾟ鯉ｿｽ software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onProtocolMessage. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Connection established with event stream RPC server. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:13,297 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.utils.FileChannelCache: FileChannelCache not initialized! Using defaults. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,000 [INFO] (main) com.amazonaws.internal.DefaultServiceEndpointBuilder: {iotsitewise, ap-northeast-1} was not found in region metadata, trying to construct an endpoint using the standard pattern for this region: 'iotsitewise.ap-northeast-1.amazonaws.com'.. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,203 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.server.protocol.AuthHandler: Greengrass v1 Auth SDK not detected. Attempting to use the v2 SDK.. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,203 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.StreamServer: Starting streamServer on port: 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,219 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.export.decider.Decider: Starting decider. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,922 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Publish the stream manager port: 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,922 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.StreamServer: StreamServer ready to accept connections on port 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. 2023 3・ｽ・ｽ 30 14:43:15,937 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Stream Manager reporting the state: RUNNING. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. 2023 3・ｽ・ｽ 30 14:43:16,617 [ERROR] (pool-7-thread-2) com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask: Encountered Throwable when exporting messages. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. com.amazonaws.SdkClientException: Unable to execute HTTP request: <MyS3Endpoint>. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1207) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1153) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:744) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:550) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:530) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5437) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5384) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.access$300(AmazonS3Client.java:421) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client$PutObjectStrategy.invokeServiceCall(AmazonS3Client.java:6508) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.uploadObject(AmazonS3Client.java:1856) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1816) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.makeSinglePutRequest(S3TaskDestination.java:435) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.sendMessage(S3TaskDestination.java:155) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask.upload(MessageUploaderTask.java:77) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.lang.Thread.run(Thread.java:829) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. Caused by: java.net.UnknownHostException: <MyS3Endpoint>. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}CommentSharerePost-User-1680648answered 2 months agoGavin_A 2 months agoLet me take a look at this. Do you see any in the entries in your proxy server referencing the Stream Manager targets.Shareochoanel 2 months agoRunning it with DEBUG level logs should print on the logs the proxy url. There is a Setting https proxy to {}", httpsProxyEnvVar); debug level log when configuring it and we get the httpsProxyEnvVar from System.getenv(HTTPS_PROXY)Share0Thank you for your answer.I have already checked "Stream Manager configuration file reference", but I have never seen "Stream Manager troubleshooting guide". The above URL seems to be invalid for me, so could you tell me the correct URL?CommentSharerePost-User-1680648answered 2 months ago0I'm sorry, I tried it again and I could access the trouble shooting guide without any problem.Unfortunately, I couldn't find anything related to the proxy setting of stream manager component.CommentSharerePost-User-1680648answered 2 months ago0Thank you for your answer.I tried suggested approaches, but neither worked. Greengrass Nucleus itself can communicate through a proxy server without any problems.Here are the logs of stream manager component."JVM_ARGS": ""shell-runner-start. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING, command=["java  -cp \u0022C:\greengrass\v2\packages\artifacts\aws.greengrass.StreamManager\2...."]}stdout. 2023 3・ｽ・ｽ 30 11:52:31,545 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKWrapper: Socket file path: \\.\pipe\NucleusNamedPipe-Cgreengrassv2. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 30, 2023 11:52:31 ・ｽﾟ前 software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onConnectionSetup. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Socket connection \\.\pipe\NucleusNamedPipe-Cgreengrassv2:8033 to server result [AWS_ERROR_SUCCESS]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 30, 2023 11:52:31 ・ｽﾟ前 software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onProtocolMessage. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Connection established with event stream RPC server. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:32,076 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.utils.FileChannelCache: FileChannelCache not initialized! Using defaults. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:33,623 [INFO] (main) com.amazonaws.internal.DefaultServiceEndpointBuilder: {iotsitewise, ap-northeast-1} was not found in region metadata, trying to construct an endpoint using the standard pattern for this region: 'iotsitewise.ap-northeast-1.amazonaws.com'.. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:33,764 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.server.protocol.AuthHandler: Greengrass v1 Auth SDK not detected. Attempting to use the v2 SDK.. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:33,779 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.StreamServer: Starting streamServer on port: 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:33,779 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.export.decider.Decider: Starting decider. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:34,842 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Publish the stream manager port: 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:52:34,842 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.StreamServer: StreamServer ready to accept connections on port 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. 2023 3・ｽ・ｽ 30 11:52:34,842 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Stream Manager reporting the state: RUNNING. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. 2023 3・ｽ・ｽ 30 11:52:35,509 [ERROR] (pool-7-thread-1) com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask: Encountered Throwable when exporting messages. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. com.amazonaws.SdkClientException: Unable to execute HTTP request: <MyS3Endpoint>. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1207) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1153) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:744) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:550) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:530) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5437) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5384) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.access$300(AmazonS3Client.java:421) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client$PutObjectStrategy.invokeServiceCall(AmazonS3Client.java:6508) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.uploadObject(AmazonS3Client.java:1856) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1816) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.makeSinglePutRequest(S3TaskDestination.java:435) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.sendMessage(S3TaskDestination.java:155) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask.upload(MessageUploaderTask.java:77) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.lang.Thread.run(Thread.java:829) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. Caused by: java.net.UnknownHostException: <MyS3Endpoint>. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}CommentSharerePost-User-1680648answered 2 months ago0"JVM_ARGS": "-DHTTP_PROXY=http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>"shell-runner-start. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING, command=["java -DHTTP_PROXY=http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>..."]}stdout. 2023 3・ｽ・ｽ 30 11:12:59,484 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKWrapper: Socket file path: \\.\pipe\NucleusNamedPipe-Cgreengrassv2. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 30, 2023 11:12:59 ・ｽﾟ前 software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onConnectionSetup. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Socket connection \\.\pipe\NucleusNamedPipe-Cgreengrassv2:8033 to server result [AWS_ERROR_SUCCESS]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. 3・ｽ・ｽ 30, 2023 11:12:59 ・ｽﾟ前 software.amazon.awssdk.eventstreamrpc.EventStreamRPCConnection$1 onProtocolMessage. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stderr. ・ｽ・ｽ・ｽ: Connection established with event stream RPC server. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:12:59,921 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.utils.FileChannelCache: FileChannelCache not initialized! Using defaults. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:01,593 [INFO] (main) com.amazonaws.internal.DefaultServiceEndpointBuilder: {iotsitewise, ap-northeast-1} was not found in region metadata, trying to construct an endpoint using the standard pattern for this region: 'iotsitewise.ap-northeast-1.amazonaws.com'.. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:01,749 [WARN] (main) com.amazonaws.iot.greengrass.streammanager.server.protocol.AuthHandler: Greengrass v1 Auth SDK not detected. Attempting to use the v2 SDK.. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:01,749 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.server.StreamServer: Starting streamServer on port: 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:01,765 [INFO] (main) com.amazonaws.iot.greengrass.streammanager.export.decider.Decider: Starting decider. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:03,359 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Publish the stream manager port: 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:03,359 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.StreamServer: StreamServer ready to accept connections on port 8088. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=STARTING}stdout. 2023 3・ｽ・ｽ 30 11:13:03,374 [INFO] (pool-6-thread-1) com.amazonaws.iot.greengrass.streammanager.server.GreengrassCoreV2SDKHandler: Stream Manager reporting the state: RUNNING. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. 2023 3・ｽ・ｽ 30 11:13:04,008 [ERROR] (pool-7-thread-1) com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask: Encountered Throwable when exporting messages. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. com.amazonaws.SdkClientException: Unable to execute HTTP request: <MyS3Endpoint>. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1207) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1153) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:744) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:550) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:530) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5437) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5384) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.access$300(AmazonS3Client.java:421) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client$PutObjectStrategy.invokeServiceCall(AmazonS3Client.java:6508) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.uploadObject(AmazonS3Client.java:1856) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1816) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.makeSinglePutRequest(S3TaskDestination.java:435) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.sendMessage(S3TaskDestination.java:155) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask.upload(MessageUploaderTask.java:77) ~[AWSGreengrassGreenlake-1.0-super.jar:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. at java.lang.Thread.run(Thread.java:829) ~[?:?]. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}stdout. Caused by: java.net.UnknownHostException: <MyS3Endpoint>. {scriptName=services.aws.greengrass.StreamManager.lifecycle.startup.script, serviceName=aws.greengrass.StreamManager, currentState=RUNNING}CommentSharerePost-User-1680648answered 2 months ago0Thank you for your responses.I'm sorry, but I can't confirm whether our proxy server actually accessed my S3 endpoint for permission reasons.I saw the URL of our proxy server in the DEBUG level log. Following is an excerpt from the stream manager log:[DEBUG] (main) com.amazonaws.iot.greengrass.streammanager.common.ProxyManager: Setting https proxy to http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>[DEBUG] (main) com.amazonaws.iot.greengrass.streammanager.common.ProxyManager: Setting http proxy to http://<MyProxyUserName>:<MyProxyPassword>@<MyProxyHost>:<MyProxyPort>[DEBUG] (main) com.amazonaws.iot.greengrass.streammanager.common.ProxyManager: Setting http.nonProxyHost to localhost(snip)[DEBUG] (pool-7-thread-1) com.amazonaws.request: Sending Request: PUT https://<MyS3Endpoint> <MyFile1> Headers: (amz-sdk-invocation-id: <SDKInvocationID1>, Content-Length: 0, Content-Type: application/octet-stream, User-Agent: AWSGreengrass-StreamManager v1.1.0;, aws-internal/3 aws-sdk-java/1.11.1030 Windows_Server_2019/10.0 OpenJDK_64-Bit_Server_VM/11.0.18+10-LTS java/11.0.18 kotlin/1.3.72 vendor/Microsoft cfg/retry-mode/standard, x-amz-meta-$aws-gg-source: AWSGreengrass-StreamManager v1.1.0;, )(snip)[DEBUG] (pool-7-thread-1) org.apache.http.impl.conn.PoolingHttpClientConnectionManager: Connection request: [route: {s}->https://<MyS3Endpoint>:443][total available: 0; route allocated: 0 of 50; total allocated: 0 of 50][DEBUG] (pool-7-thread-1) org.apache.http.impl.conn.PoolingHttpClientConnectionManager: Connection leased: [id: 0][route: {s}->https://<MyS3Endpoint>:443][total available: 0; route allocated: 1 of 50; total allocated: 1 of 50][DEBUG] (pool-7-thread-1) org.apache.http.impl.execchain.MainClientExec: Opening connection {s}->https://<MyS3Endpoint>:443(snip)[DEBUG] (pool-7-thread-2) com.amazonaws.request: Sending Request: PUT https://<MyS3Endpoint> <MyFile2> Headers: (amz-sdk-invocation-id: <SDKInvocationID2>, Content-Length: 2539349, Content-Type: application/octet-stream, User-Agent: AWSGreengrass-StreamManager v1.1.0;, aws-internal/3 aws-sdk-java/1.11.1030 Windows_Server_2019/10.0 OpenJDK_64-Bit_Server_VM/11.0.18+10-LTS java/11.0.18 kotlin/1.3.72 vendor/Microsoft cfg/retry-mode/standard, x-amz-meta-$aws-gg-source: AWSGreengrass-StreamManager v1.1.0;, )(snip)[DEBUG] (pool-7-thread-2) org.apache.http.impl.conn.PoolingHttpClientConnectionManager: Connection request: [route: {s}->https://<MyS3Endpoint>:443][total available: 0; route allocated: 1 of 50; total allocated: 1 of 50][DEBUG] (pool-7-thread-2) org.apache.http.impl.conn.PoolingHttpClientConnectionManager: Connection leased: [id: 1][route: {s}->https://<MyS3Endpoint>:443][total available: 0; route allocated: 2 of 50; total allocated: 2 of 50][DEBUG] (pool-7-thread-2) org.apache.http.impl.execchain.MainClientExec: Opening connection {s}->https://<MyS3Endpoint>:443[DEBUG] (pool-7-thread-1) com.amazonaws.http.conn.ClientConnectionManagerFactory:java.lang.reflect.InvocationTargetException: nullat jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:?]at jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:?]at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:?]at java.lang.reflect.Method.invoke(Method.java:566) ~[?:?]at com.amazonaws.http.conn.ClientConnectionManagerFactory$Handler.invoke(ClientConnectionManagerFactory.java:76) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.conn.$Proxy25.connect(Unknown Source) ~[?:?]at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:393) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:236) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.apache.client.impl.SdkHttpClient.execute(SdkHttpClient.java:72) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeOneRequest(AmazonHttpClient.java:1331) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeHelper(AmazonHttpClient.java:1145) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutor.doExecute(AmazonHttpClient.java:802) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutor.executeWithTimer(AmazonHttpClient.java:770) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutor.execute(AmazonHttpClient.java:744) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutor.access$500(AmazonHttpClient.java:704) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient$RequestExecutionBuilderImpl.execute(AmazonHttpClient.java:686) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:550) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.http.AmazonHttpClient.execute(AmazonHttpClient.java:530) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5437) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.services.s3.AmazonS3Client.invoke(AmazonS3Client.java:5384) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.services.s3.AmazonS3Client.access$300(AmazonS3Client.java:421) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.services.s3.AmazonS3Client$PutObjectStrategy.invokeServiceCall(AmazonS3Client.java:6508) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.services.s3.AmazonS3Client.uploadObject(AmazonS3Client.java:1856) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.services.s3.AmazonS3Client.putObject(AmazonS3Client.java:1816) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.makeSinglePutRequest(S3TaskDestination.java:435) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.iot.greengrass.streammanager.export.destination.S3TaskDestination.sendMessage(S3TaskDestination.java:155) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at com.amazonaws.iot.greengrass.streammanager.export.upload.MessageUploaderTask.upload(MessageUploaderTask.java:77) ~[AWSGreengrassGreenlake-1.0-super.jar:?]at java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700) ~[?:?]at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]at java.lang.Thread.run(Thread.java:829) ~[?:?]Caused by: java.net.UnknownHostException: 繝ｻ・ｽ繝ｻ・ｽ繝ｻ・ｽ・後ｈ縺・・・ｽ・医・繝ｻ・ｽX繝ｻ・ｽg繝ｻ・ｽ・堺ｸ阪・・ｽ繝ｻ・ｽ繝ｻ・ｽ・・ｑ・ｿ・ｽ繝ｻ・ｽB (<MyS3Endpoint>)CommentSharerePost-User-1680648answered 2 months ago0Thank you for your response.The java.net.UnknownHostException exception doesn't mean the stream manager can not access S3, it means that it could not resolve the IP address of the S3 endpoint provided through the proxy. I think the issue is with the network or proxy configuration that fails to resolve the S3 address.I analyzed network packets at the beginning of HTTP communication for Nucleus and Stream Manager.In the case of Nucleus, our proxy server was resolved first, and then Nucleus could access endpoints via our proxy server. Stream Manager, on the other hand, tried and failed to resolve S3 endpoint, but I think it should be accessed through our proxy server as well as Nucleus. Followings are screenshots of Wireshark.Nucleus:Stream Manager:I have already configured proxy settings (WinHTTP, WinINet, environment variables) for Windows OS, but if there is anything else needs to be configured, please let me know.CommentSharerePost-User-1680648answered 2 months ago"


Question: Send a text message and receive a response

"Hi,I am trying to send a text message to a phone using AWSSDK.Pinpoint using Visual Studio (VB.NET or C#).I have written some code, but am not sure where to specify a mobile phone number yet.Public Function Send(sendMessage As SendMessageInfo) As String Implements ISendMessage.Send        Dim ppClient As New AmazonPinpointClient        Dim ppSMSMessage As New SMSMessage With {            .Body = sendMessage.Message,            .MessageType = MessageType.PROMOTIONAL,            .SenderId = "ACG",            .Keyword = "ACG"        }        Dim ppMessageConfiguration As New DirectMessageConfiguration With {            .SMSMessage = ppSMSMessage        }        Dim ppAddressConfiguration As New Dictionary(Of String, AddressConfiguration)        Dim ppMessageRequest As MessageRequest        Dim ppRequest As SendMessagesRequest        Dim ppResponse As SendMessagesResponse        Dim ppEndpoints = New Dictionary(Of String, EndpointSendConfiguration)        ppAddressConfiguration.Add("1", New AddressConfiguration With {            .ChannelType = ChannelType.SMS        })        ppMessageRequest = New MessageRequest With {            .MessageConfiguration = ppMessageConfiguration,            .Addresses = ppAddressConfiguration        }        ppRequest = New SendMessagesRequest With {            .ApplicationId = "ACG",            .MessageRequest = ppMessageRequest        }        ppResponse = ppClient.SendMessages(ppRequest)        Return ppResponse.HttpStatusCode.ToString    End FunctionNote: I am already using S3 and SNS is working using AWSAccessKey and AWSSecretKey in the Web.config (eu-west-1)I am currently getting "HttpErrorResponseException: The remote server returned an error: (404) Not Found."  Previously, I was getting an error related to 'mobiletargeting' which I got around by adding an IAM group, and assigning it to the user.Also, I was wondering if it possible to send the text message and receive a reply straight to e-mail?Any help would be greatly appreciated.Thanks,FollowComment"

Answer: "0I found that the following works for sending the text message.Public Function Send(sendMessage As SendMessageInfo) As String Implements ISendMessage.Send        Dim strReturn As String = String.Empty        Dim strAppID As String = "abcdef123456" 'Pinpoint Project ID in the AWS console (not Project Name)        Dim ppGetEndpointResponse As New GetEndpointResponse        Dim ppEndpointResponse As EndpointResponse = ppGetEndpointResponse.EndpointResponse        Dim ppDirectMessageConfiguration As New DirectMessageConfiguration With {            .SMSMessage = New SMSMessage With {                .Body = sendMessage.Message,                .MessageType = MessageType.PROMOTIONAL            }        }        Dim ppAddressConfiguration As New AddressConfiguration With {            .ChannelType = ChannelType.SMS        }        Dim ppMessageRequest As New MessageRequest With {            .MessageConfiguration = ppDirectMessageConfiguration,            .Addresses = New Dictionary(Of String, AddressConfiguration) From {{sendMessage.PhoneNumber, ppAddressConfiguration}}        }        Dim ppSendMessagesRequest As New SendMessagesRequest With {            .ApplicationId = strAppID,            .MessageRequest = ppMessageRequest        }        Using ppClient As New AmazonPinpointClient            strReturn = ppClient.SendMessages(ppSendMessagesRequest).HttpStatusCode.ToString        End Using        Return strReturn    End FunctionCommentShareEdSansburyanswered 4 years ago"


Question: ECS tasks stops server while connecting to mongo atlas

"“message”:“Server selection timed out after 30000 ms”,“reason”:{“type”:“ReplicaSetNoPrimary”,“servers”:{},“stale”:false,“compatible”:true,“heartbeatFrequencyMS”:10000,“localThresholdMS”:15,“setName”:“atlas-uhi03q-shard-0”}This is error I am receiving when I connect to mongo atlas instance from ECS tasks (EC2 instance running on private subnet). Runs well when I run this application from localhost. I have also enabled VPC peering and IP under network access is open to the world. Cannot figure out the issue. Appreciate some help here.FollowCommentrePost-User-4151060 a year agoIssue with outbound network connection from ec2 instance. I had created VPC endpoints for AWS related services, but for mongo atlas I had to create NAT gateway. With the registration of NAT gateway and allowing all routes in the routing table established mongo atlas connection from private ec2 instance. VPC peering might work, but as I was on shared cluster in mongo it didn't work for me.Share"

Answer: "-1A few things on top of my head:Do you connect with the mongo+srv:// address ? If not, you should and make sure to have open the security group ports on your VPC Private Link (I presume that's what you meant by peering). That way the clients in reply will get both IP address and port to connect to. That's how we do and connection works greatDid you create a MongoDB user with your EC2 IAM task role ? If not, I'd recommend that over username/password. Checkout in CloudFormation -> Public Extensions -> 3rd Party -> look for MongoDb::Atlas::AwsIamDatabaseUser. Of course, that's if you use CFN.CommentShareJohnPrestonanswered a year agorePost-User-4151060 a year agoYes I connect using mongo+srv:// address.. VPC peering is the latest option looks like but didn't work for me, as I am on the shared cluster. I have enabled all HTTP for my alb. What are the security ports I should enable? Can you share any links or elaborate a bit here?Share"


Question: S3 Destinations are not available in Add option of Option Group for SQL BACKUP

"I already created an Option Group in RDS and am trying to add Option.But when I try that with the new IAM role, I can't select the S3 bucket from the list.The S3 list is not populating in the drop-down.The data list (S3 bucket list) from API is coming as I checked with the browser console.Note: I did the same day before as a test without such an issue and deleted the created IAM role.And I have Admin access to the account.FollowComment"

Answer: 0Make sure you have the correct IAM Policy that's attached to the IAM role as it is listed in the RDS AWS S3 integration documentation. Hope this helpsCommentShareAWS-User-EPanswered 3 months ago


Question: Textract - read barcode

"I saw that in the past some questions have been raised about the possibility of reading barcodes with Textract. Did it evolve? If not, is there any other AWS tool that can provide this service?FollowComment"

Answer: 0Hi! Currently Textract does not support reading barcodes. A possible workaround would be to create a Lambda function with Zbar libraries to read the codes!CommentShareDani Manswered 10 months ago


Question: unable to connect to GIT from Repository HTTPS

"Hi Team, I am not able to connect to GIT using the HTTPS generated GIT crdentials. USer name : Srinivas-at-508466978865 and Password.  I have rcetaed a IAM user from my root account and trying to connect to GIT with HTTPS generated credentials. It is not allowing me to connect. Please helpThanks SrinivasFollowCommentkentrad EXPERT10 days agoAre you using CodeCommit?Sharesedat_salman EXPERT10 days agocan you provide more details about your operation and environmentare you using github, codecommit or another platform?Share"

Answer: "0Hi, a few steps I would try are:Verify IAM User Access: Ensure that the IAM user you created has the necessary permissions and access to interact with the Git service you are trying to connect to. Check the IAM user's policies and ensure they haveappropriate permissions for Git access.Check HTTPS Git Endpoint: Ensure that you are using the correct HTTPS Git endpoint for the Git service you are trying to connect to. Different Git service providers may have different endpoint URLs. Verify that you areusing the appropriate endpoint.Troubleshoot Connectivity Issues: If you are still unable to connect, there may be connectivity issues preventing the connection. Check your network settings, firewall configurations, and ensure that the necessary ports areopen for Git communication over HTTPS.Hope this helps!CommentShareFS_AWSanswered 10 days ago"


Question: New lightsail instance from snapshot without sysprep

"I have several times created a new lightsail Windows 2019 instance from a snapshot of a server which I have fully configured (IIS, web sites, users, firewall etc). The new instance runs perfectly. I did not use sysprep ever.Does anyone know what ill effects I might encountera) if I create new instance without sysprep, but terminate the old instance (as described above)b) if I create a new instance without sysprep, and keep the other instance running. Ie two clones running, but on different ip addressesThanksFollowComment"

Answer: "1Thanks for your answer.From my testing, the only 'ill effect' I've seen of creating a new instance from a non sysprep snapshot is that the machine name is identical to the first. This can be confusing, and changing the machine name seems to cause issues. The advantage is that literally everything else works with no more fussing.I think if simply replacing one instance with another (perhaps larger) I'd go this route.I was having big problems getting sysprep to work, but I found this was because I had changed the name of the Administrator account on my source machine. When I changed it back to Administrator, Lightsail allowed me to access the new sysprepped image. Without an account named Administrator, Lightsail would never give me the password, or allow access to new instance.The advantage of the sysprepped image over a straight clone was that a new machine name was generated.The disadvantage was that several things needed to be reset, includingScheduled tasks needed to be resavedSqlserver needed some scripts to be run to allow Mixed logon.Recreate self signed certs for IIS.Reenter some authorisation details on IIS.One thing I would say is be patient when firing up the new sysprepped image, it takes a good 15 mins for the password to be exposed and RDP to connect.CommentShareVentonanswered a year agoPavel - AWS a year agoThere's a lot of info at https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.html about sysprep. Including this bit: "EC2Launch offers a default answer file and batch files for Sysprep that automate and secure the image-preparation process on your AMI. Modifying these files is optional." Perhaps, you can experiment with sysprep's config files and see if some of the "ill effects" can be resolved, including regenerating the machine name.SharePavel - AWS a year agoProcedural note: We're all new rePost system here :) It works differently from Forums we are all familiar with.Please post an answer when it is actually an answer to the question at the top of the page. Otherwise please use comment buttons.Share0Can you clarify what exactly you're worried about? I'm assuming something to do with licensing? If so, unfortunately I can't help with that, otherwise, go ahead and create/destroy as many instances you want to test as long as you have your original snapshot that you can revert back to if things go wrong. That's the beauty of the cloud :)CommentShareJohn Voldanswered a year ago0No not licensing as I still pay for every instance.Two things I'm worried about.Firstly, the instructions for creating a new instance from a windows snapshot specifically mention needing to run sysprep. I can't see it written anywhere that for Windows I can simply create a snapshot and create an instance from it. Linux instructions do seem that straight forward, not windows. This worries me that I can't see it in black and white. Surely a snapshot should be a really strong and quick backup option in case of disaster.Secondly, if I was to run two cloned instances (without sysprep) .. does this confuse things in terms of the lightsail infrastructure? Will lightsail throw a wobbly when it finds two 'identical' machines?The first worry is my main concern... I really wanted a quick and easy backup option.  Here's the link to creating windows snapshot which worries me.https://lightsail.aws.amazon.com/ls/docs/en_us/articles/prepare-windows-based-instance-and-create-snapshotThanksCommentShareVentonanswered a year ago0Not really here to criticise the documentation, I'd just like to confirm if I really can just create a snapshot without sysprep, delete my instance, create new one from snapshot etc. (windows specifically).The document https://lightsail.aws.amazon.com/ls/docs/en_us/articles/prepare-windows-based-instance-and-create-snapshot says:If your instance doesn't function as expected after running Sysprep, then follow the steps in Creating an instance from a snapshot in Amazon Lightsail to create a new instance from the backup snapshot. There is a link to this page: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/lightsail-how-to-create-instance-from-snapshotThat page says: You must have a snapshot of an instance before you can create another instance from a snapshot. For more information, see Creating a snapshot of your Linux or Unix instance in Amazon Lightsail or Creating a snapshot of your Windows Server instance in Amazon Lightsail. ... which points back to the first page....It's cyclicle.... take a snapshot before you take a snapshot, if you have trouble after taking snapshot, create an instance...CommentShareVentonanswered a year ago0Here's a simplified/vague description of how sysprep works.Bear in mind, that I am not a Windows specialist.Sysprep has two phases of interest:In "generalize" phase, sysprep executes during shutdown to prepare the instance to become a "prototype" from which you can clone some number of new instances. After the "generalize" phase finishes, various customizations, personalizations and so on, that you might have made, will be reset so that the disk of this instance is ready to be cloned to make new instances. Once shutdown is complete, it is safe to make instance shapshots. Any instances created off such snapshots will enter..."Specialize" sysprep phase. At first boot, a new instance will initialize itself as a new machine, you can now personalize it again and configure it as you see fit. It's not going to be the same as the "prototype" instance but various installed software packages will still be the same. Anything that wasn't reset during "generalize" phase, will be the same as it was on the "prototype" instance's disk.Note 1: If you don't initiate sysprep during shutdown, neither "generalize" nor "specialize" phases are executed.Note 2: If you initiated shutdown with sysprep, the original instance will undergo both sysprep phases: "generalize" (during shutdown) and "specialize" (during boot).To answer your question about "ill effects of not using sysprep": you should be fine as long as you keep record of Adminstrator password that the original instance was using, because all other instances that were made from such sysprep-less snapshots will have the same password.A more definitive explanation about sysprep can be found in "Sysprep phases" section here: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/Creating_EBSbacked_WinAMI.htmlCommentSharePavel - AWSanswered a year ago"


Question: How to add custom userUUD when logging aws Lambda Function

"I have a few Lambda functions that run using nodejs. In the function code I have a few logs eg consoleLog('email provided') etcI can also see the logs in cloud watch.My question: I it possible to set a userUUID on the function so that I can filter cloud watch logs by uuid or tag or something like that?The app sends a request to AWS gateway, which calls the lambda. In the request, is the UUID. So wondering if I can use that as some type of filterThanksFollowComment"

Answer: "0The lambda function context has a unique awsRequestId, that you can use to uniquely identify every invocation of a lambda function. By default, lambda generated logs have the Request ID, but you can also get it from the context object and add it to every log statement in your own lambda code - https://docs.aws.amazon.com/lambda/latest/dg/nodejs-context.htmlAlso take a look at this blog about logging when using Lambda with API Gateway - https://aws.amazon.com/blogs/compute/techniques-and-tools-for-better-serverless-api-logging-with-amazon-api-gateway-and-aws-lambda/CommentShareEXPERTIndranil Banerjee AWSanswered 9 months agoEXPERTUrireviewed 9 months agoUri EXPERT9 months agoI would also look at using Lambda Power Tools, which helps you in writing logs according to the best practices.Share"


Question: Generic "Invalid Code" or "User not found" error when implementing SSO workaround for Amazon Cognito

"Due to an issue with the PreSignUp trigger and AdminLinkProviderForUser command, I am following the workaround described by an AWS support engineer in the linked re:Post forum to implement single sign-on for my application that uses Amazon Cognito.https://repost.aws/questions/QULY1qbV21TYqrnVnNdpdpqQ/remove-external-identity-from-cognito-userThe TL:DR of the workaround above is that the AdminLinkProviderForUser command is used in the PostConfirmation trigger. However to do this, we first have to delete the automatically created external IdP user to prevent the command from throwing an error.Depending on which OAuth flow that I choose for single sign-on, such as the authorization code, or the implicit grant, I get an 'invalid code' or 'user not found' error instead of receiving the JWT tokens that I need for my application when applying this workaround. I suspect that the error is because I delete the user that the authorization token or the implicit grant is supposed to be for, but then how did the AWS support engineer successfully retrieve JWT tokens back?Has this been an issue with anyone else? I'm fairly certain I implemented everything in the same manner (except that it is written in JavaScript), but I just simply cannot get it to work.P.S. Any updates on fixing the SSO bug from any AWS employees? More details about this bug described here: https://repost.aws/questions/QUgWVkIodQS1W3Yj8MYjInbA/cognito-auth-flow-fails-with-already-found-an-entry-for-username-usernameFollowComment"


Question: not authorized to perform: sagemaker:CreateModel on resource

"I have been given AmazonSagemakerFullAccess by my companie's AWS admin. No one at our company can figure out why I can't get this line to run to launch the model.***** CODE PRODUCING ERROR *****lang_id = sagemaker.Model(image_uri=container, model_data=model_location, role=role, sagemaker_session=sess)lang_id.deploy(initial_instance_count=1, instance_type="ml.t2.medium")***** ERROR MESSAGE *****ClientError                               Traceback (most recent call last)<ipython-input-5-4c80ec284a4b> in <module>2     image_uri=container, model_data=model_location, role=role, sagemaker_session=sess3 )----> 4 lang_id.deploy(initial_instance_count=1, instance_type="ml.t2.medium")56 from sagemaker.deserializers import JSONDeserializer~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/sagemaker/model.py in deploy(self, initial_instance_count, instance_type, serializer, deserializer, accelerator_type, endpoint_name, tags, kms_key, wait, data_capture_config, async_inference_config, serverless_inference_config, **kwargs)11321133         self._create_sagemaker_model(-> 1134             instance_type, accelerator_type, tags, serverless_inference_config1135         )1136~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/sagemaker/model.py in _create_sagemaker_model(self, instance_type, accelerator_type, tags, serverless_inference_config)671             tags=tags,672         )--> 673         self.sagemaker_session.create_model(**create_model_args)674675     def _ensure_base_name_if_needed(self, image_uri, script_uri, model_uri):~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/sagemaker/session.py in create_model(self, name, role, container_defs, vpc_config, enable_network_isolation, primary_container, tags)2715                     raise2716-> 2717         self._intercept_create_request(create_model_request, submit, self.create_model.name)2718         return name2719~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/sagemaker/session.py in _intercept_create_request(self, request, create, func_name)4294             func_name (str): the name of the function needed intercepting4295         """-> 4296         return create(request)42974298~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/sagemaker/session.py in submit(request)2703             LOGGER.debug("CreateModel request: %s", json.dumps(request, indent=4))2704             try:-> 2705                 self.sagemaker_client.create_model(**request)2706             except ClientError as e:2707                 error_code = e.response["Error"]["Code"]~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/botocore/client.py in _api_call(self, *args, **kwargs)506                 )507             # The "self" in this scope is referring to the BaseClient.--> 508             return self._make_api_call(operation_name, kwargs)509510         _api_call.name = str(py_operation_name)~/anaconda3/envs/tensorflow2_p36/lib/python3.6/site-packages/botocore/client.py in _make_api_call(self, operation_name, api_params)909             error_code = parsed_response.get("Error", {}).get("Code")910             error_class = self.exceptions.from_code(error_code)--> 911             raise error_class(parsed_response, operation_name)912         else:913             return parsed_responseClientError: An error occurred (AccessDeniedException) when calling the CreateModel operation: User: arn:aws:sts::XXXXXXXXXX:assumed-role/sagemakeraccesstoservices/SageMaker is not authorized to perform: sagemaker:CreateModel on resource: arn:aws:sagemaker:us-east-2:XXXXXXXXXX:model/blazingtext-2022-08-09-13-58-21-739 because no identity-based policy allows the sagemaker:CreateModel actionFollowComment"

Answer: "0Based on your description I understand that you are trying to create a Model using the Amazon SageMaker Python SDK with an assumed IAM Role with the AmazonSagemakerFullAccess policy, which should allow sagemaker:CreateModel.It's difficult to identify what the underlying issue is since multiple IAM mechanisms (like SCPs or explicit Denies) can prevent the sagemaker:CreateModel permission.To work towards a solution I would recommend:Simulate the sagemaker:CreateModel action using the IAM Policy Simulator with your User/Role. This may identify the root cause for your issue and how it can be fixed.Open an AWS Support ticket describing the issue. AWS Support engineers are highly trained, experienced and well equipped to provide you with timely assistance.CommentShareJohann Fuechslanswered 10 months ago"


Question: AWS AMI Creation Stuck for a long time even after EBS snapshots are available (100%)

"We are using EC2ImageBuilder to build AMIs but the AMI creation gets stuck after the EBS snapshot are created (available 100%). There is also no visibility to track the progress of AMI creation. The same AMI creation (with exactly same configuration) was being completed within an hour couple of days back.Are there any additional time intensive steps taken post snapshot creation for building AMI? And is there a way to track the progress, root cause and speed up AMI creation?Instance configuration : (EBS Volume size : 50gb, instanceType : g4dn.8xlarge)(PS: We are using ecs optimized gpu AMI as base AMI and the only additional step is that we're downloading a docker image (~ 15 GB) before taking snapshot)FollowComment"

Answer: "0Are you still having the issue? The following knowledge center article describes few common causes. Please take a look and see if any of them applies. If so, make sure to implement the preventative measures.Why is my EC2 AMI or EBS snapshot creation slow?CommentShareTaka_Manswered 5 months ago"


Question: Cloud 9 IDE Vue.js unable to preview browser on 8080

"Environment: Using t3.small with resized EBS to 20GB; Connecting from: Mac OS (Safari or Chrome - current versions)Repro:nvm install stablenpm install -g @aws-amplify/cli        # optional (unless testing `amplify run`)npm install vuenpm install -g @vue/clivue create testsite# use babel, router, lint; vue3cd testsitenpm run serveAt this point server is running normally with following message:App running at:Local: http://localhost:8080/Network: http://xxx.xxx.xxx.xxx:8080/However Cloud9 reports following error:Cloud9 HelpYou may be using the wrong PORT & IP for your server application.  Try passing port 8080 to properly launch your application.We can continue installing Amplify to show it also fails with amplify run:amplify configure     # create or use existing amplify user passing appropriate key/secret idsamplify init                # use defaultsnpm install aws-amplify @aws-amplify/ui-componentsamplify add auth      # optional - I was trying to test drive Cognito; some code changes required, but not relevant for this testamplify pushamplify runSame result as with npm run serve.Reviewed following references, but did not find any working solutions:https://docs.aws.amazon.com/cloud9/latest/user-guide/app-preview.html#app-preview-run-apphttps://docs.aws.amazon.com/cloud9/latest/user-guide/troubleshooting.html#troubleshooting-app-previewhttps://repost.aws/questions/QUyfyfFI92TO6lN6s6Ti-7Ig/can-no-longer-preview-running-applications-vfs-connection-does-not-existNote: In Chrome this seems to now be "SameParty cookies to be first-party" and in Safari disabling prevent cross-site tracking and block all cookies - neither worked for meWhen I had first started while following the initial Cloud 9 guide I was able to get the preview application to work while using the default t3.micro instance on Safari.  After upgrading to t3.small it did not work any longer, though the t3.micro instance was failing in numerous other ways due to low memory, so this was not a viable setup.  Following through the Cloud 9 instructions to create new environment instances I was unable to get any working Preview scenarios in any of the environments following various variations on the setup and sequencing of the vue3 and vue/cli installation.Any additional suggestions are appreciated.FollowComment"


Question: "Pinpoint, SMS not received (Vietnam)"

"Hi All,I was testing SMS for Vietnam and haven't received yet.I've applied for Pinpoint Sender ID and registered successfully, and I am sure that I sent SMS in the registered templates.My current customer service plan won't get AWS help, so I come here to ask for some support.Many Thanks,Kenny WangFollowComment"

Answer: "0Hi, @KennyWangYou may be able to get post-send failure events, etc. by enabling the event stream.If you want to check the sending status of SMS, first enable the event stream and look for hints.https://docs.aws.amazon.com/pinpoint/latest/developerguide/event-streams.htmlCommentShareEXPERTiwasaanswered a year agoKennyWang a year agoThank you for the kind response, I'll try it now.ShareKennyWang a year agoHi iwasa,Unfortunately, the logs don't really help, and I still can't find out why I still can't receive SMS of Vietnam.Do you know some other solutions maybe? I'll appreciate so much :)Shareiwasa EXPERTa year agoHi, @KennyWangI listened to your contact and checked the documentation again. The following is the information for sending SMS on SNS.https://docs.aws.amazon.com/sns/latest/dg/sns-supported-regions-countries.htmlSenders are required to use a pre-registered alphabetic sender ID. To request a sender ID from AWS Support, file a support request. Some countries require senders to meet specific requirements or abide by certain restrictions in order to obtain approval. In these cases, AWS Support might contact you for additional information after you submit your sender ID request.According to this, it seems that additional procedures are required because sending SMS in Vietnam is restricted.The following Twillio Vietnam SMS Guidelines may also be helpful.https://www.twilio.com/guidelines/vn/smsShareKennyWang a year agoHi iwasa,Thank you for reply.Yes, it comes with the requirements that you mentioned and I've already applied for it, as well as the templates we'd send.The situation is, my account has registered the Sender ID and templates of Vietnam. I sent SMS to China, Indonesia and Vietnam in one time and separated, but the Vietnam end users don't receive anything in both ways.This is really confused @@Share"


Question: Test can't find Chrome

"I'm getting a Error: Activity class {com.android.chrome/com.google.android.apps.chrome.Main} does not exist. error in my Appium logs.My tests specify the following capabilities that I would hope is general enough to work for any device.                platformName: "Android",                "appium:automationName": 'UiAutomator2',                browserName: 'Chrome',Testing on a Google Pixel 6a.I can run my tests locally against both the simulator and a real device.Any pointers? Can I run the Device Farm setup locally for faster testing?FollowComment"


Question: Mounting EFS on a Non Empty Directory

"Hello,can anyone here to help with the mounting of an AWS EFS with a non-empty directory without hiding the current data in that directory. also the data already exists in that directory should be mounted in that EFS.FollowComment"

Answer: "1Yes, you can mount EFS as standard NFS using NFS utils or as EFS using amazon-efs-utils on your linux systems and whatever the data exists on that exported path in EFS, the data will be available to that client.  The behavior to client is same irrespective of empty or non-empty directory. If you have any specific errors when you are mounting or accessing the data, then let me know.https://docs.aws.amazon.com/efs/latest/ug/efs-mount-helper.htmlhttps://docs.aws.amazon.com/efs/latest/ug/mounting-fs-old.htmlCommentShareRRP_AWSanswered 10 months ago"


Question: aws iotsecuretunneling close-tunnel

"I have done the following:aws configure sso (allowed device)aws iotsecuretunneling open-tunnel ....Retrieved the tunnelId from the above command.Tried:aws iotsecuretunneling close-tunnel --tunnel-id xxxx-xxxx-xxxBut I am getting: "Unable to locate credentials. You can configure credentials by running "aws configure"."I want to add the close-tunnel to my script just incase it ends before my tunnel session expires, since when I start a new one, the localproxy command still uses the old/closed one.FollowComment"

Answer: "0Hello,The error indicates missing credentials in the system.As you’re trying to invoke the AWS CLI command from the script you will need to configure the AWS credentials on the device.You can use the AWS user credentials by executing the aws configure CLI command and entering the credentials.However, a better security practice will be to configure the CLI to use an IAM role directly[1].It appears you’re already configuring the AWS CLI to use single-sign-on (SSO) and appears you are getting the credentials from that specific call only, in which case you can use the SSO profile [2] to crate the credentials (Note this involves some manual interaction).References:[1] https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-role.html[2] https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-sso.htmlCommentShareSUPPORT ENGINEERTim_Panswered a year ago"


Question: All development stage in one account

"Hi Folks,I am in a company where we are using AWS and we are having 4 stages as "Development", "Acceptance", "Sandbox" and "Production"for all four we can login at a time then logout and signing to other stage. So we are thinking to have a Dashboard to place all four stages in one place. Where we just can easily switch the stages and get all the services stage wise. So is there any way how can we implement within or outside AWS.FollowComment"

Answer: 0Not 100% this is what you are looking for but it sounds like you want IAM Identity Center (AWS SSO) to switch between your different AWS accounts?  - https://aws.amazon.com/blogs/security/introducing-aws-single-sign-on/ "The users can choose an account and a permission set to sign in to that account without needing to provide a password again."CommentShareEXPERTThaddeus_Wanswered 3 months ago


Question: AppFlow Hubspot Connection not updating the token

"Hi,I have setup the hubspot connection in the AppFlow with all required scopes configured as per https://docs.aws.amazon.com/appflow/latest/userguide/connectors-hubspot.html. After configuring the flow and running it, I have noticed that after some time the ingestion fails and I am getting 401 from HubSpot. The logs on the HubSpot show that the token timed out.To fix it I need to edit connection and re-submit userid and the secret.AppFlow establishes the initial connection with ClientId and Secret however after the first token expired, AppFlow is not renewing it.FollowComment"


Question: .app domain transfer

"Hi all,We own a .app domain and we want to transfer it to Route 53.Actually .app is not a supported TLD.Any idea / suggestion in welcome!FollowComment"

Answer: "1Hi Devops-tn,I understand that you would like to register a domain with .app TLD on AWS however, you were unable to find it. Below is my observation on the same.Unfortunately, as of now .app TLD is not supported on Route 53. Here is the list of TLD that is supported [1]. However, as a workaround you can still choose Route 53 as your DNS service provider for your .app domain registered with a different domain registrar. Refer [2] for more details on how to use Route53 as DNS service provider.AWS does not have a timeline when this domain extension will be added to supported domain names, but you can check it periodically to see if '.app' domain names are available by reviewing this AWS documentation.Additionally I do encourage you to keep in touch with the community pages (What's new page or AWS Blog) so that you know when it does get implemented [3].I hope this information will be helpful. Feel free to reach out if you have any further queries or concern.References:Domains that you can register with Amazon Route 53 - Generic top-level domainsMaking Route 53 the DNS service for a domain that's in useWhat's New with AWSAWS blogCommentShareCebianswered a year ago0I'd like to add to Cebi's answer. Do open an AWS Support Case and let them know your interest. That will help them to add your influence to support additional TLDs (especially .app) by the Route 53 service.CommentShareEXPERTShree_Canswered a year ago0Same issues here no solutionCommentSharedansinghanswered 3 months ago"


Question: BYOL EC2 Instance - Office 365 business Premium License

"Team,  Please suggest if we can install the Office 365 premium license  on EC2 Windows 2022 datacenter edition. We already have office 365 business  premium license  in place.FollowComment"

Answer: "0Hello,Thank you for querying in this forum.From your description, it seems that you want to know if you can apply already purchased Office 365 premium license on EC2 Windows Server 2022.Technically, you should be able to apply your already purchased Office 365 Premium licenses to EC2 Windows, but the clarification of the licensing terms and whether having Office 365 licenses on top of EC2 Windows Server 2022 affects your license agreement? You'll have to contact Microsoft support once to see if that's the case. Anyways. I found a Microsoft document addressing a similar request at the following link.[+] https://answers.microsoft.com/en-us/msoffice/forum/all/microsoft-office-365-licenses-aws-ec2-instance/06ebcb45-5430-46f8-a5c5-dac0e0e7b79eAlso read the license terms and choose the AWS model that fits your needs. In general, there are different products with different levels of BYOL support. Note that while most BYOL scenarios are supported using Dedicated Hosts, only certain scenarios are supported with Dedicated Instances. The application of licenses to EC2 Windows also depends on the license type. This is because certain licensing agreements require the use of dedicated hosts rather than instances running on shared hosts. I also found an article saying that support for running Microsoft 365 Apps on Windows Server 2022 is currently in preview. To start testing on Windows Server 2022, it is recommend to use the latest version of Microsoft 365 Apps supported by Current Channel.[+] https://techcommunity.microsoft.com/t5/windows-server-insiders/windows-server-2022-adds-support-for-microsoft-365-apps/m-p/3653854For final word and confirmation, contact Microsoft support once to avoid any possible license terms violations.Hope the above information helps!!Additional Resources:1. https://aws.amazon.com/windows/faq/2. https://aws.amazon.com/windows/resources/licensemobility/3. https://aws.amazon.com/windows/resources/licensing/CommentSharevaibhav-AWSanswered 6 months ago"