Question: Cross account ecs fargate blue/green deploy from code pipeline

I want have the deploy stage cross account and using code pipeline+code build+code deployi am creating dynamic taskdef.json and app-spec file in the build stage as output and want to include them as input in the cross account deployment.confused on how to achieve the cross account deployment.FollowComment

Answer: "1Hello Piyush,You can follow below document to use resources created or managed by another AWS account.https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-create-cross-account.htmlAdditionally, you can also refer to following AWS Blog which explain about building a Cross-Region/Cross-Account Code Deployment Solution using AWS CodeDeploy and AWS CodePipeline.https://aws.amazon.com/blogs/devops/building-a-cross-regioncross-account-code-deployment-solution-on-aws/Hope above documents will help you to achieve your use-case.CommentShareSUPPORT ENGINEERSatyam_Ganswered a year agoEXPERTPankaj_Areviewed a year ago"


Question: AWS ChatBot not recognising ecs update-service command

"I am trying to create a command from Slack using AWS ChatBot that enables anyone in the channel to perform some AWS CLI commands, in this case it is ecs update-service. I've created an alias as follows@aws alias create restart_service ecs update-service --cluster $cluster-name --service $service-name --force-new-deployment --region ap-southeast-2Then, I was hoping that anyone that run this command@aws run restart_service --cluster-name cluster-a --service-name service-awill just right away execute the command and restart the service.But instead, I received this message as if the AWS ChatBot doesn't understand the command@slack-user - I'm not sure which AWS service or operation you meant by "ecs update-service --cluster cluster-a --service service-a --force-new-deployment --region ap-southeast-2".Did you mean one of the following?ecs update-service --service service-a cluster-a: Modifies the parameters of a service.Is there any solution to this? Thanks!FollowComment"

Answer: "0Please review the following documentationhttps://docs.aws.amazon.com/chatbot/latest/adminguide/chatbot-cli-commands.htmlAs a workaround,you can Create a Lambda function andCreate an IAM role for your Lambda function with the necessary permissions to update the ECS service and thenConfigure AWS ChatBot to allow invoking the Lambda function. This requires adding the necessary permissions to the AWS ChatBot IAM role.Use AWS ChatBot to invoke the Lambda function from Slack, passing the required parameters like cluster-name and service-name.like the following@aws lambda invoke --function-name your_lambda_function_name --payload '{"cluster-name": "cluster-a", "service-name": "service-a"}'CommentShareEXPERTsdtslmnanswered a month ago"


Question: SIGSEGV error during simulation.

"While compiling my desing with the latest version of HDK Kit (HDK_VERSION=1.4.7) and Vivado version 2018.2, I get the following error.ERROR: [XSIM 43-3316] Signal SIGSEGV received.I also found another user having the same error with an hdk example design itself as in thread below.  I am attaching tail my elaborate.log below to provide another datapoint.https://forums.aws.amazon.com/thread.jspa?messageID=890695&#890695WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:475]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:476]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:477]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:478]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:479]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:480]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:481]WARNING: [VRFC 10-1635] non-void function initialize_memory_with_file called as a task without void casting [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:482]WARNING: [VRFC 10-727] function device_bdr_ld has no return value assignment [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/fpga/fpga_ddr.svh:396]WARNING: [VRFC 10-696] first argument of $fatal is invalid, expecting 0, 1 or 2 [/home/asanghi/project/aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/sh_bfm/sh_bfm.sv:2527]WARNING: [VRFC 10-696] first argument of $fatal is invalid, expecting 0, 1 or 2 [/home/asanghi/project/aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/sh_bfm/sh_bfm.sv:2685]WARNING: [VRFC 10-727] function match_char_after has no return value assignment [/home/asanghi/project/valtix-hw/ade/design/rtl_json/http_parser.v:4562]WARNING: [VRFC 10-727] function match_range has no return value assignment [/home/asanghi/project/valtix-hw/ade/design/rtl_json/http_parser.v:4575]WARNING: [VRFC 10-727] function track_value_context has no return value assignment [/home/asanghi/project/valtix-hw/ade/design/rtl_json/http_parser.v:5545]WARNING: [VRFC 10-597] element index 7 into dq_temp is out of bounds [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/ddr4_model/ddr4_model.sv:1571]WARNING: [VRFC 10-597] element index 7 into dq_temp is out of bounds [../../../../../../../../aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/ddr4_model/ddr4_model.sv:1573]WARNING: [VRFC 10-597] element index 143 into sampled_val1_str is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/extract_content_type.v:182]WARNING: [VRFC 10-597] element index 143 into sampled_val1_str is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/extract_content_type.v:195]WARNING: [VRFC 10-1324] repetition multiplier must be positive [/home/asanghi/project/valtix-hw/ade/design/rtl_json/ab_api_key_match.sv:117]WARNING: [VRFC 10-1324] repetition multiplier must be positive [/home/asanghi/project/valtix-hw/ade/design/rtl_json/ab_api_key_match.sv:118]WARNING: [VRFC 10-1324] repetition multiplier must be positive [/home/asanghi/project/valtix-hw/ade/design/rtl_json/len_model_mgmt.sv:320]WARNING: [VRFC 10-597] element index 16 into valid_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:147]WARNING: [VRFC 10-597] element index 16 into sign_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:148]WARNING: [VRFC 10-597] element index 16 into dividend_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:149]WARNING: [VRFC 10-597] element index 16 into dividend_lo_bits_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:150]WARNING: [VRFC 10-597] element index 16 into divisor_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:151]WARNING: [VRFC 10-597] element index 16 into remainder_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:152]WARNING: [VRFC 10-597] element index 16 into quotient_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:153]WARNING: [VRFC 10-597] element index 16 into division_done_in is out of bounds [/home/asanghi/project/valtix-hw/ade/design/rtl_json/divider.v:154]Completed static elaborationWARNING: [XSIM 43-4127] File "/home/asanghi/project/aws_hdk/2018.2/aws-fpga/hdk/common/shell_v04261818/design/ip/ddr4_core/rtl/cal/ddr4_v2_2_cal_cplx.sv" Line 855 : The "System Verilog Assertion" is not supported yet for simulation. The statement will be ignored.WARNING: [XSIM 43-4127] File "/home/asanghi/project/aws_hdk/2018.2/aws-fpga/hdk/common/shell_v04261818/design/ip/ddr4_core/rtl/cal/ddr4_v2_2_cal_top.sv" Line 1753 : The "System Verilog Assertion" is not supported yet for simulation. The statement will be ignored.INFO: [XSIM 43-4329] Assuming default value 1 for the first arguement of $fatal at Line 2527, File /home/asanghi/project/aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/sh_bfm/sh_bfm.svINFO: [XSIM 43-4329] Assuming default value 1 for the first arguement of $fatal at Line 2685, File /home/asanghi/project/aws_hdk/2018.2/aws-fpga/hdk/common/verif/models/sh_bfm/sh_bfm.svERROR: [XSIM 43-3316] Signal SIGSEGV received."elaborate.log" 159L, 29695CFollowComment"

Answer: "0I found the cause for this issue. I isolated the module causing this error and compiled separately. I found that this module had some warnings regarding functions not having defined the return values. After fixing those, this error went away.CommentSharefpgamagicanswered 4 years ago"


Question: Any update on progress with Sumerian rebuild using Babylon?

"I'm really eager to work with Sumerian but have not seen any news in almost a year about the current project status. I would much rather work through Sumerian given its integration with AWS.FollowCommentFisher_XR 6 months agoHello, here is a link to the Sumerian FAQ about the future of Sumerian.https://aws.amazon.com/sumerian/faqs/Share"


Question: EMR serverless on arm64

"I want to configure jar (deequ-2.0.1-spark-3.2.jar) on EMR serverless arm64.This works for x86_64  but doesn't work for arm64 architecture.Could you please consider this matter it gave this error :  https://repos.spark-packages.org/com/amazon/deequ/deequ/2.0.1-spark-3.2/deequ-2.0.1-spark-3.2.jar::::::::::::::::::::::::::::::::::::::::::::::::          UNRESOLVED DEPENDENCIES         :::::::::::::::::::::::::::::::::::::::::::::::::: com.amazon.deequ#deequ;2.0.1-spark-3.2: not found:::: ERRORSServer access error at url https://repo1.maven.org/maven2/com/amazon/deequ/deequ/2.0.1-spark-3.2/deequ-2.0.1-spark-3.2.pom (java.net.ConnectException: Connection timed out (Connection timed out))Server access error at url https://repo1.maven.org/maven2/com/amazon/deequ/deequ/2.0.1-spark-3.2/deequ-2.0.1-spark-3.2.jar (java.net.ConnectException: Connection timed out (Connection timed out))Server access error at url https://repos.spark-packages.org/com/amazon/deequ/deequ/2.0.1-spark-3.2/deequ-2.0.1-spark-3.2.pom (java.net.ConnectException: Connection timed out (Connection timed out))Server access error at url https://repos.spark-packages.org/com/amazon/deequ/deequ/2.0.1-spark-3.2/deequ-2.0.1-spark-3.2.jar (java.net.ConnectException: Connection timed out (Connection timed out)):: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILSException in thread "main" java.lang.RuntimeException: [unresolved dependency: com.amazon.deequ#deequ;2.0.1-spark-3.2: not found]at org.apache.spark.deploy.SparkSubmitUtils$.resolveMavenCoordinates(SparkSubmit.scala:1494)at org.apache.spark.util.DependencyUtils$.resolveMavenDependencies(DependencyUtils.scala:185)at org.apache.spark.deploy.SparkSubmit.prepareSubmitEnvironment(SparkSubmit.scala:311)at org.apache.spark.deploy.SparkSubmit.org$apache$spark$deploy$SparkSubmit$$runMain(SparkSubmit.scala:944)at org.apache.spark.deploy.SparkSubmit.doRunMain$1(SparkSubmit.scala:180)at org.apache.spark.deploy.SparkSubmit.submit(SparkSubmit.scala:203)at org.apache.spark.deploy.SparkSubmit.doSubmit(SparkSubmit.scala:90)at org.apache.spark.deploy.SparkSubmit$$anon$2.doSubmit(SparkSubmit.scala:1090)at org.apache.spark.deploy.SparkSubmit$.main(SparkSubmit.scala:1099)at org.apache.spark.deploy.SparkSubmit.main(SparkSubmit.scala)FollowCommentdacort 15 days agoMake sure you've configured your EMR Serverless application with VPC connectivity. By default, EMR Serverless only has access to a few AWS services in the same region.Share"

Answer: "1Accepted AnswerHi,The error message you encountered indicates that the required dependency, com.amazon.deequ#deequ;2.0.1-spark-3.2, could not be found in the Maven repositories. The connection timeout error suggests that the dependency resolution process failed to retrieve the required files from the Maven repositories.To address this issue, you can try the following solutions:Check Internet Connectivity: Ensure that the EMR serverless arm64 instance has proper internet connectivity to access the Maven repositories. You can test the connectivity by running other commands that require internet access on the instance.Update Maven Repository Configuration: If the instance has internet access, verify that the Maven repository configuration is correct. Check if the Maven repository URLs are properly configured in the settings.xml file located in the .m2 directory in the user's home directory. Make sure the necessary repositories, such as Maven Central and Spark Packages, are included and accessible.Try a Different Repository: If the default Maven repositories are inaccessible, you can try using alternative repositories.Alternatively, you can manually download the required JAR file and its dependencies from a different source and install them on the EMR serverless arm64 instance.CommentShareStefanoBanswered 16 days ago0Thanks.. this was the issue "Check Internet Connectivity " , I didn't configure VPC .CommentSharerePost-User-6281491answered 15 days ago"


Question: Greengrass access local device environment variables

As the title mentioned is there a way to access the device local environment variables while the greengrass is deploying or running the life cycle steps?FollowComment

Answer: "0Accepted AnswerHello,Greengrass components receive environment variables from Greengrass and from the recipe. You may configure any environment variable by using the setEnv key in the recipe. You could also use any number of other methods to load environment variables/configuration from the device, such as by using the source shell command to load a file.CommentShareEXPERTMichaelDombrowski-AWSanswered a year agoMadhav a year agoThanks for the information Michael.Share"


Question: Debug help please - ERROR: main L#190 Error(-12)

"Hello Folks,I seem to be having a problem connecting my client to the IOT server. My IOT console is showing that I'm making connection, however I'm receiving the following error on the client debug output:ERROR: main L#190 Error(-12) connecting to a12j6rskk6eu7d-ats.iot.us-east-1.amazonaws.com:8883I'm new to AWS IOT, and have not yet had my system up and running, so my thought is that I don't have something configured properly.My full client log as well as my configuration is listed below. I'm using the C++ version of the code.Thanks in advance for your help, and please let me know if you need any other further information to assist with the debug.-ShawnCLIENT OUTPUT:root@PCD-FDE2:~/aws_sdk/sample_apps# ./subscribe_publish_sampleAWS IoT SDK Version 3.0.1-DEBUG:   main L#159 rootCA /root/aws_sdk/sample_apps/../certs/rootCA.crtDEBUG:   main L#160 clientCRT /root/aws_sdk/sample_apps/../certs/cert1.crtDEBUG:   main L#161 clientKey /root/aws_sdk/sample_apps/../certs/private1.keyConnecting...DEBUG:   iot_tls_connect L#132. Seeding the random number generator...DEBUG:   iot_tls_connect L#140   . Loading the CA root certificate ...DEBUG:   iot_tls_connect L#146  ok (0 skipped)DEBUG:   iot_tls_connect L#148   . Loading the client cert. and key...DEBUG:   iot_tls_connect L#161  okDEBUG:   iot_tls_connect L#163   . Connecting to a12j6rskk6eu7d-ats.iot.us-east-1.amazonaws.com/8883...DEBUG:   iot_tls_connect L#182  okDEBUG:   iot_tls_connect L#184   . Setting up the SSL/TLS structure...DEBUG:   iot_tls_connect L#225SSL state connect : 0DEBUG:   iot_tls_connect L#228  okDEBUG:   iot_tls_connect L#230SSL state connect : 0DEBUG:   iot_tls_connect L#231   . Performing the SSL/TLS handshake...DEBUG:   _iot_tls_verify_cert L#51Verify requested for (Depth 2):DEBUG:   _iot_tls_verify_cert L#53 cert. version     : 3serial number     : 06:7F:94:4A:2A:27:CD:F3:FA:C2:AE:2B:01:F9:08:EE:B9:C4:C6issuer name       : C=US, ST=Arizona, L=Scottsdale, O=Starfield Technologies, Inc., CN=Starfield Services Root Certificate Authority - G2subject name      : C=US, O=Amazon, CN=Amazon Root CA 1issued  on        : 2015-05-25 12:00:00expires on        : 2037-12-31 01:00:00signed using      : RSA with SHA-256RSA key size      : 2048 bitsbasic constraints : CA=truekey usage         : Digital Signature, Key Cert Sign, CRL Signcertificate policies : Any PolicyDEBUG:   _iot_tls_verify_cert L#56   This certificate has no flagsDEBUG:   _iot_tls_verify_cert L#51Verify requested for (Depth 1):DEBUG:   _iot_tls_verify_cert L#53 cert. version     : 3serial number     : 06:7F:94:57:85:87:E8:AC:77:DE:B2:53:32:5B:BC:99:8B:56:0Dissuer name       : C=US, O=Amazon, CN=Amazon Root CA 1subject name      : C=US, O=Amazon, OU=Server CA 1B, CN=Amazonissued  on        : 2015-10-22 00:00:00expires on        : 2025-10-19 00:00:00signed using      : RSA with SHA-256RSA key size      : 2048 bitsbasic constraints : CA=true, max_pathlen=0key usage         : Digital Signature, Key Cert Sign, CRL Signcertificate policies : ???DEBUG:   _iot_tls_verify_cert L#56   This certificate has no flagsDEBUG:   _iot_tls_verify_cert L#51Verify requested for (Depth 0):DEBUG:   _iot_tls_verify_cert L#53 cert. version     : 3serial number     : 0F:B5:CF:2F:A1:69:48:A1:35:BB:4A:A8:5E:97:C0:ABissuer name       : C=US, O=Amazon, OU=Server CA 1B, CN=Amazonsubject name      : CN=*.iot.us-east-1.amazonaws.comissued  on        : 2020-04-03 00:00:00expires on        : 2021-04-03 12:00:00signed using      : RSA with SHA-256RSA key size      : 2048 bitsbasic constraints : CA=falsesubject alt name  :dNSName : iot.us-east-1.amazonaws.comdNSName : *.iot.us-east-1.amazonaws.comkey usage         : Digital Signature, Key Enciphermentext key usage     : TLS Web Server Authentication, TLS Web Client Authenticationcertificate policies : ???, ???DEBUG:   _iot_tls_verify_cert L#56   This certificate has no flagsDEBUG:   iot_tls_connect L#248  ok[ Protocol is TLSv1.2 ][ Ciphersuite is TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256 ]DEBUG:   iot_tls_connect L#250     [ Record expansion is 29 ]DEBUG:   iot_tls_connect L#255   . Verifying peer X.509 certificate...DEBUG:   iot_tls_connect L#264  okDEBUG:   iot_tls_connect L#274   . Peer certificate information    ...DEBUG:   iot_tls_connect L#276       cert. version     : 3serial number     : 0F:B5:CF:2F:A1:69:48:A1:35:BB:4A:A8:5E:97:C0:ABissuer name       : C=US, O=Amazon, OU=Server CA 1B, CN=Amazonsubject name      : CN=*.iot.us-east-1.amazonaws.comissued  on        : 2020-04-03 00:00:00expires on        : 2021-04-03 12:00:00signed using      : RSA with SHA-256RSA key size      : 2048 bitsbasic constraints : CA=falsesubject alt name  :dNSName : iot.us-east-1.amazonaws.comdNSName : *.iot.us-east-1.amazonaws.comkey usage         : Digital Signature, Key Enciphermentext key usage     : TLS Web Server Authentication, TLS Web Client Authenticationcertificate policies : ???, ???ERROR: main L#190 Error(-12) connecting to a12j6rskk6eu7d-ats.iot.us-east-1.amazonaws.com:8883root@PCD-FDE2:~/aws_sdk/sample_apps#CLIENT CONFIG:// =================================================#define AWS_IOT_MQTT_HOST              "a12j6rskk6eu7d-ats.iot.us-east-1.amazonaws.com" ///< Customer specific MQTT HOST. The same will be used for Thing Shadow#define AWS_IOT_MQTT_PORT              8883 ///< default port for MQTT/S#define AWS_IOT_MQTT_CLIENT_ID         "arn:aws:iot:us-east-1:901916029934:thing/pcd2" ///< MQTT client ID should be unique for every device#define AWS_IOT_MY_THING_NAME              "arn:aws:iot:us-east-1:901916029934:thing/pcd2" ///< Thing Name of the Shadow this device is associated with#define AWS_IOT_ROOT_CA_FILENAME       "rootCA.crt" ///< Root CA file name#define AWS_IOT_CERTIFICATE_FILENAME   "cert1.crt" ///< device signed certificate file name#define AWS_IOT_PRIVATE_KEY_FILENAME   "private1.key" ///< Device private key filename// =================================================FollowComment"

Answer: 0I figured it out. I didn't have my policy set up correctly on the server side.CommentSharePerkinsInnovationanswered 3 years ago


Question: "Getting started with AWS IoT Core" Shadow Python scripts get connection exception

"Using "Getting started with AWS IoT Core" to generate Python scripts. The basicPubSub.py sample script works fine. The Shadow examples, basicShadowDetailListener.py, basicShadowUpdater.py and ThingShadowEcho.py all get connection timeout exception when run.2022-04-03 13:08:49,371 - AWSIoTPythonSDK.core.protocol.mqtt_core - ERROR - Connect timed outTraceback (most recent call last):File "/home/pi/connect_device_package/aws-iot-device-sdk-python/samples/basicShadow/basicShadowDeltaListener.py", line 110, in <module>myAWSIoTMQTTShadowClient.connect()File "/usr/local/lib/python3.9/dist-packages/AWSIoTPythonSDK/MQTTLib.py", line 1278, in connectreturn self._AWSIoTMQTTClient.connect(keepAliveIntervalSecond)File "/usr/local/lib/python3.9/dist-packages/AWSIoTPythonSDK/MQTTLib.py", line 520, in connectreturn self._mqtt_core.connect(keepAliveIntervalSecond)File "/usr/local/lib/python3.9/dist-packages/AWSIoTPythonSDK/core/protocol/mqtt_core.py", line 199, in connectraise connectTimeoutException()AWSIoTPythonSDK.exception.AWSIoTExceptions.connectTimeoutExceptionThe IoT client and Shadow client appear to have the same connection configuration parametersAWSIoTMQTTShadowClient configurationmyAWSIoTMQTTShadowClient.configureAutoReconnectBackoffTime(1, 32, 20)myAWSIoTMQTTShadowClient.configureConnectDisconnectTimeout(10)  # 10 secmyAWSIoTMQTTShadowClient.configureMQTTOperationTimeout(5)  # 5 secAWSIoTMQTTClient connection configurationmyAWSIoTMQTTClient.configureAutoReconnectBackoffTime(1, 32, 20)myAWSIoTMQTTClient.configureOfflinePublishQueueing(-1)  # Infinite offline Publish queueingmyAWSIoTMQTTClient.configureDrainingFrequency(2)  # Draining: 2 HzmyAWSIoTMQTTClient.configureConnectDisconnectTimeout(10)  # 10 secmyAWSIoTMQTTClient.configureMQTTOperationTimeout(5)  # 5 secFollowCommentAWS-User-5524412 a year agoRunning basicPubSub.py results in a 'connack'. Running basicShadowDeltaListener.py results in a 'disconnect' with the same parameters used.2022-04-06 08:00:49,884 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Produced [connack] event2022-04-06 08:02:12,820 - AWSIoTPythonSDK.core.protocol.internal.workers - DEBUG - Produced [disconnect] eventShare"

Answer: "0Hi,the IoT policy that is created by the "getting started" guide in the IoT Core console does not have permissions to interact with the shadow.The shadow delta listener uses by default the client id basicShadowDeltaListener which is not allowed in the policy.The policy does not include permissions to interact with the device shadow topicsFor me the following modified policy works with the basicShadowDeltaListener in case you use repost as thing name and client id:{  "Version": "2012-10-17",  "Statement": [    {      "Effect": "Allow",      "Action": [        "iot:Publish",        "iot:Receive",        "iot:RetainPublish"      ],      "Resource": [        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topic/sdk/test/java",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topic/sdk/test/Python",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topic/topic_1",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topic/topic_2",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topic/$aws/things/repost/shadow/*"      ]    },    {      "Effect": "Allow",      "Action": "iot:Subscribe",      "Resource": [        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topicfilter/sdk/test/java",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topicfilter/sdk/test/Python",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topicfilter/topic_1",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topicfilter/topic_2",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:topicfilter/$aws/things/repost/shadow/*"      ]    },    {      "Effect": "Allow",      "Action": "iot:Connect",      "Resource": [        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:client/sdk-java",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:client/basicPubSub",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:client/repost",        "arn:aws:iot:REPLACE_WITH_YOUR_AWS_REGION:REPLACE_WITH_YOUR_AWS_ACCOUNT_NUMBER:client/sdk-nodejs-*"      ]    }  ]}You can find more information about IoT Policies in the developer guide.KR,PhilippCommentSharePhilipp Sanswered a year agoAWS-User-5524412 a year agoThanks for your response. After applying the policy changes mentioned, the   connection issue still persists.SharePhilipp S a year agoDid you use "repost" for thing name and client id? If not you need to modify the policy accordingly. You can also take a look at CloudWatch logs (insights) to find connection errors.ShareAWS-User-5524412 a year agoChanged the "repost" to the name of my ThingShareAWS-User-5524412 a year agoPublishing the get topic to the shadow from the MQTT Test Client returns get/accepted$aws/things/GatewayPi4/shadow/get/acceptedApril 06, 2022, 12:16:07 (UTC-0700){"state": {},"metadata": {},"version": 3,"timestamp": 1649272567}$aws/things/GatewayPi4/shadow/getApril 06, 2022, 12:16:07 (UTC-0700){"message": "Hello from AWS IoT console"}ShareAWS-User-5524412 a year agopublishing to the reserved shadow topics works, but subscribing to reserved topics fails.ShareShow 1 more comment"


Question: "Filters, IN comparison operator,  toDynamoDBFilterExpression()"

"Hi,This is not a question, but a solution to a problem we were having.Me and my team wanted to filter a query by comparing a field with different values in a list. Something like this:query listCars{listCars(filter:{ car_color: {in: ['red', 'black']}}){car_namecar_color}}Note the in comparison operator.We found that the resolver for that filter input was calling a function: toDynamoDBFilterExpression(), for example:{  "version": "2017-02-28",  "operation": "Scan",  "filter": #if($context.args.filter) $util.transform.toDynamoDBFilterExpression($ctx.args.filter) #else null #end,  "limit": $util.defaultIfNull($ctx.args.limit, 20),  "nextToken": $util.toJson($util.defaultIfNullOrEmpty($ctx.args.nextToken, null)),}That function transforms the filter input according to the documentation (https://docs.aws.amazon.com/appsync/latest/devguide/resolver-util-reference.html).Now Appsync autogenerates code for the TableStringFilterInput, but it doesnt include the in operator. The question is, does this function support this operator?We found that adding the in operator in the schema is sufficient to make it work:input TableStringFilterInput {  ne: String  eq: String  le: String  lt: String  ge: String  gt: String  in: [String]  contains: String  notContains: String  between: [String]  beginsWith: String}Then we could run the query at the beginning of this post.FollowComment"

Answer: "0Thank you for the investigation. If you would like to make this change permanent I know the team is happy to review PRs. It looks like your change could be made permanent if added to the logic rooted here: https://github.com/aws-amplify/amplify-cli/blob/00ed819419a4959a6d62da2fc5477621c046eff0/packages/graphql-dynamodb-transformer/src/definitions.ts#L437.CommentShareparismicanswered 4 years ago0marked thread as answeredEdited by: Chagui on May 27, 2020 9:29 AMCommentShareChaguianswered 3 years ago"


Question: EMR Spark output file consolidation in S3

"Can you suggest a good way to consolidate partitioned Spark data into a single CSV file. From what is seen online, the simple Spark approach to combining data (repartition or coalesce) performs poorly and it is recommended to output as partitioned data files and then combine them into one.s3-dist-cp seems to be the right utility to use here, but one thing that is not clear is how to keep one set of headers at the top of the combined csv file.Is there a simple way to consolidate output files while stripping all but one file headers?FollowComment"

Answer: "1Accepted AnswerIt is not that s3-dist-cp is better than Spark at this particular problem. The problem by it's very definition is a bottleneck - i.e. multiple input files can be read by multiple readers but has to be merged into one output file by a single writer. s3-dist-cp will use multiple mappers to read the input files and a single reducer to write the output file. Spark will do the same, multiple executors can be used to read the input files but the eventual coalesce will consolidate to a single executor/partition to write the final file. Spark should actually be faster as the intermediate data will be in memory than s3-dist-cp which will save intermediate files to disk.s3-dist-cp does perform better when the output is being saved in S3, and a lot of files are being written out to S3. This is because Spark does a more complicated path of writing files to a temp directory in S3 and then finally renaming all files to the main directory, and those are expensive steps in S3.Here Spark and coalesce(1) are the best options, and the output file should be saved to HDFS. Once the final file is in HDFS, use the AWS S3 cli to copy the file to S3, if that is where it needs to be. Spark can recognize headers in CSV files and can insert headers in output CSV files as well, so there would be no additional effort to strip or add headers.CommentShareAWS-User-4669487answered 5 years ago"


Question: AWS Codebuild: docker run options

"I have a build project in AWS CodeBuild. This project uses a docker image stored in AWS ECR. I have to modify the options which are used to run the container - specifically, I want to add --init. I see there is a initProcessEnabled option which can be used for ECS, but I don't understand how to combine this with CodeBuild.FollowCommentMichael_F EXPERTa year agoCan you tell us what problem you're trying to solve, exactly? Why do you want to add --init?Share"

Answer: "0If you are using tini, in the buildspec.yml file, within the build phase, you could run the docker run --init... command. The buildspec.yml file syntax can be seen here.CommentSharejimmyrayanswered a year agomax a year agoThanks for your reply, but I am still confused.In my understanding the commands specified in the build phase are the ones which are executed within the container which is specified in the environment section.I would like to modify the docker run which is used as environment. Is it possible?If not, I think I should run again a docker with the init optionShare"


Question: I can't connect to virtual server

"I was connecting to a virtual server that I opened in about 3 days without any problems. When I try to connect today, I cannot connect to the virtual server. I've rebooted several times and still can't log in. What could be the reason for this?FollowCommentjoahna a month agoWhat are you using to connect to your virtual server? Did your IP address change? Also, have you already checked the security group of your EC2?Share"

Answer: "0In the AWS console, verify that your EC2 instance is running. And verify that its public IP address is the same as 3 days ago (if the instance was stopped for a while and then restarted its public IP will have changed).Verify the inbound rules for the security group that is applied to your instance, looking for TCP port 22 (if it's Linux) or TCP port 3389 (if it's Windows). Is it allowing inbound connections from anywhere (0.0.0.0/0) or only your IP address.If it's only allowing connections from your IP address then is this still the same today as it was 3 days ago? Your IP is going to be different at home compared to in the office, and different again if you are on a VPN while WFH. Even if you're always at home, your home IP may change periodically depending on your ISP.CommentShareRWCanswered a month ago"


Question: Sonarqube version upgradation

I want upgrade my sonarqube version from 6.7 to 9.7 in Aws Ec2 machine.How to upgrade .pls guide.FollowComment

Answer: "0Should be no different from how you would upgrade it on your on-prem machine. Having said that, your chances of getting a good response are higher if you post this question on the Sonarqube Community Forum https://www.sonarqube.org/community/CommentShareEXPERTIndranil Banerjee AWSanswered 7 months agoEXPERTBrettski-AWSreviewed 7 months ago"


Question: "ERROR: [Synth 8-5809] Error generated from encrypted envelope, Failed to read verilog"

"Hi,I am new to AWS EC2 F1 FPGAs. I am trying to build cl_helloworld.sv example. When I am compiling synthesis failing due to following error.ERROR: [Synth 8-5809] Error generated from encrypted envelope. [/home/centos/aws-fpga/hdk/cl/examples/cl_hello_world/build/src_post_encryption/cl_hello_world.sv:470]Failed to read verilog '/home/centos/aws-fpga/hdk/cl/examples/cl_hello_world/build/src_post_encryption/cl_hello_world.sv'INFO: [Common 17-83] Releasing license: Synthesis10 Infos, 9 Warnings, 0 Critical Warnings and 2 Errors encountered.synth_design failedERROR: [Common 17-69] Command failed: Synthesis failed - please see the console or run log file for detailsCould someone help to resolve this error?Thanks,SaichandFollowComment"

Answer: "0This error message suggests that there's an issue with the encrypted envelope for the cl_helloworld example in AWS EC2 F1 FPGA. It seems like the encrypted Verilog file failed to be read during synthesis, causing the synth_design process to fail.To resolve the issue, you could try the following steps:Check the file path of the encrypted Verilog file to ensure it's correct and readable.Check the permissions of the file and the directories to ensure they are set correctly.If the file path is correct and the permissions are set correctly, try re-encrypting the Verilog file.If re-encrypting doesn't work, try to compile a different example to see if it's a general issue with the AWS EC2 F1 FPGA setup or just with this specific example.CommentShareDivyam Chauhananswered 4 months agorePost-User-8756111 4 months agoHi Divyam,Thank you for the suggestions.I checked file path of the encrypted Verilog file it is correct and readable.I checked the permissions of the file and the directories and found them to be correctly set.I re-encrypted the Verilog file by deleting the older encrypted file and a new file got created.I tried compiling cl_dram_dma example and I find same error which is as below.ERROR: [Synth 8-5809] Error generated from encrypted envelope. [/home/centos/aws-fpga/hdk/common/shell_v04261818/design/ip/ila_vio_counter/hdl/xsdbm_v3_0_vl_rfs.v:1]ERROR: [Synth 8-5809] Error generated from encrypted envelope. [/home/centos/aws-fpga/hdk/common/shell_v04261818/design/ip/ila_vio_counter/hdl/xsdbm_v3_0_vl_rfs.v:1]Failed to read verilog '/home/centos/aws-fpga/hdk/common/shell_v04261818/design/ip/ila_vio_counter/hdl/xsdbm_v3_0_vl_rfs.v'INFO: [Common 17-83] Releasing license: Synthesis10 Infos, 14 Warnings, 0 Critical Warnings and 3 Errors encountered.synth_design failedERROR: [Common 17-69] Command failed: Synthesis failed - please see the console or run log file for detailsThanks,Saichand.Share0Hi Saichand,Thank you for being interested in F1 instance. Divyam has really good points. Can you please check those points and make sure you see the encrypted cl_hello_world.sv under /src_post_encryption. I recommend you double check and ensure that you are following the steps here (https://github.com/aws/aws-fpga/tree/master/hdk#getting-started) for building the cl_hello_world example. In addition, can you please let me know if you're running this test on a EC2 instance or on an on-prem machine?Thanks,ChenCommentShareAWS-zhczanswered 4 months agorePost-User-8756111 4 months agoHi Chen,Thank you for the suggestions.I am running the example on EC2 t2.nano instance using FPGA Developer AMI and Vivado 2022.1v.I can access encrypted cl_hello_world.sv under /src_post_encryptionI followed all the steps mentioned in https://github.com/aws/aws-fpga/tree/master/hdk#getting-startedI also want to mention couple of things here hoping to helping to resolve the errors.While running hdk_setup.sh there was an ERROR: Vivado v2022.1 (64-bit) is not supported by this HDK release.To resolve the above error I added v2022.1 in supported_vivado_versions.txt.Then the hdk_setup.sh ran successfully.While running the build there was the following errorERROR: YOUR INSTANCE has less memory than is necessary for certain builds. This means that your builds will take longer than expected.I am using following command:./aws_build_dcp_from_cl.sh -ignore_memory_requirement -notifyto ignore and bypass the errorApart from the encrypted envelop  errors that mentioned earlier there was a WARNING: [Vivado 12-13651] The IP file '/home/centos/src/project_data/aws-fpga/hdk/common/shell_v04261818/design/ip/vio_0/vio_0.xci' has been moved from its original location, as a result the outputs for this IP will now be generated in '/home/centos/src/project_data/aws-fpga/hdk/common/shell_v04261818/design/ip/vio_0'. Alternatively a copy of the IP can be imported into the project using one of the 'import_ip' or 'import_files' commands.Thanks,Saichand.Share0Hi Saichand,I want to double check the branch you used for this job that generated the synthesis error. Since you're using Vivado v2022.1, you would need to switch to the branch "REL_2022_1" (https://github.com/aws/aws-fpga/tree/REL_2022_1) in order to build those CL examples. My guess is that you were using the main branch. If so, please switch the branch and try again. You should be unblocked.In addition, please be careful about the memory error and the usage of the "-ignore_memory_requirement" option. Xilinx recommends at least 32GB memory space, so a bigger instance type is recommended.Please let us know if you're still facing any problem.Thanks,ChenCommentShareAWS-zhczanswered 3 months agoSaichand Samudrala 3 months agoHi Chen,Thank you for the suggestions.I will try synthesis by switching to the branch "REL_2022_1" and get back on it.Regards,Saichand.Share0Hi Saichand,Thank you for your patience and all the information provided. That's very helpful. I'll further investigate this issue on my end to see if I can replicate this. I'll keep you updated asap.Thanks,ChenCommentShareAWS-zhczanswered 4 months ago"


Question: Can't Create Channel in AWS Managed Blockchain

"Hi,I've encountered an error while following this step in the AMB docs:https://docs.aws.amazon.com/managed-blockchain/latest/hyperledger-fabric-dev/get-started-create-channel.html#get-started-create-channel-create-channelWhen I execute the command for creating a channel:docker exec cli peer channel create -c mychannel -f /opt/home/mychannel.pb -o $ORDERER --cafile /opt/home/managedblockchain-tls-chain.pem --tlsI got this error message:Error: failed to create deliver client for orderer: orderer client failed to connect to orderer.n-2xq2mxyg2vhf5cmce4ystjjgda.managedblockchain.ap-southeast-1.amazonaws.com:30001: failed to create new connection: context deadline exceededPlease tell me if the error message means something.Thanks.FollowCommentJC 10 months agoIs this error persistent or have you beed able to create this channel yet?ShareRichard 10 months agoI've just opened access to port 30001 on SG.Right now, the error message is:2022-08-01 12:56:40.482 UTC [channelCmd] InitCmdFactory -> INFO 001 Endorser and orderer connections initializedError: got unexpected status: BAD_REQUEST -- error applying config update to existing channel 'mychannel': error authorizing update: error validating ReadSet: proposed update requires that key [Group]  /Channel/Application be at version 0, but it is currently at version 1ShareSuhan 10 months agoIt sounds like the channel is created already.  Can you trydocker exec cli peer channel listShare"

Answer: 1It sounds like the channel is created already.  Can you try to join peer to the channel?CommentShareSuhananswered 10 months agoJC 10 months agodocker exec cli peer channel listShare


Question: How to pass null/Nan values into the dataframe passed into batch transform

"I am trying to make inference using my Xgboost model on a dataset which has NaN values, now inherently Xgboost handles the NaN values, it does not throw any error while training with NaN values whereas the batch transform job gives the error ''could not convert string to float'' when it encounters NaN values into the dataset that is to be transformed.Can anyone help me as to how can I pass NaN values into my input dataset for the batch transform job?Thanks a ton!FollowComment"

Answer: "0Hi bharat-patidar,Thanks for your interest in Amazon SageMaker XGBoost. We recently made a change to address empty values in the dataset. Now you should be able to pass empty strings or "NaN" strings with CSV data. Can you please verify and let us know if the change addresses the issue at your end?Thanks!Regards,Amazon SageMaker TeamCommentShareAWS-User-6593450answered 4 years ago"


Question: Unassigned ticket past 3 days

Fri Dec 10 2021 I submitted a support case (case ID: 9331878621) that is still unassigned. Can someone from AWS Support please take respond to it? Thanks.FollowComment

Answer: "0Thank you for providing your case ID.First off, I would like to say, I'm terribly sorry for this frustration. This isn't the experience we want for you or any of our customers.Although, I'm unable to share any account or case specific details via this platform. I can tell you that I’ve reached out internally on your behalf to get your case addressed. I'd ask, in the meantime, that you keep a close eye on your email for a response from our Support team. Please be sure to monitor any spam/junk folders you may have as well, just in case our reply gets filtered to a different location.Thank you,Randi S.CommentShareEXPERTAWS Support - Randianswered a year agorshukayl a year agoUnfortunately, it is still Unassigned.Share"


Question: Elastic Beanstalk Configuration update

"Hi,I changed my Elastic Beanstalk Configuration last time in December, but now I logged today and i can see new elastic beanstalk configuration panel and i can not update in it anything. If i change something and click "continue" or "apply" there is nothing changed and i can not see any information about error. May you help me what is wrong?FollowComment"

Answer: "1It's possible that there may be a compatibility issue between your Elastic Beanstalk environment and the new configuration panel.You may want to try updating the Elastic Beanstalk CLI to the latest version and then try updating your environment configuration through the CLI. This will allow you to see any error messages that may be preventing your configuration changes from being applied.Alternatively, you can try creating a new Elastic Beanstalk environment with the desired configuration settings and deploy your application to the new environment. This will allow you to start fresh with the new configuration panel.If neither of these options work, you may want to contact AWS Support for further assistance in troubleshooting the issue.CommentShareAWS_Guyanswered 3 months ago"


Question: unable to access S3 log files owned by "s3-log-service"

"I'm getting access denied when trying to access s3 log files.This is a corporate account so i dont have root access. My user account, as well as the account i use with aws cli both have "administrator access" in iam.I have 2 buckets that have logging enabled (Server access logging) and are writing their logs to a third bucket. all 3 buckets are in the same account.I am completely unable to access these log files:via aws gui, i can see the files, i can open their details, but any method i try to download them always results in the access denied xml response.via aws cli using aws s3 sync, again, access denied error.in lambda, with a policy that allows get object on all keys in the third bucket, also access denied.Looking at the log file details i can see they are owned by s3-log-service. I do not want to make the files public (public is completely disabled on this bucket).the end goal is option 3 above, i need to have a lambda script that parses the s3 log files so it needs to be able to read them. Manually updating the log files is not really an option as the flow should be fully automated. There there an iam policy or similar that needs to be configured to ensure the lambda has access to the s3-log-service owned files?thanks!Edited by: Thomas Smart on Dec 4, 2019 9:26 PMFollowComment"

Answer: "0ok this was a case of RTFM.If you have KMS managed encryption enabled on the bucket where you are storing logs, you will get this error. This is noted on the manual page for server access logs.CommentShareThomasanswered 3 years ago"


Question: lambda import layer in nodejs

"Hello everyone,I am desperately trying to call my layer's functions inside a lambda function.But at build or at runtime the function does not find the layer :(template.yaml  HelpersLayer:    Type: AWS::Serverless::LayerVersion    Properties:      LayerName: HelpersLayer      Description: HelpersLayer      ContentUri: ./helpers-layer      CompatibleRuntimes:        - nodejs16.x  ApiSaasTestFunction:    Type: AWS::Serverless::Function    Properties:      CodeUri: api/saas/test/      Handler: app.lambdaHandler      Runtime: nodejs16.x      Architectures:        - x86_64      Layers:        - !Ref HelpersLayerthe helperhelpers-layernodejsnode_modulesmongoHandlerindex.jspackage.jsonindex.js content :module.exports.executeStatement = async(params) => {  console.log('mongoHandler start')  return { statusCode: 200, body: JSON.stringify({ message: 'mongoHandler OK'} ) }}lambda app.ts :const mongoHandler = require('/opt/nodejs/mongoHandler')sam build =>Build FailedError: NodejsNpmEsbuildBuilder:EsbuildBundle - Esbuild Failed: ✘ [ERROR] Could not resolve "/opt/nodejs/mongoHandler"    app.ts:6:29:      6 │ const mongoHandler = require('/opt/nodejs/mongoHandler')        ╵                              ~~~~~~~~~~~~~~~~~~~~~~~~~~how should it be done?Have a nice day, JulienFollowComment"

Answer: 0You did not specify which version of SAM CLI you were using. The information I am providing below is based on SAM CLI version 1.55.0.So your layer code doesn't really follow your local hierarchy or include the name of the layer itself. The warning you get of the missing package.json is a warning that tells you the code is not been placed where you expect.You need to remove the nodejs folder so your code looks like this:├── layers/│   └── SQLLayer/       │      ├── package.json│      └── index.tsThis will create a layer with the current hierarchy├── nodejs/│   ├── package.json│   └── index.tsIn your actual Lamabda function this will look like this├── /opt/│   └── nodejs/       │      ├── package.json│      └── index.tsCommentShareEXPERTDaniel ABIBanswered 5 months ago


Question: Containers based on Red Hat UBI 8 not scanned in ECR by Amazon Inspector

"Hello,I pushed containers based on Red Hat UBI 8, which is a subset of RHEL 8. More than that, as stated by Red Hat: "UBI is RHEL. It’s not a downstream rebuild" (source: https://developers.redhat.com/blog/2019/10/09/what-is-red-hat-universal-base-image).Problem is: my containers are not scanned by Amazon Inspector. When I click on "See findings" in "Vulnerabilities" column I got "Scan status: UNSUPPORTED_IMAGE". The documentation mentions RHEL 8 as being supported though: https://docs.aws.amazon.com/inspector/latest/user/supported.htmlI don't know how Inspector determines the OS in use but it seems it does not properly recognize UBI as RHEL (content of '/etc/redhat-release' file on UBI is clear enough: "Red Hat Enterprise Linux release 8.5 (Ootpa)").Any idea?ThanksFollowComment"

Answer: "0Accepted AnswerFYI I did open a case at AWS support and they were able to repro the issue. It happens that the issue can be seen when you use podman to build images. Such images, once pushed into ECR, will show "UNSUPPORTED_IMAGE" scan status.They now have fixed that and ECR Enhanced Scanning works properly on both Docker and Podman built images.CommentShareAWS-User-4447491answered a year ago0I tried to push ubi8/ubi:8.5-200 in my environment.As a result, a scan was performed, and one vulnerability was detected.Here is the result of referring to findings in AWS CLI.$ aws inspector2 list-findings{    "findings": [        {            "awsAccountId": "123456789012",            "description": "A flaw was found in the way Unicode standards are implemented in the context of development environments, which have specialized requirements for rendering text. An attacker could exploit this to deceive a human reviewer by creating a malicious patch containing well placed BiDi characters. The special handling and rendering of those characters can be then used in an attempt to hide unexpected and potentially dangerous behaviour from the reviewer.",            "findingArn": "arn:aws:inspector2:ap-northeast-1:123456789012:finding/0b9c60a7b1ddba6e914d21aa04cf****",            "firstObservedAt": "2021-12-23T03:06:02.647000+00:00",            "inspectorScore": 8.5,            "inspectorScoreDetails": {                "adjustedCvss": {                    "adjustments": [],                    "cvssSource": "REDHAT_CVE",                    "score": 8.5,                    "scoreSource": "REDHAT_CVE",                    "scoringVector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",                    "version": "3.1"                }            },            "lastObservedAt": "2021-12-23T03:06:02.647000+00:00",            "packageVulnerabilityDetails": {                "cvss": [                    {                        "baseScore": 8.5,                        "scoringVector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H",                        "source": "REDHAT_CVE",                        "version": "3.1"                    },                    {                        "baseScore": 5.1,                        "scoringVector": "AV:N/AC:H/Au:N/C:P/I:P/A:P",                        "source": "NVD",                        "version": "2.0"                    },                    {                        "baseScore": 8.3,                        "scoringVector": "CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H",                        "source": "NVD",                        "version": "3.1"                    }                ],                "referenceUrls": [                    "https://access.redhat.com/errata/RHSA-2021:4037",                    "https://access.redhat.com/errata/RHSA-2021:4730",                    "https://access.redhat.com/errata/RHSA-2021:4598",                    "https://access.redhat.com/errata/RHSA-2021:4036",                    "https://access.redhat.com/errata/RHSA-2021:4596",                    "https://access.redhat.com/errata/RHSA-2021:4035",                    "https://access.redhat.com/errata/RHSA-2021:4034",                    "https://access.redhat.com/errata/RHSA-2021:4694",                    "https://access.redhat.com/errata/RHSA-2021:4595",                    "https://access.redhat.com/errata/RHSA-2021:4039",                    "https://access.redhat.com/errata/RHSA-2021:4038",                    "https://access.redhat.com/errata/RHSA-2021:4599",                    "https://access.redhat.com/errata/RHSA-2021:4590",                    "https://access.redhat.com/errata/RHSA-2021:4033",                    "https://access.redhat.com/errata/RHSA-2021:4594",                    "https://access.redhat.com/errata/RHSA-2021:4593",                    "https://access.redhat.com/errata/RHSA-2021:4592",                    "https://access.redhat.com/errata/RHSA-2021:4591",                    "https://access.redhat.com/errata/RHSA-2021:4649",                    "https://access.redhat.com/errata/RHSA-2021:4669",                    "https://access.redhat.com/errata/RHSA-2021:4724",                    "https://access.redhat.com/errata/RHSA-2021:4729",                    "https://access.redhat.com/errata/RHSA-2021:4587",                    "https://access.redhat.com/errata/RHSA-2021:4586",                    "https://access.redhat.com/errata/RHSA-2021:4585",                    "https://access.redhat.com/errata/RHSA-2021:4723",                    "https://access.redhat.com/errata/RHSA-2021:4602",                    "https://access.redhat.com/errata/RHSA-2021:4601",                    "https://access.redhat.com/errata/RHSA-2021:4600",                    "https://access.redhat.com/errata/RHSA-2021:4743",                    "https://access.redhat.com/errata/RHSA-2021:4589",                    "https://access.redhat.com/errata/RHSA-2021:4588"                ],                "relatedVulnerabilities": [],                "source": "REDHAT_CVE",                "sourceUrl": "https://access.redhat.com/security/cve/CVE-2021-42574",                "vendorCreatedAt": "2021-11-01T00:00:00+00:00",                "vendorSeverity": "Moderate",                "vulnerabilityId": "CVE-2021-42574",                "vulnerablePackages": [                    {                        "arch": "X86_64",                        "epoch": 0,                        "name": "libgcc",                        "packageManager": "OS",                        "release": "3.el8",                        "sourceLayerHash": "sha256:ce3c6836540f978b55c511d236429e26b7a45f5a6f1204ab8d4378afaf77332f",                        "version": "8.5.0"                    },                    {                        "arch": "X86_64",                        "epoch": 0,                        "name": "libstdc++",                        "packageManager": "OS",                        "release": "3.el8",                        "sourceLayerHash": "sha256:ce3c6836540f978b55c511d236429e26b7a45f5a6f1204ab8d4378afaf77332f",                        "version": "8.5.0"                    }                ]            },            "remediation": {                "recommendation": {                    "text": "This issue can be mitigated by ensuring code commits get a proper review. All new commits can also be scanned for the presence of BiDi characters before accepting the commit."                }            },            "resources": [                {                    "details": {                        "awsEcrContainerImage": {                            "architecture": "amd64",                            "imageHash": "sha256:8ee9d7bbcfc19d383f9044316a5c5fbcbe2df6be3c97f6c7a5422527b29bdede",                            "imageTags": [                                "8.5-200"                            ],                            "platform": "RHEL_8",                            "pushedAt": "2021-12-23T03:05:54+00:00",                            "registry": "123456789012",                            "repositoryName": "test/ubi8/ubi"                        }                    },                    "id": "arn:aws:ecr:ap-northeast-1:123456789012:repository/test/ubi8/ubi/sha256:8ee9d7bbcfc19d383f9044316a5c5fbcbe2df6be3c97f6c7a5422527b29bdede",                    "partition": "N/A",                    "region": "N/A",                    "tags": {},                    "type": "AWS_ECR_CONTAINER_IMAGE"                }            ],            "severity": "HIGH",            "status": "ACTIVE",            "title": "CVE-2021-42574 - libgcc, libstdc++",            "type": "PACKAGE_VULNERABILITY",            "updatedAt": "2021-12-23T03:06:02.647000+00:00"        }    ]}CommentSharehayao-kanswered a year ago0Following what you did, I pushed the original ubi8/ubi:8.5-214: in this case ECR scanning works and no findings were reported (no CVE currently).Then I pushed an image built using super simple following DockerFile:FROM registry.access.redhat.com/ubi8/ubi:8.5-214CMD ["/bin/bash"]And then ECR scanning failed with "Scan status: UNSUPPORTED_IMAGE". Note that I use the AWS Console since using the CLI (aws inspector2 list-findings --filter-criteria '{"ecrImageRepositoryName": [{"comparison": "EQUALS", "value": "<your repo name>"}]}') always reports no findings.CommentShareAWS-User-4447491answered a year ago"


Question: Firewall Appliance in front of API Gateway

"Hi,I have a architectual doubt,Its possible place a firewall virtual appliance in front of a regional API gateway to inspect or control the traffic from the internet agains an particular API?Thanks in advance for any hint about.FollowComment"

Answer: "2Accepted AnswerThe only way to place an appliance in front of API Gateway is to use a Private API. Point your clients into the appliance in the VPC which will then route to the API Gateway VPC endpoint.CommentShareEXPERTUrianswered a year ago1Not answering your question but: why do you want to do this? API Gateway gives you the ability to "pull apart" each request; transform it and then reform a new request to the back end. What do you need the firewall to do that you can't do in API Gateway?CommentShareEXPERTBrettski-AWSanswered a year agoKarlos a year agothat's the point, I needed to confirm that it is indeed unnecessary to deploy a firewall in front of an api gateway.i mean, i needed a differents points of views about that requirement. :) , btw  thanks for detailed explanationShare"


Question: Elastic IP address not attached to a running instance per hour (prorated)

i have already remove the elastic IP from US East (N. Virginia) but i still can see the charges per hour increased everyday.Please help to remove the EIP chargesFollowComment

Answer: "0Accepted AnswerHello,Did you remove it from just the EC2 or from the EIP landing page as well? To fully remove the EIP, you must disassociate it from the EC2 and release it from the "actions" button in the top right corner in the console. If you have done this, ensure no other EIPs are enabled in other regions within you AWS account. I would check out your billing statement to validate. EIPs only incur charges when not in use. If you have validated all of these options, I would reach out to aws billing for support.CommentShareCloud_Ganswered 5 months ago"


Question: AWS Backup Plan - Cold Storage

Does AWS Backup Plan support cold storage for backing up VMware Onprem VMs?FollowComment

Answer: 1Hi - Please refer the blog Backup and restore on-premises VMware virtual machines using AWS Backup. The blog also talks about transition to cold storage and retention period parameters.CommentShareEXPERTAWS-User-Nitinanswered a month ago


Question: rds instance upgraded when Auto minor version upgrade is Disabled

"We have a MySQL instance with version 8.0.23 running for a few months now and this is the max version supported on the third party service we are using. So, I have disabled the 'Auto minor version upgrade' option. Since two days the service is not working as expected and when I checked the version it got minor upgraded to 8.0.28 even though the option is disabled.I found this answer https://repost.aws/questions/QUSriNlSzGRSSWDWYQOnox1g/rds-auto-upgrade-bug-automatic-minor-upgrade-despite-being-disabledAs I cannot go back to the version 8.0.23, are there any other solutions? or do I need to self-host?FollowComment"

Answer: "1Hi,If it is a must to have exactly that version, your main option is probably to host it in ec2, which of course has the disadvantage of increasing operational overhead on your side with patch management for example.On the other hand, Ec2 will give you full control over your database, to use features that may not currently available in RDS and allow you to fine tuning installation as you wish.Hope it helps ;)CommentShareEXPERTalatechanswered 8 days ago"


Question: JSON format error in Manifest file

"Hi'im' trying to setup a training dataset for object localization using the manifest method. Im' getting the following error:401: The S3 input manifest file s3://custom-labels-console-us-east-1-833b01ea2f/datasets/TestTrainingSet/manifests/output/output.manifest does not have the correct JSON format.I couldn't figure out what's wrong with the json, was hoping somebody could help me resolving the issue.Following is the json for one of image files.{"source-ref": "s3://custom-labels-console-us-east-1-833b01ea2f/DentalCEPH/TrainingData/001.png", "bounding-box": {"image_size": [{"width": 1935, "height": 2400, "depth": 3}], "annotations": [{"class_id": 0, "top": 929, "left": 768, "width": 128, "height": 128}, {"class_id": 1, "top": 968, "left": 1405, "width": 128, "height": 128}]}, "bounding-box-metadata": {"objects": [{"confidence": 1}, {"confidence": 1}], "class-map": {"0": "sella turcica", "1": "nasion", "2": "orbitale", "3": "porion", "4": "subspinale", "5": "supramentale", "6": "pogonion", "7": "menton", "8": "gnathion", "9": "gonion", "10": "lower incisal incision", "11": "upper incisal incision", "12": "upper lip", "13": "lower lip", "14": "subnasale", "15": "soft tissue pogonion", "16": "posterior nasal spine", "17": "anterior nasal spine", "18": "articulate"}, "type": "groundtruth/object-detection", "human-annotated": "yes", "creation-date": "2020-11-18T02:53:27", "job-name": "custom labels"}}Thank you,V.Vamsi KrishnaEdited by: vkrishna on Mar 7, 2021 3:53 AMFollowComment"

Answer: "0Just in case some poor soul runs into this same damn issue.When using python for creating the manifest file don't re-direct the output to the manifest file. Open a file from within the script and write the json value.FacePalmCommentSharevkrishnaanswered 2 years ago0Hi Vamsi,seems like you found the solution. If you run into any other issues, please let us know. We are happy to assist you. :)CommentShareAWS-User-1865959answered 2 years ago0vkrishna,I am getting this error too and can't figure out where I am going wrong. I've formatted my manifest file as described at https://docs.aws.amazon.com/rekognition/latest/customlabels-dg/cd-manifest-files-object-detection.html and I used R to create the file (and wrote to a new file as you suggested for python). Could you provide the python code that you used to finally get it working? Or any other tips/suggestions.Thanks,SCommentSharessantoanswered 2 years ago0Hi ssanto,I can help you debug the issue if you would like to share via private message a recent project version name that exhibited the issue you're describing.Thanks,ChristianDAtAWSCommentShareaws-cdunnanswered 2 years ago"


Question: Parameter Validation Error using 'aws ec2 import-image'

"Objective is to pull .vmdk from S3 to EC2, but getting errors around the flag--disk-containersUsing Ubuntu 18.04Linux version 4.15.0-30-generic (buildd@lgw01-amd64-060)pip 9.0.1 from /usr/lib/python3/dist-packages (python 3.6)$ aws ec2 import-image --description TestVM --license-type BYOL --disk-containers UserBucket={"S3Bucket":"vm-test-data","S3Key":"VM-for-input.vmdk"} --dry-runParameter validation failed:Invalid type for parameter DiskContainers[0].UserBucket, value: S3Bucket:vm-test-data, type: <class 'str'>, valid types: <class 'dict'>Invalid type for parameter DiskContainers[1].UserBucket, value: S3Key:VM-for-input.vmdk, type: <class 'str'>, valid types: <class 'dict'>I've also run this using a JSON file per the documentation, but that receives a strange error as well:Error parsing parameter '--disk-containers': Expected: '=', received: 'EOF' for input:container.jsonHas anyone encountered this or can see a way around it?FollowComment"

Answer: "0Hi,I'd like to know if you were able to execute this command correctly, it's happening to me, so I don't really know what's the correct way to run this.I'm using the example provided in https://docs.aws.amazon.com/es_es/vm-import/latest/userguide/vmimport-image-import.htmlaws ec2 import-image --description "SOMETHING X" --license-type auto --disk-containers Description="BUSPDI",Format="vhdx",UserBucket={S3Bucket="migracion-dev803xx",S3Key="PDI.vhdx"} --dry-runCommentShareh3ct0rjsanswered 4 years ago0Same error here, trying to convert an OVA to AMI, does anybody knows the right way to do it ?CommentSharey7857011hanswered 2 years ago"


Question: Instance stuck in 'shutting-down' state

"The EC2 instance "i-0195ea5cf3147180a" is stuck in "shutting down" state and won't ever actually shut down.  Attempting to terminate via GUI doesn't work, and attempting to start, restart, or terminate via the CLI doesn't do anything either. It seems we don't have the tools necessary to resolve this, and I was directed to start a thread here to get help.Any assistance would be great-TomFollowComment"

Answer: "0Hello,Thank you for your post.The instance is stuck in shutting down due to problems with underlying host. Can you please try to perform force stop on the instance?Force the instance to stop using either the console or the AWS CLI.To force the instance to stop using the console, select the stuck instance, and choose Actions, Instance State, Stop, and Yes, Forcefully Stop.To force the instance to stop using the AWS CLI, use the stop-instances command and the --force option as follows:aws ec2 stop-instances --instance-ids i-0123ab456c789d01e --forceMy apologies for any inconvenience this may have resulted in.References:[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/TroubleshootingInstancesStopping.htmlCommentShareAWS-User-4405449answered 4 years ago0Hi Vicky,Thanks for your response, I was unaware of the --force operator for this sub-option.  Unfortunately it didn't work either :( .  I also tried to stop the instance from the Web UI and that didn't work either.$ aws ec2 stop-instances --instance-id i-0195ea5cf3147180a --forceAn error occurred (IncorrectInstanceState) when calling the StopInstances operation: This instance 'i-0195ea5cf3147180a' is not in a state from which it can be stopped.$CommentShareTomL-awsanswered 4 years ago0Hello TomL-aws,Thank you for letting us know about the problem. The issue seems to be related to our underlying AWS infrastructure and so I have created an internal ticket for our service team to deal with it. I will inform you when the issue is resolved.Thank you for your patience and please accept our apologies for the inconvenience caused.Regards,awstomasCommentShareAWS-User-3892169answered 4 years ago0Hello TomL-aws,This is just to confirm that our internal service team has successfully assisted your instance i-0195ea5cf3147180a to shut-down.Once more please accept our apologies for the inconvenience caused. Please let us know if you need any further help.Regards,awstomasCommentShareAWS-User-3892169answered 4 years ago0That instance is shutdown/gone now.Thank you for your help!CommentShareTomL-awsanswered 4 years ago"


Question: Elastic Beanstalk application deployment took long time than expected.

"I'm deploying an ECS Based application via Elastic Bean Stalk, it's been executed for a long time.Environment health has transitioned from Pending to Severe. The command is executing on all instances (15 minutes or more elapsed).This might be an issue with the permissions attached via the service role.How to resolve this issue?FollowComment"


Question: Compute Optimizer export bug?

"Hi, there appears to be a bug in the export of Compute Optimizer to S3 ... when selecting all the available columns, the Migration Effort column(s) are blank.Anyone have a workaround for this? Thanks.FollowComment"


Question: Single IAM Policy for multiple users to access particular S3 bucket.

I want to create a policy for IAM. I have 3 IAM users and 3 S3 buckets. Each user can access only one bucket. Is it possible to create one IAM policy to meet the requirements or I have to create 3 different policies? Thank you.FollowComment

Answer: "1Accepted AnswerYou can use tags on the IAM users and on the buckets and then create a policy that allows access if the values of these tags are equal, using the same policy for each user. Something like this:{    "Version": "2012-10-17",    "Statement": {        "Effect": "Allow",        "Action": s3:*,        "Resource": "*",        "Condition": {"StringEquals":             {"aws:ResourceTag/Owner": "${aws:PrincipalTag/Name}"}}    }}CommentShareEXPERTkentradanswered a month ago1Hi, yes: you can have a single policy and use IAM conditions to allow to a given principalHave a look at https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_condition-keys.htmlAnd search for aws:PrincipalArn in this page to see examplesCommentShareDidier_AWSanswered a month ago"


Question: how to back up my ec2 instance for a biginner

please i have a instance that is generating cost i will back the information of that instance and terminate it and only relaunch it when i need it please can anyone help me with how to back up the information?FollowComment

Answer: "0Does your EC2 instance have only instance store or does it have an EBS volume - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Storage.htmlIf you already have your data in EBS, then your data won't get lost if you reboot your EC2 machine. However, it is still recommended to backup the data in your EBS volumes - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/EBSSnapshots.htmlIf you have only instance store, then the data is ephemeral. Then you should create an EBS volume and attach it to your EC2 machine and copy the data from the instance store to the EBS volume, as mentioned here - https://aws.amazon.com/premiumsupport/knowledge-center/back-up-instance-store-ebs/There is also a service called AWS Backup that allows you to backup your EBS volumes among other things. This tutorial will help you come up to speed on how to do that - https://aws.amazon.com/getting-started/hands-on/amazon-ebs-backup-and-restore-using-aws-backup/CommentShareEXPERTIndranil Banerjee AWSanswered 9 months ago0Just take the snapshot of the block storage and terminate the instance.You can able to restore it in the future with the same configurations.CommentShareKanavanswered 7 months ago"


Question: Getting InvalidSequenceToken

"Hi, I am logging to AWS Cloudwathc using Nlog via a config file. I have set my target as Cloudwatch and gave loggroup name and logStream name in nlog.config file. Also I am logging to same logstream everytime  as I cannot create infinite LogStreams and now facing this error "One or more errors occurred. (The given sequenceToken is invalid. The next expected sequenceToken is: 4963127683279910027287863256864324598022939474020165313". Please help me resolve itFollowComment"

Answer: 0This article explains what the error is and how to troubleshoot. https://aws.amazon.com/premiumsupport/knowledge-center/cloudwatch-invalid-sequence-token/CommentShareMike_Oanswered 10 months ago


Question: Maximum workflow and activity types

"Hello,We have hit the limit "Maximum workflow and activity types"  Although we can still register activities in other domains, switching domains is too complicated in out case because the domain name is used in many places outside SWF :-)We use Java framework and use same version across all WFs and activities. So whenever we change activities, we bump up the version number that leads to hundreds of new activities to be registered.While we are waiting on the limit increase, what would be the recommended practice to minimize the number of activities registered?Thank youFollowComment"

Answer: 0There is no need to register a different workflow or activity type if there is no change in their timeouts and other options.CommentSharemfateevanswered 4 years ago


Question: Get the name of the greengrass core through the API

I would like one of my components to get the name of its hosting greengrass core. Is there an API that I can call to accomplish this?FollowComment

Answer: "0Accepted Answer3 posts down:https://forums.aws.amazon.com/thread.jspa?threadID=336187&tstart=0How to retreive GreengrassV2 Core Device's AWS IoT Thing nameTLDR: Use the AWS_IOT_THING_NAME environment variableEdited by: iamalsohere on Mar 1, 2021 1:08 AMCommentShareiamalsohereanswered 2 years ago"


Question: How to upload dynamically generated file to S3 bucket using lambda with PHP?

"Using bref as PHP serverless framework.Problem:Unable to upload the dynamically generated file to S3 bucket from Lambda using PHP. In CloudWatch, there is no any error.Code:serverless.ymlservice: lambdaToS3provider:    name: aws    region: ap-southeast-2    runtime: provided.al2    #stage: prod    profile: default    iam:        role:            statements:                - Effect: Allow                  Action:                    - 's3:GetObject'                    - 's3:PutObject'                    - 's3:GetObjectAcl'                    - 's3:PutObjectAcl'                  Resource:                    - 'arn:aws:s3:::*/*'plugins:    - ./vendor/bref/breffunctions:    lambdaToS3:        handler: index.php        description: ''        layers:            - ${bref:layer.php-74}        events:            - httpApi: '*'# Exclude files from deploymentpackage:    patterns:        - '!tests/**'        - '!tmp/**'index.phpcomments are output when executing a file using HTTP GateWayIn this file, I am generating a simple text file in /tmp/ folder and trying to upload it to the S3 bucket with two different attributes, SourceFile or Body. None of them working.<?php declare(strict_types=1);ini_set('display_errors', "1");ini_set('display_startup_errors', "1");error_reporting(E_ALL);require __DIR__ . '/vendor/autoload.php';use Aws\S3\S3Client;use Bref\Logger\StderrLogger;    $logger = new StderrLogger();    $s3client = new S3Client([        'scheme' => 'http',        'version' => '2006-03-01',        'region' => 'ap-southeast-2',        'output' => 'JSON'    ]);    $bucket = 'bucketname';        $file = "/tmp/newfile.txt";    $myfile = fopen($file, "w") or die("Unable to open file!");    $txt = "John Doe\n";    fwrite($myfile, $txt);    $txt = "Jane Doe\n";    fwrite($myfile, $txt);    fclose($myfile);    echo "
"; print_r("File Exist: ". file_exists($file)); echo "
"; // 1    echo "
"; print_r(" ================ "); echo "
";     echo "
"; print_r(file_get_contents($file)); echo "
"; // we can get content using this method.    echo "
"; print_r(" ================ "); echo "
";     // Put on S3 using SourceFile    $result = $s3client->putObject([        'Bucket' => $bucket,        'Key' => "AWS_LAMBDA_S3.txt",        'SourceFile' => $file,        'ACL' => 'public-read',    ]);    echo "
"; print_r("File Upload: " . json_encode($result)); echo "
";     // Put on S3 using Body    $myfile = fopen($file, "rb");    $result = $s3client->putObject([        'Bucket' => $bucket,        'Key' => "AWS_LAMBDA_S3_BODY.txt",        'Body' => $myfile,        'ACL' => 'public-read',    ]);    echo "
"; print_r("File Upload: " . json_encode($result)); echo "
";     exit;Regarding policy:Once the function deploy to AWS Lambda, we got a following policy for the role{    "Version": "2012-10-17",    "Statement": [        {            "Sid": "VisualEditor0",            "Effect": "Allow",            "Action": [                "logs:CreateLogStream",                "logs:CreateLogGroup"            ],            "Resource": "arn:aws:logs:ap-southeast-2:xxxx:log-group:/aws/lambda/lambdaToS3-dev*:*"        },        {            "Sid": "VisualEditor1",            "Effect": "Allow",            "Action": [                "s3:PutObject",                "s3:GetObjectAcl",                "s3:PutObjectAcl"            ],            "Resource": "*"        },        {            "Sid": "VisualEditor2",            "Effect": "Allow",            "Action": [                "sqs:DeleteMessage",                "sqs:ReceiveMessage",                "sqs:GetQueueAttributes",                "logs:PutLogEvents"            ],            "Resource": [                "arn:aws:logs:ap-southeast-2:xxxx:log-group:/aws/lambda/lambdaToS3-dev*:*:*",                "arn:aws:sqs:ap-southeast-2:xxxx:xxxx"            ]        }    ]}FollowComment"


Question: The reason of the automatic ECS task reboot

"From 14th November through 17th November, all the AWS ECS tasks, have been restarted automatically.  I think it was stopped by AWS. May I know what's happened?FollowComment"

Answer: 1There are a lot of reasons your tasks may have been restarted. This support article mentions several of them. One reason is maintenance on the underlying host. This documentation talks more about maintenance related restarts and how to identify if a task was restarted for maintenance.CommentShareNoah_Lanswered 6 months ago


Question: OpenSearch not creating geo_point field type in new instances

There's seems to be an issue creating geo_point field types. We have a process that indexes a latitude and longitude coordinate that used to create a geo_point field type and now it creates two separate fields for the lat/lon as float types. This is a real problem since we can no longer perform geo distance searches. We haven't touched the code that performs the indexing so nothing has changed on our end and we can't even create geo_point field types on old version of Elasticsearch. What's going on and how do we create geo_point field types now?FollowComment

Answer: "0Hi, can you please confirm the version of the Opensearch and maybe an example of data and the query?I've tried the below using Opensearch 1.3 and it seems to be working as expected...PUT testindex1{  "mappings": {    "properties": {      "point": {        "type": "geo_point"      }    }  }}PUT testindex1/_doc/1{  "point": {     "lat": 40.71,    "lon": 74.00  }}PUT testindex1/_doc/2{  "point": "txhxegj0uyp3"}GET testindex1/_search{  "query": {    "geo_bounding_box": {       "point": {        "top_left": {          "lat": 42,          "lon": -72        },        "bottom_right": {          "lat": 40,          "lon": -74        }      }    }  }}CommentShareAlex_Tanswered 9 months ago"


Question: Cognito refresh token won't work.

"Hello, We're using Amazon Cognito as the authentication system for our desktop java client. The login process is working fine. I was able to get the credential from the access token, and use the credential for services like S3, dynamoDB etc.Now I noticed that Cognito access token only valid for an hour, and I'm trying to use the refresh token to get new access token, but I can't get it to work. I followed the instruction on https://docs.aws.amazon.com/cognito/latest/developerguide/amazon-cognito-user-pools-using-tokens-with-identity-providers.html  about how to use the refresh token.InitiateAuthRequest initiateAuthRequest = new InitiateAuthRequest().withAuthFlow(AuthFlowType.REFRESH_TOKEN_AUTH).withClientId(CLIENTAPP_ID);initiateAuthRequest.addAuthParametersEntry("REFRESH_TOKEN", refreshToken);Then passed the request to a cognitoIdentityProviderInitiateAuthResult initiateAuthResult = cognitoIdentityProvider.initiateAuth(initiateAuthRequest);But I'm getting a NotAuthorizedException, saying "Invalid Refresh Token.", I'm really confused about this error, because the refresh token is extracted from the same challenge result as the access token, and the access token obviously is working fine. Please help!com.amazonaws.services.cognitoidp.model.NotAuthorizedException: Invalid Refresh Token. (Service: AWSCognitoIdentityProvider; Status Code: 400; Error Code: NotAuthorizedException; Request ID: 94aa060a-78cd-11e9-912f-93b3dfdf29d1)Edited by: yLi on May 17, 2019 11:48 AMFollowComment"

Answer: "0Did you ever figure this out - the question is marked answered, but I don't see an answer - I'm having the exact same problem - and it's very confusing.  I have a test case that grabs the tokens from auth, and then tries refresh, and it immediately fails - it's very frustrating!CommentShareAlex Turneranswered 3 years ago0Check this https://forums.aws.amazon.com/thread.jspa?threadID=322793&tstart=0CommentSharekodlessanswered 3 years ago"


Question: Where to find updated manifest file after labeling a dataset using a premade manifest for a Rekognition Custom Labels project without training a model?

Hi!I have a training set of images for which I manually created a manifest file respecting the format required to train a Rekognition Custom Labels model for object detection. Both the images and that manifest are stored in an S3 bucket. When creating a project to train the model I noticed that the manifest contained some errors which I corrected manually ("Start labeling" then "Draw bounding boxes") but the updated manifest is nowhere to be found.I made sure to save the changes and when I browse through the dataset as it appears during the creation of a project I noticed that my changes were taken into account. I want the manifest so that I can store it locally on my computer but I can't seem to find it. Any help is very much appreciated.Thank you!FollowComment

Answer: "0Unless you specified otherwise, Rekognition Custom Labels will upload everything into the S3 bucket which was created when you first accessed the service. The S3 bucket name will be along the lines of custom-labels-console-<region>-<UID>. Inside this bucket, you should find the following folder structure:projects/    your-project-name/        datasets/            TRAIN/                output.manifest            TEST/                output.manifestTake a look at these manifest files. I think these will contain the updates you made.CommentShareS_Mooseanswered a month agomeLikeServerless a month agoI thank you for your answer. There is indeed such a folder in the bucket. The issue is I don't have the folder datasets/ (and evidently its child folders TRAIN/ and TEST/ and their files). When I access the your-project-name folder I find a labels.json which is empty.I think the structure you're suggesting is only available after training a model.Share"


Question: S3 bucket replication with Object lock. "Contact support"

"I simply want to replicate an S3 bucket with object lock to another region. When I try it says to "Contact Support" and has a link to the support page.How do I properly contact support for THIS specific issue???"If the source bucket has S3 Object Lock enabled, the destination buckets must also have S3 Object Lock enabled.For more information, see Using S3 Object Lock. To enable replication on a bucket that has Object Lock enabled, contact AWS Support."https://docs.aws.amazon.com/AmazonS3/latest/userguide/replication.htmlYou can NOT open a tech support ticket with Basic Support plan. I don't really need more than that. So I select "Limit Increase" as its the only option available with a basic support account. The only options under S3 are:Bucket LimitMultiRegion Access pointsNEITHER are for replication of object locked buckets. I wrote my issue in the description, and of course the ticket was closed without them reading the description! Only saying the limit is already set to more than what I needed.FollowComment"

Answer: "0Hello,I understand you are having difficulty contacting support about replication on a bucket that has object lock enabled with only a basic support plan.Possibly try opening a general question account and billing support ticket:Select "General Info and Getting Started"Using AWS & ServicesGeneral QuestionI hope that helps get you in contact with the correct support team.CommentShareAWS_Gerald_Hanswered 10 months agorePost-User-4162877 8 months agoI have done exactly this, and they keep stating that they are unable to assist me. We have to enable premium support according to them. This make does not make any sense as this is an action that cannot be completed by us. We are being directed to contact Support, and without paying, we cannot enable this function. Please let me know if you have any other options.Share"


Question: ORACLE_FDW in AWS Aurora Postgres

How can we change SQLNET.ENCRYPTION_CLIENT = Accepted to Requested in Oracle_FDW extension? Which parameter has to be changed?FollowComment


Question: SES + SNS delivery status in batch

"Hi,We're using SNS to send HTTP requests to our endpoint. That's how we record delivered, sent, bounced, etc.If we send 500,000 emails this means we will receive 500,000 requests. I wonder whether is it possible to bulk this? It would be great if there is something like this:{"items": [{"messageId": 123"}, {"messageId": 456}]}I haven't been able to find such solution.Thanks,NedimFollowComment"

Answer: 0Bumping this question.CommentShareNedimanswered 2 months ago


Question: ECS: Autoscaling scale down the wrong instance

"HelloWe have a web application which start on demand algorithms. When a user start an algorithm, it starts a task in an ECS Cluster, which has a capacity provider configured to provide an EC2 to run the algorithm.Here I have 2 issues :When ECS detect that it needs to provide an EC2, 2 servers are scaled while only 1 task is startedAs we can see in the screenshot, after 15 min the capacity provider detects that it needs only 1 EC2, so it scale down one EC2, but sometimes, it kills the server on which the algorithm is running.Logs from amazon-ecs-agent on tail -f during the execution of the task :level=info time=2022-11-17T13:20:40Z msg="Managed task at steady state" task="e4874c5693044ed08acbeb311c4919a5" knownStatus="RUNNING"level=info time=2022-11-17T13:20:40Z msg="Managed task at steady state" task="e4874c5693044ed08acbeb311c4919a5" knownStatus="RUNNING"Connection to 35.180.71.XXX closed by remote host.Is there a way to provide only 1 EC2 when we start a task ?Is ECS the right way to do these actions ?Thank you,ValentinFollowComment"

Answer: 0Here are some ideas how you could manage these on-demand jobs better:If you are just running the container to execute one time algorithm then AWS Batch might be better way for you to launch and manage those containers.If you don't want implement AWS Batch and you like your current ECS setup. Then you should consider AWS Fargate with ECS. This would launch your on-demand Tasks as individual compute and you wouldn't need to manage EC2 capacity.ECS also just launched new feature called scale-in protection. So you could tag the ECS Task running your algorythm as protected. This would prevent the capacity provider from scaling that specific EC2 instance down. You would have to implement this protection and removal of protection as part of your web service.CommentShareEXPERTToni_Sanswered 6 months ago


Question: API BEST CLOUD DEVELOPMENT

What kind of API setups are you guys working on?  Id love to share what I have. Still learning….FollowComment


Question: CloudTrail Console showing blank screen

The CloudTrail console is showing a blank screen in multiple regions. I've yet to find a region where it shows anything but a blank screen. All other aws services are displaying as normal. status.aws.amazon.com shows no issues.Test Machine Specs:Brave (1.34.80) desktop browserSafari (15.2) desktop browsersmacOS 12.1FollowComment

Answer: "0Hi, I would suggest to clear out cache, cookies, re-login and try againCommentShareSrianswered a year ago0If you open your browser developer tools and look for the console messages do you see any errors that may help diagnose the issue further?CommentShareRoBanswered a year ago0I've tried clearing my browser data (cache, cookies, data, and all other options selected). I've also tried on Chrome 97.0.4692.99.Here is the console output when loading the CloudTrial page:d6b2kad6rb03m.cloudfront.net/css/aws-cloudtrail-e9df402cb1403848ab72349f3c7d77485953925d.gz.css:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDd6b2kad6rb03m.cloudfront.net/css/aws-cloudtrail-b4e245afe97a1c81998d19f21473e66a134475f1.gz.css:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDd6b2kad6rb03m.cloudfront.net/css/aws-cloudtrail-842c9175672c593231247c04f63bd2aeb533b3ea.gz.css:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDaws-cloudtrail-4dce33a718d6ce79a16f8b1cc6d88d3b09d6e73e.gz.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDaws-cloudtrail-56db7694481b23ce9e42709dcf12ca13cf279662.gz.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDaws-cloudtrail-0fa74b39d7b407552ba2a128a14eea92695ac4f7.gz.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDprod.log.shortbread.analytics.console.aws.a2z.com/1x1.png?severity=info&message=checkForCookieConsent&payload=%7B%22timestamp%22%3A1643145257464%2C%22logVersion%22%3A%221%22%2C%22domain%22%3A%22console.aws.amazon.com%22%2C%22url%22%3A%22https%3A%2F%2Fconsole.aws.amazon.com%2Fcloudtrail%2Fhome%3Fregion%3Dus-east-1%22%2C%22cookie%22%3A%7B%22essential%22%3Atrue%2C%22performance%22%3Atrue%2C%22functional%22%3Atrue%2C%22advertising%22%3Atrue%7D%7D:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTaws-cloudtrail-f2fc9bae8aa11cb32d6dfdfa1d21760857edebe7.gz.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDaws-cloudtrail-7f4fc0f1a9067f5200007bcee9a19d1a5847ae3d.gz.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDaws-cloudtrail-a1993cd981387ef272b83a1eb621df3f54839626.gz.js:1 Failed to load resource: net::ERR_CONNECTION_REFUSEDo197999.ingest.sentry.io/api/6008007/envelope/?sentry_key=3b4bb33e1dfc432c9ccd9f9ce5a4bd25&sentry_version=7:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENTo197999.ingest.sentry.io/api/6008007/envelope/?sentry_key=3b4bb33e1dfc432c9ccd9f9ce5a4bd25&sentry_version=7:1 CommentShareAWS-User-2052131answered a year ago0it appears to be blocked by a pop up blocker or something on the browser, could you please check if a pop up blocker extension is blocking the console?I would also recommend you to try Chrome or Firefox just to rule out a browser issue.CommentShareSrianswered a year ago0Chrome and Safari were freshly installed with no modifications to any settings and no extensions installed...However, today when I tested on Brave (my default browser with lots of extensions and ad blockers) it decided to work. I have not changed any settings except for upgrading my OS from macOS 12.1 to macOS 12.2 and restarting my machine.The console errors have disappeared and everything seems to work as intended...Thanks for everyone's help, regardless!CommentShareAWS-User-2052131answered a year ago"


Question: Application Load Balancer payload limit?

"Hello,I was curious what the maximum payload ammount is for an application load balancer?For example, what is the size limit that an ALB will allow a json request body to be for an HTTP post call.   Is 100MB the limit?i've checked https://docs.aws.amazon.com/elasticloadbalancing/latest/application/load-balancer-limits.html for quotas but I'm not seeing payload listed.FollowComment"

Answer: "-1The max payload that ALB can handle will be a function of sum(request size + response size) x number of requests per minute. Higher the payload size lesser will be your number of requests that ALB can handle. There are more factors involved like HTTP vs HTTPS and also, whether backend connections are persistent or not.  It will be best to open a support case and get ELB/ALB team to give a concrete answer.CommentShareEXPERTgauravanswered 8 months agotbear 4 months agoIs there documentation where more info on this is available?  In general this approach is a bit vague and makes it difficult to troubleshoot errors that may or may not be the result of a request payload that's too large.Share"


Question: AWS RDS Custom SQL Server Incompatible-create

"I have created a RDS Custom SQL Server instance. But after waiting for a long time, the status of instance change to 'Incompaible-create'. And there is one record in the Recent event: 'You can't create the DB instance because of incompatible resources. Workflow step ValidateInstanceProfile reached timeout: 600 seconds'. How can I fix this error status? ThxFollowCommentAWS-User-6943560 a year agoAnd there is an AccessDenied error in CloudTrial, event name is PutTargetsError Message is : User: arn:aws:sts::xxxxxxxxx:assumed-role/AWSServiceRoleForRDSCustom/SLRManagement is not authorized to perform: events:PutTargets on resource: arn:aws:events:us-east-2:xxxxxxxxx:rule/do-not-delete-rds-custom-db-KXBOWMDX2LBPGHYDTJQHC7PJD4-xxxxxx because no identity-based policy allows the events:PutTargets action. Is it the root cause for this issue?Share"

Answer: "0I have encountered similar situations while creating RDS Custom for Oracle. I found starting/restarting the base ec2 instances clearing up this problem usually. I would hence suggest you check the status of the base ec2 instances.CommentShareGovardhanan_Ranswered a year agoAWS-User-6943560 a year agoThanks Govardhanan, but when the RDS Custom status change to Incompaible-create, I can`t find the EC2 instance which is created by RDS Custom anymore...Share0There are few areas to check on this issue:Follow official doc to make sure your VPC and IAM created per requirements. https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/custom-setup-sqlserver.html#custom-setup-sqlserver.reviewSelect correct VPC , Subnet Group and instance profile during the DB CreationCheck security group, if Security Group used by RDS is not same as default security groups (the one associated with VPC endpoints), make sure necessary file ports openCommentShareDonghua Luoanswered a year ago"


Question: Performance Insights for Aurora Postgres doesn't show any data

"Hi,I just enabled Performance Insights for Aurora Postgres and under TOP bar there is no data:What have I missed?ThanksFollowComment"

Answer: "0Accepted AnswerIssue is fixed, I just have to wait a little bit longer once the data is populated.CommentSharemyronix88answered 25 days ago0Because Performance Insights is a sampling method, queries that are completed in a short period of time may not be sampled.In other words, I think the SQL you executed was not displayed because it was done quickly.https://aws.amazon.com/rds/performance-insights/faqs/?nc1=h_lsPerformance Insights counts active sessions and records each session’s attributes about every second using a lightweight sampling mechanism. The sampled data is encrypted and aggregated to a variety of granularities and served through the API and in the DB Load chart in the Amazon RDS Management Console.CommentShareEXPERTRiku_Kobayashianswered a month ago"


Question: Speed Up Loading of Table Visual in Quicksight?

"I have a Quicksight dataset with around 30M rows. I'm trying to visualize a TABLE from this data (filtering it to only show about 100 records) but it is **SUPER **slow to load (around 20 - 30 seconds). I've tried a number of different techniques to see if it is my formula fields, but other visuals using the same formulas (charts, graphs, insights) all load much quickly then the table visual. So, I think it is the visual rather than the calculation that is causing the slow down. Does anyone have a workaround for this? Would be great to have pagination as a future enhancement to handle this.FollowComment"

Answer: "0Accepted AnswerSo... for anyone experiencing a similar issue, keep an eye on your use of Table Expressions. I have a SumOver() calculation that was the culprit.CommentSharedmarcusanswered a year ago"


Question: "URGENT HELP, Name correction for AWS exam"

"Hi,My name needs to be corrected as per the government issued ID. I raised a ticket in https://support.aws.amazon.com/#/contacts/aws-training on 1st of July and there is no update yet. My exam is scheduled on 6th July. Could you please resolve this.My Candidate ID: AWS01566359Thank you.FollowComment"

Answer: 0This was resolved by AWS support.CommentSharesasik198answered 3 years ago


Question: Amazon Quicksight deployment automation

"A customer plans to use both a centrally managed Quicksight account, but also allow freedom for individual account owners to spin up their owner Quicksight instance.  They would like to automate some steps of the QS setup, ie: Enable SAML SSO, Attach VPC.  Without cloudformation support for QS, is there any other way to automate the initial setup & config of a new QS deployment?FollowComment"

Answer: 0Accepted AnswerA few thoughts you can create custom resources within CloudFormation that will hit the QuickSight API's. So 1 or more Lambda functions that will create the application resources that dont have CloudFormation support. Another option is writing a python or shell script that you could eventually incorporate into a CI/CD pipeline using CodeBuild to run. Example script using the QuickSight APIs: https://github.com/aws-samples/amazon-quicksight-sdk-proserve/tree/master/Migration-scripts/Jupyter%20NotebookCommentShareAWS-User-2013569answered 3 years ago