Question: Very specific bug in SES SMTP parsing when sending broken email

"Our mail client implementation had a bug that would generate some header lines without a colon and in doing so we caused a very odd issue that was complicated to track down, made much harder by SES handling the bad input badly. I am going to attempt to document the bug here with the hopes that it can be resolved or improved on the SES end. When sending emails, the From header line was missing a colon. This means that "From: Email" was being generated as "From Email" which is invalid. This appears to cause undefined behavior on several mail clients. But it also appears to cause issues with SES before the email is even sent. from what I can tell, SES ignores the invalid line, where other clients treat it as starting the body of the email. This causes the headers later added by SES to be included in the body rather than applying to the email directly. When viewing the email in Gmail's "show original" it looks correct:Delivered-To: [redacted]@[example.com]Received: by 2002:a05:6512:ba2:0:0:0:0 with SMTP id b34csp1868805lfv;        Tue, 19 Jul 2022 15:02:14 -0700 (PDT)X-Google-Smtp-Source: AGRyM1sAt11EJQpBcpsH0GTK2s5bI26SsS7gxiTNJqEy/PeSZwNNOdGak0lFKLNNe70j78n7gF9OX-Received: by 2002:ab0:4973:0:b0:37f:27c2:59fb with SMTP id a48-20020ab04973000000b0037f27c259fbmr12968094uad.80.1658268134737;        Tue, 19 Jul 2022 15:02:14 -0700 (PDT)ARC-Seal: i=1; a=rsa-sha256; t=1658268134; cv=none;        d=google.com; s=arc-20160816;        b=NwIQxq8OfIVWjAj+yLkno3oEc7oXgqQq1SKvcERe9KQCzFCnanhM1mAw/o4er6gp8p         I/7pWiojQH80z8Jp5J6c2dY+z59SpFMZNyaXHM6XT/SQ4Rsfuu2PWwYN4m3DGpe0yoyI         44wanALu4O8JPN1EYUPyF48s3i0S3WNlbGIqugQFimhUEvY6zmNzKp5EA1O8+8ahA/c2         goSdWWNTp+cihl5tvu2iArZIa4e9eGtPxdPcrAFOE74YSb7iESvRAh94V2wtDyB8x0TN         FSbUChDrx8i0SI850icgHgGjOX91L9prqPCdMGfZAG5sMrXil4qtRO9FJkZklT3QE9Ns         iDhQ==ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;        h=feedback-id:date:from:message-id:subject:to:dkim-signature         :dkim-signature;        bh=7pwq8WTKmJK1Et0R8m2RTs37rtmeOK2Y2tw9V9/1JX8=;        b=NrgBe935AWuUuXB1xpc9nsoQ608x0EQWRGTSyULRsgVQtJC+MhQGcKNzobXD5vUKe/         D6l1YVCJemefrCwdc9Y5ur7mMuBRQgW21+bvGXdgWf2AOOoNoZ4f0W8A66iLHj3cBlSS         XehTECSNPd4sW4SxZUJSAQFyRyAP+k89gv3khdPQuviVgfCoENP4uVWutqlMjJ0eKJqO         oPARJ7+MSV09oc4L2ldQqpMklt36WGk1LUBDSHPCfUG9krHRP+oJMq7bmtVtLJhLWFWn         QWXL5CJjOpuujeU9P6lGbbrkvfidoQ43+fyndU3cccMOQH0EVylLSH682j9P3kcLrCBS         jIRA==ARC-Authentication-Results: i=1; mx.google.com;       dkim=neutral (body hash did not verify) header.i=@[example.com] header.s=[dkimid1] header.b="pd2nv/OH";       dkim=neutral (body hash did not verify) header.i=@amazonses.com header.s=[dkimid2] header.b=QZGwayBq;       spf=pass (google.com: domain of 010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@noreply.[example.com] designates 23.251.226.3 as permitted sender) smtp.mailfrom=010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@noreply.[example.com];       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=[example.com]Return-Path: <010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@noreply.[example.com]>Received: from e226-3.smtp-out.us-east-2.amazonses.com (e226-3.smtp-out.us-east-2.amazonses.com. [23.251.226.3])        by mx.google.com with ESMTPS id k3-20020a676f03000000b0034c1ac9bfd8si2804803vsc.434.2022.07.19.15.02.14        for <[redacted]@[example.com]>        (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128);        Tue, 19 Jul 2022 15:02:14 -0700 (PDT)Received-SPF: pass (google.com: domain of 010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@noreply.[example.com] designates 23.251.226.3 as permitted sender) client-ip=23.251.226.3;Authentication-Results: mx.google.com;       dkim=neutral (body hash did not verify) header.i=@[example.com] header.s=[dkimid1] header.b="pd2nv/OH";       dkim=neutral (body hash did not verify) header.i=@amazonses.com header.s=[dkimid2] header.b=QZGwayBq;       spf=pass (google.com: domain of 010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@noreply.[example.com] designates 23.251.226.3 as permitted sender) smtp.mailfrom=010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@noreply.[example.com];       dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=[example.com]DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=[dkimid1]; d=[example.com]; t=1658268133; h=To:Subject:Message-ID:From:Date; bh=7pwq8WTKmJK1Et0R8m2RTs37rtmeOK2Y2tw9V9/1JX8=; b=pd2nv/OHEuMgmYb8nMdY+GH52kNoLe0NRb4OGzp/oiA9gt0Z3sSpQ7adEQ5Ys7M9 1G469mgzANBG7UrnmytpZhD4wHQJUg3FRNijnP0Vud7Ec+pr7X4E629BtsaOXGWeh/P 0xzeKwfLxwIfF/PIQlixs72E1g7t79n+dC5r86QT+9rHRUplgjc4w+LFWF+UimDvAHu 6sLdiambI737HHCxEwBVrLDrA6ND7tblKU0QVSvyRgcB9bykb2WuGP5lXzEkZxVW3dS QBc5Ipp2Vo3+715BcLhA91e+t/3FBNfIMODnt/yO1w7Wnu+f6YFg1Lbr2iOZrqwxUR/ d9KPPmWYXA==DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/simple; s=[dkimid2]; d=amazonses.com; t=1658268133; h=To:Subject:Message-ID:From:Date:Feedback-ID; bh=7pwq8WTKmJK1Et0R8m2RTs37rtmeOK2Y2tw9V9/1JX8=; b=QZGwayBqH56MN00vngBNtPdpksHd8cPyB4f7QQ9Ox+Vm+Lgo4NNH6d0V8DD0F55Y qmuWPpTD9uKLgqPsEMRrKnIevaVuxoF8k/mIGR2BtY4jqjJQgvZzjLr4xKG+85cXmRh en87LS3WoXEnJ/2H/jSMzaHpkJWLXSStoQCXupVo=To: [redacted]@[example.com]Subject: Testing Email from bx-dev.[example.com]Message-ID: <010f0182187ba838-40718a6b-7d54-458b-bae9-184134f16d2e-000000@us-east-2.amazonses.com>From: noreply@[example.com]Date: Tue, 19 Jul 2022 22:02:13 +0000Feedback-ID: 1.us-east-2.mM11q1NsBOaKhKuE1cIVPG6HuOlVAX0aAAVYk49yrLE=:AmazonSESX-SES-Outgoing: 2022.07.19-23.251.226.3Test message for notification TESTING from bx-dev.[example.com]!Note that "body hash did not verify", this is because the real email that was delivered had extra content in the body that doesn't show up in the gmail view. If pasted into a dkim validator the email will pass even though gmail failed, this is because gmail's view is actually modified. When sending through a server that doesn't mutate we can see that dkim passes:Authentication-Results: [example.com];        iprev=pass (e226-4.smtp-out.us-east-2.amazonses.com) smtp.remote-ip=23.251.226.4;        spf=pass smtp.mailfrom=noreply.[example.com];        dkim=pass header.d=[example.com] header.s=[dkim1] header.a=rsa-sha256;        dkim=pass header.d=amazonses.com header.s=[dkim2] header.a=rsa-sha256;        dmarc=skipped;        arc=noneExcept in this case we see the real body starts with what appear to be headers. (note the missing colon in the From line)From noreply@[example.com]To: [redacted]@[example.com]Subject: Testing Email from bx-dev.[example.com]Message-ID: <010f01821ce7b3e9-2879bf86-f3f1-47c5-a62c-747833d398ce-000000@us-east-2.amazonses.com>From: noreply@[example.com]Date: Wed, 20 Jul 2022 18:38:43 +0000Feedback-ID: 1.us-east-2.mM11q1NsBOaKhKuE1cIVPG6HuOlVAX0aAAVYk49yrLE=:AmazonSESX-SES-Outgoing: 2022.07.20-23.251.226.4Test message for notification TESTING from bx-dev.[example.com]!Obviously the From line being broken is a client side bug, but note some of the bad behavior from SES here. It noted the lack of From: in the initial email and used the SES config to add a default sender, however it do so by appending to the end of the block which actually added to the body of the email. It also Added Date: and Feedback-ID: erroneously after the From line that started the body processing. It then signed the email using the whole body contents, starting from the bad From line and including the Amazon added content but also signing using the headers that were now part of the body. So clearly SES is inconsistent in the way it handles this error case. This lead to endless confusion as gmail was masking the real email contents, SES was adding headers effectively in the body of the email, and several email providers where just straight rejecting mail without any reason or explanation.Ideally SES would reject email attempts that do not conform to standards (using the empty blank line to start the body of the email) but barring that ideally SES wouldn't add headers after the point where it considers the body to have started, and wouldn't dkim sign including those headers later.FollowComment"


Question: rds connection from telnet or pgAdmin - what host?

I created DB instance and obtained such endpoint:tripbook-db.cvvxhyaiehrw.us-east-2.rds.amazonaws.comwith port 5430I tried to log in via pgAdmin or telnet but no success.telnet supposed to work like this : telnet <endpoint> <port> but its' not working:telnet tripbook-db.cvvxhyaiehrw.us-east-2.rds.amazonaws.com 5430DB is available and public open.FollowComment

Answer: "0I found a solution in sapenov's anwer, here:https://stackoverflow.com/questions/16837806/cant-connect-to-rds-instance-from-ec2-instanceCommentSharehipodromanswered 6 years ago"


Question: CloudFormation cannot update tags on Elastic Beanstalk Environments

"Hi,I just noticed that it is not possible to update the tags set on an AWS::ElasticBeastalk::Environment resource through CloudFormation. I thought it strange, since it is possible to do it through the elastic beanstalk console (select environment -> click tags -> click update), triggering an environment update. This works perfectly for other changes such as configuration, source bundle, ...Do you plan on making this available?Thanks!Edited by: nunest on Mar 6, 2019 6:39 AMFollowComment"

Answer: 0This seems to have been fixed in the 2019-04-04 release of Elastic Beanstalk: https://docs.aws.amazon.com/elasticbeanstalk/latest/relnotes/release-2019-04-04-tagging-clients.html.CommentSharenunestanswered 4 years ago


Question: Bug: Creating and accepting a contact with empty reference will freeze the CCP

"I noticed that one can create a task contact (I'm using boto3) with a reference with an empty string as the value. This is fine in my opinion.However, as soon as an agent accepts this contact, this will freeze the CCP and the agent will only see a white screen.The only way I found to fix this is to call stop-contact twice (once to end the task and once to get it out of ACW).Is this a known bug?Is there another way to fix such broken contacts using the connect web GUI?FollowComment"


Question: "@" A-Record not validating with website host

"When creating an A-Record with "@" our website hosting server is unable to validate this. The www A-record validated almost immediately.When looking at DNS checks for the domain, we receive an error (but without any error direction), but if we look up specifically "@.example.com" it comes back successful. I am wondering if the period after the @ is causing a problem. AWS adds that period automatically and I cannot remove it. The website host says it must be on AWS side.Any ideas would be helpful. Thank you in advance.FollowComment"

Answer: "0Accepted AnswerTo get the "@" record correct in AWS, simply leave the field where you would want to write "@" blank.CommentSharerePost-User-3836628answered 7 months ago"


Question: Postgres RDS Schema Upgrade (migration) with no downtime

"Hello,What is the recommended way to create a snapshot (for backup) of an RDS Postgres instance to apply schema changes? We want to maintain both replicas in sync, minimize downtime and keep the new replica up to date. We want to create and keep a snapshot in case we need to rollback these schema changes.I have made research and found https://aws.amazon.com/getting-started/hands-on/move-to-managed/migrate-postgresql-to-amazon-rds/ not sure if this feature can be used for this purpose. Will live schema changes break the migration?Our schema changes are simple, we are adding nullable new columns to existing tables and we are also creating new tables.Thank you in advance.FollowComment"

Answer: "1Hello,Is the requirement only to being able to restore the database to a previous point in time? If yes, then this can be done without any replication, just with regular database backups.When people speak about replicas, this means there is a secondary instance that is receiving all the changes in (near) real time, but it doesn't seam to me you're asking for that?RegardsCommentShareAWS-ADolganovanswered a year agoKevin_Z SUPPORT ENGINEERa year agoYeah I would ask the same as ADolganov mentioned that are we talking about read replica or backups/snapshots?For replicas: We can use native RDS Read Replica or We can use DMS to create replication between two PostreSQL instances. (RDS PostgreSQL to RDS PostgreSQL or RDS PG to on-prem PG or RDS PG to Aurora).By the way, DMS does support DDL change add columns and create tables: https://docs.aws.amazon.com/dms/latest/userguide/CHAP_Introduction.SupportedDDL.html but test is suggested before applying this to Production.Share0for managed database offering you can set backup 0-35 days and for issues or rollback you can do a point in time for that period to a new instance. thus any schema changes could be rolled back as long as the change was done in last n days (n=backup days set on instance )CommentShareAWS-User-8174525-subhashanswered a year ago"


Question: i was not able to use my account

I was getting error as not a valid recognized account while launching instance.it was occuring from pas one hour. can u please look into this issue as soon as possible?FollowComment

Answer: "0Hi ThereCheck this previous post for some tips: https://repost.aws/questions/QUwnXvvsQyRzut3QE3ct3qOg/account-is-currently-blocked-when-trying-to-create-ec-2-instanceit is possible that your account is limited to use certain region only as free tiers ( mainly US East (N. Virginia), US East (Ohio), US West (Oregon)) You can validate by trying to create the EC2 in those regions. if you need more regions, you will have to contact aws-verification@amazon.com and explain why you need other regions.CommentShareEXPERTMatt-Banswered 2 months ago"


Question: Help with Textract using Java 1.x SDK

"I'm looking to extract form data utilizing textract. I've tested with a PDF in the demo and results are great. Results using the SDK however are far from optimal, actually, completely inaccurate. If I use StartDocumentAnalysisRequest/StartDocumentAnalysisResult (asynchronous), I only get 1 block returned of type PAGE, never KEY_VALUE_SET. If I convert my PDF to an image and use the synchronous route, I do get KEY_VALUE_SET back but results are completely inaccurate.Does anyone know how I can utilize the asynchronous analysis functionality to retrieve form values as the documentation indicates?Sample Code below:`StartDocumentAnalysisRequest req = new StartDocumentAnalysisRequest().withFeatureTypes(FeatureType.FORMS).withDocumentLocation(new DocumentLocation().withS3Object(new com.amazonaws.services.textract.model.S3Object().withName(objectName).withBucket(awsHelper.getS3BucketName())));        StartDocumentAnalysisResult startDocumentAnalysisResult = amazonTextract.startDocumentAnalysis(req);        String startJobId = startDocumentAnalysisResult.getJobId();        GetDocumentAnalysisResult documentAnalysisResult = null;        String jobStatus = "IN_PROGRESS";        while (jobStatus.equals("IN_PROGRESS")) {            try {                TimeUnit.SECONDS.sleep(10);                GetDocumentAnalysisRequest documentAnalysisRequest = new GetDocumentAnalysisRequest()                        .withJobId(startJobId)                        .withMaxResults(1);                documentAnalysisResult = amazonTextract.getDocumentAnalysis(documentAnalysisRequest);                jobStatus = documentAnalysisResult.getJobStatus();            } catch (Exception e) {                logger.error(e);            }        }        if (!jobStatus.equals("IN_PROGRESS")) {                List<Block> blocks = documentAnalysisResult.getBlocks();                logger.error("block list size " + blocks.size());                Map<String, Map<String, Block>> keyValueBlockMap = new HashMap<>();                Map<String, Block> keyMap = new HashMap<>();                Map<String, Block> valueMap = new HashMap<>();                Map<String, Block> blockMap = new HashMap<>();                for (Block block : blocks) {                    logger.error("Block Type:" + block.getBlockType());                    String blockId = block.getId();                    blockMap.put(blockId, block);                    if (block.getBlockType().equals("KEY_VALUE_SET")) {                        if (block.getEntityTypes().contains("KEY")) {                            keyMap.put(blockId, block);                        } else {                            valueMap.put(blockId, block);                        }                    }                }                keyValueBlockMap.put("keyMap", keyMap);                keyValueBlockMap.put("valueMap", valueMap);                keyValueBlockMap.put("blockMap", blockMap);                Map<String, String> keyValueRelationShip = getKeyValueRelationShip(keyValueBlockMap);                for (String key : keyValueRelationShip.keySet()) {                    logger.error("Key: " + key);                    logger.error("Value: " + keyValueRelationShip.get(key));                }            }`Synchronous path which results and completely horrible resultsAnalyzeDocumentRequest request = new AnalyzeDocumentRequest()                     .withFeatureTypes(FeatureType.FORMS)                     .withDocument(new Document().                             withS3Object(new com.amazonaws.services.textract.model.S3Object()                                     .withName(objectName)                                     .withBucket(awsHelper.getS3BucketName())));  AnalyzeDocumentResult result = amazonTextract.analyzeDocument(request);FollowCommentAWS-User-1695148 a year agoFWIW, I upgraded to v2 and the results still suckShareAWS-User-1695148 a year agoi also submitted this: https://github.com/aws/aws-sdk-java-v2/issues/3095Share"

Answer: "0Hi, it'd be great if you could you provide us with a sample file for which you are facing the issues and your AWS account id and the region you are operating in.You could contact AWS support to share the details. This will help us in identifying the issue.CommentSharekasnitisAWSanswered a year agoAWS-User-1695148 a year agoThanks I've opened a support case and will update here if it ends up being something on my side.Share0Hi, Thank you for using Amazon Textract, and I am sorry to hear that you are facing some issues with our APIs. We are investigating this issue, and I'll update the thread once I have more details.CommentShareAWS-User-8501837answered a year ago"


Question: How to correctly integrate AWS WorkMail with AWS Identity Center?

"Dear community,I use AWS Organisations and AWS Identity Center (Successor to SSO). Therefore, I already have an SSO start page with a subdomain (name of my company). I want to be able to integrate AWS WorkMail into AWS Identity Center. However, as seen on the screenshot, I can't find my existing AWS Identity Center directory from the dropdown menu. I also can't reuse the sub-domain I use for AWS Identity Centre (https://my-company.awsapps.com/start) to link them together (https://my-company.awsapps.com/mail). I also can't find AWS WorkMail in the list of integrations in AWS Identity Centre (see the second screenshot).What am I doing wrong? Did I miss any configuration settings anywhere? Is AWS's very own WorkMail not yet supported by AWS's very own Identity Center? It seems rather unlikely.FollowComment"

Answer: "2Accepted AnswerHello ,Thank you for posting your question on the AWS Repost, my name is Rochak and it will be a pleasure assisting you with this today.I understand you would like to know if Amazon WorkMail integrates with AWS Identity Center. Please, let me know if my understanding is incorrect.Currently, AWS Identity Center is not one of the services that Amazon WorkMail integrates with. Please see here the list of services that Amazon WorkMail integrates with. [1]For any new features or capabilities updates for AWS, please keep an eye on Feature Announcement here [2]I hope this helps. If you need further info, let me know in the comments; otherwise I'd appreciate if you mark my answer as "accepted".Kind regards,Rochak from AWSReferences:[1] Amazon WorkMail FAQs (Integration with AWS Services)https://aws.amazon.com/workmail/faqs/[2] What’s New at AWShttps://aws.amazon.com/new/CommentShareAWS-Rochakanswered 3 months ago"


Question: hot to make ALB forward traffic to API Gateway

"I want to expose my service to public through ALB, is there any way to call API Gateway through ALB?It seems ALB just support instance, ip and lambda as target?Thanks,MingtongFollowComment"

Answer: "0Can you explain your use-case? API Gateway itself can expose your service to the public. API Gateway supports Regional or Edge Optimized endpoints that are external facing. So why do you want to add ALB in front of API Gateway again. What are you planning to achieve with that architecture?CommentShareEXPERTIndranil Banerjee AWSanswered 6 months agomingtong 6 months agoWe plan to use ALB to expose our portal, API gateway works for backend. API gateway cannot be access from public for china regions aws account default configuration(some china regions policy), so we want to use ALB to handle all request from public, and then forward to API Gateway.Share0Can you try using the private IP from Network Interfaces attached to the API Gateway as the ALB Target. But the Private IP can change so you need to have some custom solution(may be lambda) to monitor the IP change.CommentShareGautam Kumaranswered 6 months ago0you need to use HTTP integrationhttps://docs.aws.amazon.com/apigateway/latest/developerguide/getting-started-http-integrations.htmlsee the following guidehttps://aws.amazon.com/premiumsupport/knowledge-center/api-gateway-application-load-balancers/CommentSharekaveerhanswered 6 months ago"


Question: What's Aurora MySQL WHILE - DO statement correct syntax?

I am trying to create a WHILE loop in Aurora MySQL. With this syntax:SET @inc = 0;WHILE @inc <= 5 DOSET @inc = @inc + 1;END;I getting syntax error near 'WHILE @inc <= 5 DOWhat's the correct syntax in Aurora MySQL?My AURORA_VERSION() is 2.10.0ThanksFollowComment

Answer: "1Accepted AnswerYou need to add a delimiter as explained here The following works for me when I test it on Aurora MySQL 2.10.0:delimiter //CREATE PROCEDURE dowhile()  BEGIN   DECLARE v1 INT DEFAULT 5;    WHILE v1 > 0 DO     SET v1 = v1 - 1;   END WHILE; END; //delimiter ;CommentShareShivanswered a year agoEXPERTJohn_Freviewed a year agormortega a year agoThanks. This solved it. Just want to point out that DELIMITER is needed with some clients. Is not a feature of Aurora or MySQL. For instance when I call the query using PyMySQL, I need to remove them.Share1According to this answer on Stack Overflow, you can only use WHILE if you're inside a stored program or function body.EDIT: Shiv has correctly identified the problem in relation to a missing delimiter reassignment. A good explanation of why the delimiter is sometimes necessary is given in the MySQL docs:If you use the mysql client program to define a stored program containing semicolon characters, a problem arises. By default, mysql itself recognizes the semicolon as a statement delimiter, so you must redefine the delimiter temporarily to cause mysql to pass the entire stored program definition to the server.The example uses // as a temporary delimiter, but any character or multiple characters (except backslash) can be used, for example $$ is commonly seen. The idea is to nest the stored program inside a pair of delimiter statements:delimiter $$          -- <- set delimiter temorarily to $$/* stored program definition goes here, including semicolons */delimeter;            -- <- restore delimiter to default (semicolon)CommentShareroianswered a year ago0WHILE statement is part of Flow Control StatementsMySQL supports the IF, CASE, ITERATE, LEAVE LOOP, WHILE, and REPEAT constructs for flow control within stored programs.CommentSharepprakashanswered a year agormortega a year agoYes. From there I took this sample:CREATE PROCEDURE dowhile()BEGINDECLARE v1 INT DEFAULT 5;WHILE v1 > 0 DOSET v1 = v1 - 1;END WHILE;END;I and get this error:You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '' at line 3None of the samples I found works.Thanks.Share"


Question: blue green deployment to ECS via another CI server

"Hello teamI've been reading documentation on how to setup Blue-Green deployments on ECS and I would like to know if it's tied to AWS CodeDeploy.The problem is my company uses another CI server but in the end containers are deployed in ECS. Is there a work around. Can I just docker push from the CI server and trigger the BG deployment? So if the docker image is built before hand in another CI server how can I leverage the codedeploy ability to do the blue-green deploymentIf not, can I just create a Deployment on CodeDeploy and just run one command, in this case docker push?thanksEdited by: elmagg on Feb 11, 2021 3:45 PMEdited by: elmagg on Feb 11, 2021 3:55 PMFollowComment"

Answer: "0No, you are not required to use AWS CodeDeploy for Blue/Green deployments however CodeDeploy does make it easier. The following is an example of using Jenkins to manage your deployments:https://aws.amazon.com/blogs/containers/blue-green-deployments-with-the-ecs-external-deployment-controller/Also, as another option, many of the popular CI servers have plugins to call CodeDeploy. In this scenario you can continue to use your existing CI server in conjunction with CodeDeploy and get the best of both worlds.Thanks,ChrisCommentShareChris_Ranswered 2 years ago"


Question: [Bug] - RunOrder is not respected

"Hi AWS,I believe I have found a bug in regards to therunOrderparameter for CodePipeline actions not being respected if they are defined out of order in the template.Example of it not respecting runOrder definitions;        - Name: StageName          Actions:            - Name: "Task2"              InputArtifacts:                - Name: GitBundle              ActionTypeId:                Category: Build                Owner: AWS                Version: 1                Provider: CodeBuild              Configuration:                ProjectName: !Ref Task2Project              RunOrder: 2            - Name: "Task1"              InputArtifacts:                - Name: GitBundle              ActionTypeId:                Category: Build                Owner: AWS                Version: 1                Provider: CodeBuild              Configuration:                ProjectName: !Ref Task1Project              RunOrder: 1In the above actions example, both actions will execute in parallel as it appears while therunOrderparameter is respected visually in the CodePipeline Console, if the higher runOrder action is defined BEFORE the lower runOrder action CodePipeline will still execute both in parallel.To rectify this, if your initial template is out of order, you simply need to migrate your action code block to be below any HIGHER runOrder items.i.e. Your runOrder: 1 Action block must be defined in the CFN before your runOrder: 2 Action block.CodePipeline will then respect the runOrder and wait for the lower runOrder item to complete before progressing.This to me appears to be a bug, regardless of what order the action has been defined, the runOrder parameter value should be respected and executed as intended.Cheers,JeremyEdited by: jbeffektd on Jan 30, 2019 5:09 PMEdited by: jbeffektd on Jan 30, 2019 5:11 PMFollowComment"

Answer: "0Hello, so far I've been unable to reproduce this behavior. The RunOrder was respected regardless of ordering within the template in the pipelines I created using stage definitions similar to yours. Will you provide us with the full resource definition with all sensitive information removed?Thanks,LukeCommentShareAWS-User-3538675answered 4 years ago0Hi Luke,Thanks for replying.That is strange, I definitely observed this at the time of the post. I've moved onto other project work however I will see if I can reproduce it again when I get an opportunity.A few other things to mention;The runOrder was amended and pushed via CFN to an existing stack, not a new stackThe stack was run in ap-southeast-2CodePipeline was currently setup in the below wayGitHub PullCB 1CB 1CB 2CB 2Whether any of the above makes a difference, I'm not sure, I'll try replicate with a fresh deployment and then test with a CFN update and see if it replicates.Cheers,JeremyEdited by: jbeffektd on Feb 20, 2019 3:10 PMHere is an extract specific to CP and CB  AmiPipeline:     Type: AWS::CodePipeline::Pipeline    Properties:       RoleArn: !GetAtt CodePipelineRole.Arn      Stages:         -           Name: Source          Actions:             -               Name: "Retrieve"              ActionTypeId:                Category: Source                Owner: ThirdParty                Version: 1                Provider: GitHub              Configuration:                Owner: !Ref GitHubOrg                Repo: !Ref GitHubRepo                Branch: !Ref GitHubBranch                OAuthToken: !Ref GitHubToken              OutputArtifacts:                - Name: GitBundle        - Name: BuildAMI          Actions:            - Name: "XXXXXXXXXXXXXX"              InputArtifacts:                - Name: GitBundle              ActionTypeId:                Category: Build                Owner: AWS                Version: 1                Provider: CodeBuild              Configuration:                ProjectName: !Ref AmiProject1              RunOrder: 1            - Name: "XXXXXXXXXXXXX"              InputArtifacts:                - Name: GitBundle              ActionTypeId:                Category: Build                Owner: AWS                Version: 1                Provider: CodeBuild              Configuration:                ProjectName: !Ref AmiProject2              RunOrder: 1            - Name: "XXXXXXXXXXXXX"              InputArtifacts:                - Name: GitBundle              ActionTypeId:                Category: Build                Owner: AWS                Version: 1                Provider: CodeBuild              Configuration:                ProjectName: !Ref AmiProject3              RunOrder: 2            - Name: "XXXXXXXXXXXXX"              InputArtifacts:                - Name: GitBundle              ActionTypeId:                Category: Build                Owner: AWS                Version: 1                Provider: CodeBuild              Configuration:                ProjectName: !Ref AmiProject4              RunOrder: 2      ArtifactStore:        Type: S3        Location: !Ref ArtifactBucket        EncryptionKey:          Id: !Ref CodePipelineKey          Type: KMS  AmiProject1:    Type: AWS::CodeBuild::Project    Properties:      Artifacts:        Type: "CODEPIPELINE"      Source:        Type: "CODEPIPELINE"        BuildSpec: buildspec/buildspec.yml      Environment:        ComputeType: "BUILD_GENERAL1_MEDIUM"        Image: !Ref DockerImageId        Type: "LINUX_CONTAINER"        EnvironmentVariables:          - Name: GITHUB_BRANCH            Value: !Ref GitHubBranch          - Name: NETWORK_STACK            Value: !Ref NetworkStack          - Name: REPORTS_BUCKET            Value: !Ref ArtifactBucket          - Name: AWS_REGION            Value: !Ref "AWS::Region"      ServiceRole: !GetAtt CodeBuildServiceRole.Arn      EncryptionKey: !Ref CodePipelineKey      TimeoutInMinutes: 120      VpcConfig:        VpcId:           Fn::ImportValue: !Sub "${NetworkStack}-VPCID"        Subnets:          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateA"          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateB"        SecurityGroupIds:          - !Ref PipelineSecurityGroup  AmiProject2:    Type: AWS::CodeBuild::Project    Properties:      Artifacts:        Type: "CODEPIPELINE"      Source:        Type: "CODEPIPELINE"        BuildSpec: buildspec/buildspec.yml      Environment:        ComputeType: "BUILD_GENERAL1_MEDIUM"        Image: !Ref DockerImageId        Type: "LINUX_CONTAINER"        EnvironmentVariables:          - Name: GITHUB_BRANCH            Value: !Ref GitHubBranch          - Name: NETWORK_STACK            Value: !Ref NetworkStack          - Name: REPORTS_BUCKET            Value: !Ref ArtifactBucket          - Name: AWS_REGION            Value: !Ref "AWS::Region"      ServiceRole: !GetAtt CodeBuildServiceRole.Arn      EncryptionKey: !Ref CodePipelineKey      TimeoutInMinutes: 120      VpcConfig:        VpcId:           Fn::ImportValue: !Sub "${NetworkStack}-VPCID"        Subnets:          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateA"          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateB"        SecurityGroupIds:          - !Ref PipelineSecurityGroup  AmiProject3:    Type: AWS::CodeBuild::Project    Properties:      Artifacts:        Type: "CODEPIPELINE"      Source:        Type: "CODEPIPELINE"        BuildSpec: buildspec/buildspec.yml      Environment:        ComputeType: "BUILD_GENERAL1_MEDIUM"        Image: !Ref DockerImageId        Type: "LINUX_CONTAINER"        EnvironmentVariables:          - Name: GITHUB_BRANCH            Value: !Ref GitHubBranch          - Name: NETWORK_STACK            Value: !Ref NetworkStack          - Name: REPORTS_BUCKET            Value: !Ref ArtifactBucket          - Name: AWS_REGION            Value: !Ref "AWS::Region"      ServiceRole: !GetAtt CodeBuildServiceRole.Arn      EncryptionKey: !Ref CodePipelineKey      TimeoutInMinutes: 120      VpcConfig:        VpcId:           Fn::ImportValue: !Sub "${NetworkStack}-VPCID"        Subnets:          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateA"          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateB"        SecurityGroupIds:          - !Ref PipelineSecurityGroup  AmiProject4:    Type: AWS::CodeBuild::Project    Properties:      Artifacts:        Type: "CODEPIPELINE"      Source:        Type: "CODEPIPELINE"        BuildSpec: buildspec/buildspec.yml      Environment:        ComputeType: "BUILD_GENERAL1_MEDIUM"        Image: !Ref DockerImageId        Type: "LINUX_CONTAINER"        EnvironmentVariables:          - Name: GITHUB_BRANCH            Value: !Ref GitHubBranch          - Name: NETWORK_STACK            Value: !Ref NetworkStack          - Name: REPORTS_BUCKET            Value: !Ref ArtifactBucket          - Name: AWS_REGION            Value: !Ref "AWS::Region"      ServiceRole: !GetAtt CodeBuildServiceRole.Arn      EncryptionKey: !Ref CodePipelineKey      TimeoutInMinutes: 120      VpcConfig:        VpcId:           Fn::ImportValue: !Sub "${NetworkStack}-VPCID"        Subnets:          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateA"          - Fn::ImportValue: !Sub "${NetworkStack}-SubnetPrivateB"        SecurityGroupIds:          - !Ref PipelineSecurityGroupEdited by: jbeffektd on Feb 20, 2019 3:17 PMCommentSharejbeffektdanswered 4 years ago0Have you tried inspecting pipeline history (specifically action executions) to get timing information?jbeffektd wrote:The runOrder was amended and pushed via CFN to an existing stack, not a new stackWhat did the pipeline look like before and after the update? If you're changing the run order of some actions, you might be observing CodePipeline "drain" a pipeline execution (started with the old pipeline definition and using the before run order to complete the stage).CommentShareAaron_Canswered 4 years ago"


Question: Do I need to be in the Managerment account to use System Manager / Patch Manager to patch instances across an Organization

I see the blog posts about being able to patch across an AWS Organization; I'm just wondering if you need to do that from the Management account or can you do it from a different account? So far it seems like you need to do it from the Management account and it looks like you need to enable a few other services ( like Config ) which I can do; but I already have a delagated account for Config so I would need to move that back to the Management account if I have to patch from there.FollowComment

Answer: "0Hi, thanks for your question.At the time, AWS Systems Manager Patch Policy across Organization [1] should be deployed from the Management Account. There is no need of setup AWS Config service to create a Patch Policy for your organization. Here is blog post you can follow to complete this setup [2].  In order to monitor your patch compliance , you can use AWS Systems Manager Explorer, which can set up a Delegated Administrator account within your Organization [3].[1]https://aws.amazon.com/about-aws/whats-new/2023/01/aws-systems-manager-patch-policies-cross-account-region-patching/[2]https://aws.amazon.com/blogs/mt/centrally-deploy-patching-operations-across-your-aws-organization-using-systems-manager-quick-setup/[3]https://docs.aws.amazon.com/systems-manager/latest/userguide/Explorer-setup-delegated-administrator.htmlRegards,CommentSharerodrggianswered 3 months ago"


Question: HOW TO CONNECT TERRAFORM WITH AWS WITHOUT ACCESSKEY AND SECRETE KEY

"HI Team,i want to know is there any another way or process to connect the terraform with aws account without access key and secrete key and if any describe the process.FollowComment"

Answer: "0To answer your question, we need to understand the operating environment of where you are operating Terraform from, as you did not specify. Depending on where you are operating Terraform from, you have different options.Are you operating Terraform from:Your computer/laptop?A Virtual Machine in your own datacenter/another cloud Provider?Terraform Cloud?EC2 in your AWS account?Container in your AWS account?The AWS provider for Terraform (a Terraform plugin) leverages the AWS GO SDK to interact with AWS APIs. The AWS Go SDK uses the AWS Credential Provider Chain. All SDKs have a series of places (or sources) that they check in order to find valid credentials to use to make a request to an AWS service. After valid credentials are found, the search is stopped. This systematic search is called the default credential provider chain.These locations include the code you are running, the environment variables of the operating environment, shared configuration and credentials files, Amazon Elastic Contianer Service (ECS) credentials, Amazon EC2 instance profile credentials. For more information, see Precedence of settings.I'm going to assume your end goal is simply to not have long lived credentials? Please confirm?I'll provide some of the most common operating environments here:Your computer/laptopWhen operating from your laptop/computer in an interactive mode from the Terminal, if you are using AWS IAM Identity Center authentication with SSO, you can use open source project Leapp to set your AWS configuration files to assume the role of your choice.If operating from within VSCode, you can leverage the AWS Toolkit for Visual Studio Code to create a Credentials Profile. This profile will be honored in the VSCode Terminal.A Virtual Machine in your own datacenter/another cloud ProviderYou can use IAM Roles Anywhere and the AWS open source RolesAnywhere Credential Helper vends temporary credentials by sending a CreateSession request to the Roles Anywhere service. You can use the update command to update the temporate credentials in the credential fie including the profile to use.Terraform Cloud?Terraform Cloud can use dynamic provider credentials for official cloud providers, including AWS.EC2 in your AWS accountIAM roles for Amazon EC2 allows processes running on that EC2 to retrieve credentials from instance metadata.ECS task/container in your AWS accountTask IAM role for ECS allows processes running in that container to retrieve credentials from container metadata, similar to EC2 instance metadata but task specific.Leapphttps://www.leapp.cloud/CommentShareawstyleranswered a month ago-1hi - it's not possible to connect Terraform to an AWS account without Access and Secret Keys. They will be required to authenticate you to interact with your account. Another way is to create an instance or credential profile with Terraform, but you'll still need the keys - https://aws.amazon.com/blogs/apn/terraform-beyond-the-basics-with-aws/CommentShareArunanswered a month agoEXPERTalatechreviewed a month agorePost-User-5178759 a month agocan you explain in detail for iam role based connectivity between terraform and awsShareawstyler a month agoThis is not fully accurate. Terraform uses the AWS Credential Provider Chain, details in below post.https://docs.aws.amazon.com/sdkref/latest/guide/standardized-credentials.htmlShare-1If Terraform is to be run outside of AWS, you will need to use an access key and a secret access key.If you do not want to use the access key and secret access key, you will need to do something like run Terraform from CloudShell or Cloud9.https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.htmlhttps://docs.aws.amazon.com/cloud9/latest/user-guide/welcome.htmlCommentShareEXPERTRiku_Kobayashianswered a month ago"


Question: Timeseries Value Lookup

"The dataset present:Time. Odometer readingt1,     120t2,     210......I am trying to find out how many miles the car has driven in the last 30 days in QuickSight.On reviewing a help document(https://docs.aws.amazon.com/quicksight/latest/user/periodToDateAvg-function.html)  I thought of using PeriodTodateAvg function.periodToDateAvg(Odometer reading,timeStamp,MONTH)The above formula is giving me null values.It would be really helpful if someone could guide me.Thank youFollowComment"


Question: Some modules can be used with NodejsFunction(AWS CDK) and some cannot?

"I defined a lambda function using NodejsFunction of AWS CDK.I installed the modules I want to use in my lambda function in node_modules of CDK.When I execute sam local invoke, some modules succeed and others fail.When an error occurs, the error message "File not found in '/var/task/...'" is displayed.Does this mean that some modules can be used with NodejsFunction and some cannot?lambda-stack.tsnew lambda.NodejsFunction(this, 'SampleFunction', {  runtime: Runtime.NODEJS_14_X,  entry: 'lambda/sample-function/index.ts'})lambda/sample-function/index.ts (use 'date-fns') -> succeeded!import { format } from 'date-fns'export const handler = async () => {  try {    console.log(format(new Date(), "'Today is a' eeee"))  } catch (error) {    console.log(error)  }}lambda/sample-function/index.ts (use 'chrome-aws-lambda') -> failedconst chromium = require('chrome-aws-lambda')export const handler = async () => {  try {    const browser = await chromium.puppeteer.launch()  } catch (error) {    // Cannot find module '/var/task/puppeteer/lib/Browser'    console.log(error)  }}lambda/sample-function/index.ts (use 'pdfkit') -> failedconst PDFDocument = require('pdfkit')export const handler = async () => {  try {    const doc = new PDFDocument()  } catch (error) {    // no such file or directory, open '/var/task/data/Helvetica.afm'    console.log(error)  }}FollowComment"

Answer: 0You need to make sure and add the modules like this hereCommentSharejthornes-awsanswered 10 months ago


Question: EC2 Instances Several Ports Open

"Hi,Recently I have received an email from AWS and the detail follows.In reviewing your Amazon EC2 instances, it appears you have left several ports open to the public (0.0.0.0/0).Please let me know how to fix this issue.FollowComment"

Answer: "1Hello there,It is not considered a good practice to have the ports of your resources open to the public as attackers may gain access to your resource and cause harm.The best approach to fix this would be to configure your security group to control the traffic to your resource. A security group acts as a virtual firewall for your instance to control inbound and outbound traffic, for more information on security groups, please see reference [1].You can configure the security group of your EC2 instance by allowing traffic from your own ip address or a selected range of ip addresses instead of having your ports open to the public.For specific security group rules, please see reference [2].References:[1] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/working-with-security-groups.html[2] https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/security-group-rules.htmlI hope this helps.CommentShareAsenathianswered a year ago"


Question: VPC - Public/Private Subnets - Unable to access from internet

"Hi,I have setup a new VPC, with a Public and Private subnet using the VPC wizard.In the public subnet I have a reverse proxy server.In the private subnet an Application server/DB.All security groups have been configured.I can access all instances inside the VPC from within the VPC (on 10.0.0.* addresses).I can ssh into reverse proxy ec2 in public subnet, and from there to the instances in the private subnet.The above has been configured using the AWS guide - https://docs.aws.amazon.com/vpc/latest/userguide/VPC_Scenario2.html#VPC_Scenario2_ImplementationThe only thing I cannot do is browse to the elastic ip address on the NAT Gateway.  It eventually times out with 'The requested URL could not be retrieved'.Does anyone have any ideas where to start looking?  Hope so :-)Thank you,CraigFollowComment"

Answer: "0Hi Craig-W,you can use a NAT gateway to allow your private instances to access Internet resources but this is strictly un-directional that means that the NAT GW will prevent the internet from initiating connections with the instances.More information here [1] and here [2].[1] https://docs.aws.amazon.com/appstream2/latest/developerguide/managing-network-internet-manual.html[2] https://docs.aws.amazon.com/vpc/latest/userguide/vpc-nat.htmlCommentShareAWS-User-3760894answered 4 years ago0Hi Craig, was this resolved? What kind of proxy server was deployed? Was routing and NAT enabled on the proxy? I have a similar issue and interested to know the outcome. Thanks.CommentShareBiscuitTinanswered a year ago"


Question: Daily Business Report Sections

"Hi Folks,The Daily Business Report has multiple sections, is there a way to request on a small subset of these sections? I.E Say I only want Section 3 of that report?I'm trying to find an easier way to ingest this report to my BI Tool, but the multiple sections make it tricky to split.Is it possible?Dave.FollowComment"


Question: SageMaker MXNet local mode not working

"Hi, I am trying to fit an MXNet model locally. I am adapting this https://aws.amazon.com/blogs/machine-learning/use-the-amazon-sagemaker-local-mode-to-train-on-your-notebook-instance/ and doing the following:bucket = 'XXXXXXXXXXX'prefix = 'sagemaker/cifar-bench/data'inputs = sagemaker_session.upload_data(    path='data',    bucket=bucket,     key_prefix=prefix)print('data sent to ' + inputs)Inception = MXNet('gluon_cifar_net.py',           role=role,           train_instance_count=1,           train_instance_type='local_gpu',          framework_version='1.2.1',          base_job_name='cifar10-inception-',          hyperparameters={'batch_size': 256,                            'optimizer': 'sgd',                           'epochs': 100,                            'learning_rate': 0.1,                            'momentum': 0.9})Inception.fit(inputs)which returns an OSError: [Errno 2] No such file or directoryIn the error log I can see that there seems to be error at self.latest_training_job = _TrainingJob.start_new(self, inputs) and self.sagemaker_client.create_training_job(**train_request)How can I make the local mode work?FollowComment"

Answer: "0Accepted AnswerIt is very likely that you don't have docker-compose (or docker) installed in the box, that is why you are getting a No such file or directory.If you want to use the GPU setup I would recommend running on a sagemaker notebook instance. Navigate to one of the example notebooks such as: https://github.com/awslabs/amazon-sagemaker-examples/blob/master/sagemaker-python-sdk/mxnet_gluon_cifar10/mxnet_cifar10_local_mode.ipynbAnd run the setup.sh cell. This will install and configure all the docker dependencies correctly and then you should be able to use MXNet locally on GPU without any issue.CommentShareAWS-User-8523138answered 5 years ago0Hello,I am attempting to run my estimator locally within a SageMaker Studio Notebook but running into the following issue when running setup.sh:!/bin/bash ./setup.sh./setup.sh: line 3: sudo: command not foundThe user does not have root access. Everything required to run the notebook is already installed and setup. We are good to go!I am using the script from here: https://github.com/aws/amazon-sagemaker-examples/blob/main/sagemaker-python-sdk/pytorch_cnn_cifar10/setup.shI've read online that when you start a SageMaker notebook, you are supposed to have root access, but I do not.  Please help.Edit: Nevermind, I referenced this issue https://github.com/aws/amazon-sagemaker-examples/issues/1419 and see that Studio Notebooks do not inherently support local mode.CommentShareSamuelanswered 2 days ago"


Question: How get message Visibility Timeout value in Lambda?

Hi! How can I get a message VisibilityTimeout value in Lambda (Node.js script) triggered by SQS? I need to change this value for staying the message in Queue for a longer period for next processing. Or how can I get the VisibilityTimeout value of the Queue itself programmatically?P.S. I'm deploying the stack via serverless-framework.FollowComment

Answer: "1Accepted AnswerUsually you can get the message visibility timeout when you make a call to get_messages, however, when invoked with Lambda, the Lambda service makes the call to get_messages, and it seems it does not ask for this attribute.You could make a call to get_queue_attributes to the get the defines visibility timeout on the queue, but remember that you can override this value for individual messages when your message producer sends the messages to the queue.CommentShareEXPERTUrianswered a year ago"


Question: How to set up SMTP for my application?

"Hello, i have a application that receives data from weather stations and sends out alert via emails. I always used Google SMTP service but recently they discontinued their basic setup and my aplication is not capable of using it with higher level of security. I have my EC2 running in Ohio but my domain i verified in Virginia on the SES page. I believe i created credentials already but when i insert the credentials and password that i took from my IAM page and configure them on my aplication, it shows error: "the server has closed the conection" when trying to send a test email. Im also out of Sanbox already and yet i dont know what could be wrong. I have tried with port 25, 465 and 587 and neither works. On my EC2 i have outbound trafic port open to all. Please help. Thanks in advanceFollowCommentjbennett 10 months agoI would step back through your setup following these notes: https://aws.amazon.com/premiumsupport/knowledge-center/ses-create-smtp-credentials/SharePrivatepilot07 10 months agojbennett, thank you for the link. I verified my domain on the same region now as my EC2, created the credentials on SES dashboard with an IAM user that has Administrator Access and yet its not working. What else could i be doing wrong. Only port 465 on TLS security shows: The server closed the connection. Port 25 shows "indefined error id", and port 587 says "bad login or password" on my aplication.Share"


Question: install package - dependency conflict

"Hi all,I'm trying to install cpan. I need it to install missing perl module(s).$ sudo yum install cpanGetting error:Loaded plugins: priorities, update-motd, upgrade-helperamzn-main                                                                                | 2.1 kB  00:00:00     amzn-updates                                                                                | 2.5 kB  00:00:00     898 packages excluded due to repository priority protectionsResolving Dependencies--> Running transaction check---> Package perl-CPAN.noarch 0:1.9800-294.43.amzn1 will be installed--> Processing Dependency: perl(local::lib) for package: perl-CPAN-1.9800-294.43.amzn1.noarch--> Processing Dependency: perl(ExtUtils::MakeMaker) for package: perl-CPAN-1.9800-294.43.amzn1.noarch--> Processing Dependency: perl(Data::Dumper) for package: perl-CPAN-1.9800-294.43.amzn1.noarch--> Running transaction check---> Package perl-Data-Dumper.x86_64 0:2.145-3.5.amzn1 will be installed---> Package perl-ExtUtils-MakeMaker.noarch 0:6.68-3.5.amzn1 will be installed--> Processing Dependency: perl(Test::Harness) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Packlist) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Manifest) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Installed) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Install) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch---> Package perl-local-lib.noarch 0:1.008010-3.6.amzn1 will be installed--> Running transaction check---> Package perl-ExtUtils-Install.noarch 0:1.58-294.43.amzn1 will be installed--> Processing Dependency: perl-devel for package: perl-ExtUtils-Install-1.58-294.43.amzn1.noarch---> Package perl-ExtUtils-Manifest.noarch 0:1.61-244.5.amzn1 will be installed---> Package perl-Test-Harness.noarch 0:3.28-3.6.amzn1 will be installed--> Running transaction check---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: systemtap-sdt-devel for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: perl(ExtUtils::ParseXS) for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: gdbm-devel for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: db4-devel for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Running transaction check---> Package gdbm-devel.x86_64 0:1.8.0-36.6.amzn1 will be installed---> Package libdb4-devel.x86_64 0:4.8.30-13.el7 will be installed--> Processing Dependency: libdb4(x86-64) = 4.8.30-13.el7 for package: libdb4-devel-4.8.30-13.el7.x86_64---> Package perl-ExtUtils-ParseXS.noarch 1:3.18-2.5.amzn1 will be installed---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements---> Package systemtap-sdt-devel.x86_64 0:3.2-2.35.amzn1 will be installed--> Running transaction check---> Package db4.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted--> Processing Dependency: db4 = 4.7.25-18.11.amzn1 for package: db4-utils-4.7.25-18.11.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam_ccreds-10-4.9.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-4.4.0-3.23.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.8-12.33.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: python27-libs-2.7.16-1.130.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python27-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: db4-utils-4.7.25-18.11.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-tools-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.5.4-6.18.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: sendmail-8.14.4-9.14.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.11.3-40.76.amzn1.x86_64---> Package libdb4.x86_64 0:4.8.30-13.el7 will be obsoleting---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Running transaction check---> Package db4.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam_ccreds-10-4.9.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-4.4.0-3.23.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.8-12.33.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: python27-libs-2.7.16-1.130.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python27-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-tools-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.5.4-6.18.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: sendmail-8.14.4-9.14.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.11.3-40.76.amzn1.x86_64---> Package db4-utils.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted---> Package libdb4-utils.x86_64 0:4.8.30-13.el7 will be obsoleting---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Processing Dependency: /usr/bin/db_stat for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Processing Conflict: libdb4-4.8.30-13.el7.x86_64 conflicts filesystem < 3--> Finished Dependency ResolutionError: Package: iproute-4.4.0-3.23.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: httpd24-tools-2.4.41-1.88.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: /usr/bin/db_stat           Removing: db4-utils-4.7.25-18.11.amzn1.x86_64 (installed)               Not found           Obsoleted By: libdb4-utils-4.8.30-13.el7.x86_64 (epel)               Not foundError: Package: pam-1.1.8-12.33.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: libdb4 conflicts with filesystem-2.4.30-3.8.amzn1.x86_64Error: Package: python27-libs-2.7.16-1.130.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-libs-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: httpd24-2.4.41-1.88.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-python27-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: pam_ccreds-10-4.9.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64 (amzn-updates)           Requires: /usr/include/db.h           Available: db4-devel-4.7.25-18.11.amzn1.x86_64 (amzn-main)               Not foundError: Package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: sendmail-8.14.4-9.14.amzn1.x86_64 (@amzn-main)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: apr-util-1.5.4-6.18.amzn1.x86_64 (@amzn-main)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigestTried with --skip-broken key as suggested$ sudo yum install cpan --skip-brokenNo errors this time, but needed packages skipped and cpan is not installed as result:Loaded plugins: priorities, update-motd, upgrade-helperamzn-main                                                                                | 2.1 kB  00:00:00     amzn-updates                                                                                | 2.5 kB  00:00:00     898 packages excluded due to repository priority protectionsResolving Dependencies--> Running transaction check---> Package perl-CPAN.noarch 0:1.9800-294.43.amzn1 will be installed--> Processing Dependency: perl(local::lib) for package: perl-CPAN-1.9800-294.43.amzn1.noarch--> Processing Dependency: perl(ExtUtils::MakeMaker) for package: perl-CPAN-1.9800-294.43.amzn1.noarch--> Processing Dependency: perl(Data::Dumper) for package: perl-CPAN-1.9800-294.43.amzn1.noarch--> Running transaction check---> Package perl-Data-Dumper.x86_64 0:2.145-3.5.amzn1 will be installed---> Package perl-ExtUtils-MakeMaker.noarch 0:6.68-3.5.amzn1 will be installed--> Processing Dependency: perl(Test::Harness) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Packlist) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Manifest) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Installed) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Install) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch---> Package perl-local-lib.noarch 0:1.008010-3.6.amzn1 will be installed--> Running transaction check---> Package perl-ExtUtils-Install.noarch 0:1.58-294.43.amzn1 will be installed--> Processing Dependency: perl-devel for package: perl-ExtUtils-Install-1.58-294.43.amzn1.noarch---> Package perl-ExtUtils-Manifest.noarch 0:1.61-244.5.amzn1 will be installed---> Package perl-Test-Harness.noarch 0:3.28-3.6.amzn1 will be installed--> Running transaction check---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: systemtap-sdt-devel for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: perl(ExtUtils::ParseXS) for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: gdbm-devel for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: db4-devel for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Running transaction check---> Package gdbm-devel.x86_64 0:1.8.0-36.6.amzn1 will be installed---> Package libdb4-devel.x86_64 0:4.8.30-13.el7 will be installed--> Processing Dependency: libdb4(x86-64) = 4.8.30-13.el7 for package: libdb4-devel-4.8.30-13.el7.x86_64---> Package perl-ExtUtils-ParseXS.noarch 1:3.18-2.5.amzn1 will be installed---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements---> Package systemtap-sdt-devel.x86_64 0:3.2-2.35.amzn1 will be installed--> Running transaction check---> Package db4.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted--> Processing Dependency: db4 = 4.7.25-18.11.amzn1 for package: db4-utils-4.7.25-18.11.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam_ccreds-10-4.9.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-4.4.0-3.23.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.8-12.33.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: python27-libs-2.7.16-1.130.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python27-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: db4-utils-4.7.25-18.11.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-tools-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.5.4-6.18.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: sendmail-8.14.4-9.14.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.11.3-40.76.amzn1.x86_64---> Package libdb4.x86_64 0:4.8.30-13.el7 will be obsoleting---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Running transaction check---> Package db4.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam_ccreds-10-4.9.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-4.4.0-3.23.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.8-12.33.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: python27-libs-2.7.16-1.130.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python27-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-tools-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.5.4-6.18.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: sendmail-8.14.4-9.14.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.11.3-40.76.amzn1.x86_64---> Package db4-utils.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted---> Package libdb4-utils.x86_64 0:4.8.30-13.el7 will be obsoleting---> Package perl-devel.x86_64 4:5.16.3-294.43.amzn1 will be installed--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Processing Dependency: /usr/bin/db_stat for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-294.43.amzn1.x86_64Package db4-devel is obsoleted by libdb4-devel, but obsoleting package does not provide for requirements--> Processing Conflict: libdb4-4.8.30-13.el7.x86_64 conflicts filesystem < 3--> Running transaction check---> Package perl-CPAN.noarch 0:1.9800-294.43.amzn1 will be installed---> Package perl-Data-Dumper.x86_64 0:2.145-3.5.amzn1 will be installed---> Package perl-ExtUtils-MakeMaker.noarch 0:6.68-3.5.amzn1 will be installed--> Processing Dependency: perl(ExtUtils::Packlist) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Installed) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Install) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch---> Package perl-ExtUtils-Manifest.noarch 0:1.61-244.5.amzn1 will be installed---> Package perl-Test-Harness.noarch 0:3.28-3.6.amzn1 will be installed---> Package perl-local-lib.noarch 0:1.008010-3.6.amzn1 will be installed--> Running transaction check---> Package perl-ExtUtils-Install.noarch 0:1.58-286.38.amzn1 will be installed--> Processing Dependency: perl-devel for package: perl-ExtUtils-Install-1.58-286.38.amzn1.noarch--> Running transaction check---> Package perl-devel.x86_64 4:5.16.3-286.38.amzn1 will be installed--> Processing Dependency: systemtap-sdt-devel for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64--> Processing Dependency: perl(ExtUtils::ParseXS) for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64--> Processing Dependency: gdbm-devel for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64--> Processing Dependency: db4-devel for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64--> Processing Dependency: /usr/include/db.h for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64--> Running transaction check---> Package db4-devel.x86_64 0:4.7.25-18.11.amzn1 will be installed--> Processing Dependency: db4-cxx = 4.7.25-18.11.amzn1 for package: db4-devel-4.7.25-18.11.amzn1.x86_64Package db4-cxx is obsoleted by libdb4-cxx, but obsoleting package does not provide for requirements---> Package perl-devel.x86_64 4:5.16.3-286.38.amzn1 will be installed--> Processing Dependency: perl(ExtUtils::ParseXS) for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64--> Processing Dependency: gdbm-devel for package: 4:perl-devel-5.16.3-286.38.amzn1.x86_64---> Package systemtap-sdt-devel.x86_64 0:3.1-2.34.amzn1 will be installed--> Running transaction check---> Package db4-devel.x86_64 0:4.7.25-18.11.amzn1 will be installed---> Package perl-ExtUtils-Install.noarch 0:1.58-286.38.amzn1 will be installed--> Processing Dependency: perl(ExtUtils::Install) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Installed) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch--> Processing Dependency: perl(ExtUtils::Packlist) for package: perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch---> Package perl-devel.x86_64 4:5.16.3-286.38.amzn1 will be installed---> Package systemtap-sdt-devel.x86_64 0:3.1-2.34.amzn1 will be installedPackages skipped because of dependency problems:    db4-devel-4.7.25-18.11.amzn1.x86_64 from amzn-main    gdbm-devel-1.8.0-36.6.amzn1.x86_64 from amzn-main    libdb4-4.8.30-13.el7.x86_64 from epel    libdb4-devel-4.8.30-13.el7.x86_64 from epel    libdb4-utils-4.8.30-13.el7.x86_64 from epel    perl-CPAN-1.9800-294.43.amzn1.noarch from amzn-updates    perl-Data-Dumper-2.145-3.5.amzn1.x86_64 from amzn-main    perl-ExtUtils-Install-1.58-286.38.amzn1.noarch from amzn-main    perl-ExtUtils-Install-1.58-294.43.amzn1.noarch from amzn-updates    perl-ExtUtils-MakeMaker-6.68-3.5.amzn1.noarch from amzn-main    perl-ExtUtils-Manifest-1.61-244.5.amzn1.noarch from amzn-main    1:perl-ExtUtils-ParseXS-3.18-2.5.amzn1.noarch from amzn-main    perl-Test-Harness-3.28-3.6.amzn1.noarch from amzn-main    4:perl-devel-5.16.3-286.38.amzn1.x86_64 from amzn-main    4:perl-devel-5.16.3-294.43.amzn1.x86_64 from amzn-updates    perl-local-lib-1.008010-3.6.amzn1.noarch from amzn-main    systemtap-sdt-devel-3.1-2.34.amzn1.x86_64 from amzn-main    systemtap-sdt-devel-3.2-2.35.amzn1.x86_64 from amzn-updatesTried running$ rpm -Va --nofiles --nodigestas suggested, but it doesn't return anything.Tried also to update:$ sudo yum updateLoaded plugins: priorities, update-motd, upgrade-helperamzn-main                                                                                | 2.1 kB  00:00:00     amzn-updates                                                                                | 2.5 kB  00:00:00     898 packages excluded due to repository priority protectionsResolving Dependencies--> Running transaction check---> Package db4.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam_ccreds-10-4.9.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-4.4.0-3.23.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.8-12.33.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: python27-libs-2.7.16-1.130.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python27-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-tools-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.5.4-6.18.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: sendmail-8.14.4-9.14.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.11.3-40.76.amzn1.x86_64---> Package db4-utils.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted---> Package libdb4.x86_64 0:4.8.30-13.el7 will be obsoleting---> Package libdb4-utils.x86_64 0:4.8.30-13.el7 will be obsoleting--> Processing Dependency: /usr/bin/db_stat for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Conflict: libdb4-4.8.30-13.el7.x86_64 conflicts filesystem < 3--> Finished Dependency ResolutionError: Package: iproute-4.4.0-3.23.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: httpd24-tools-2.4.41-1.88.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: /usr/bin/db_stat           Removing: db4-utils-4.7.25-18.11.amzn1.x86_64 (installed)               Not found           Obsoleted By: libdb4-utils-4.8.30-13.el7.x86_64 (epel)               Not foundError: Package: pam-1.1.8-12.33.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: libdb4 conflicts with filesystem-2.4.30-3.8.amzn1.x86_64Error: Package: python27-libs-2.7.16-1.130.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-libs-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: httpd24-2.4.41-1.88.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-python27-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: pam_ccreds-10-4.9.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64 (installed)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: sendmail-8.14.4-9.14.amzn1.x86_64 (@amzn-main)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64 (@amzn-updates)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit)Error: Package: apr-util-1.5.4-6.18.amzn1.x86_64 (@amzn-main)           Requires: libdb-4.7.so()(64bit)           Removing: db4-4.7.25-18.11.amzn1.x86_64 (installed)               libdb-4.7.so()(64bit)           Obsoleted By: libdb4-4.8.30-13.el7.x86_64 (epel)              ~libdb-4.8.so()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles --nodigest$ sudo yum update --skip-brokenLoaded plugins: priorities, update-motd, upgrade-helper898 packages excluded due to repository priority protectionsResolving Dependencies--> Running transaction check---> Package db4.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam_ccreds-10-4.9.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-lib-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: ruby20-libs-2.0.0.648-1.32.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: iproute-4.4.0-3.23.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: pam-1.1.8-12.33.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: python27-libs-2.7.16-1.130.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-python27-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: cyrus-sasl-2.1.23-13.16.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: httpd24-tools-2.4.41-1.88.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-build-libs-4.11.3-40.76.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: apr-util-1.5.4-6.18.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: sendmail-8.14.4-9.14.amzn1.x86_64--> Processing Dependency: libdb-4.7.so()(64bit) for package: rpm-libs-4.11.3-40.76.amzn1.x86_64---> Package db4-utils.x86_64 0:4.7.25-18.11.amzn1 will be obsoleted---> Package libdb4.x86_64 0:4.8.30-13.el7 will be obsoleting---> Package libdb4-utils.x86_64 0:4.8.30-13.el7 will be obsoleting--> Processing Dependency: /usr/bin/db_stat for package: rpm-4.11.3-40.76.amzn1.x86_64--> Processing Conflict: libdb4-4.8.30-13.el7.x86_64 conflicts filesystem < 3Packages skipped because of dependency problems:    libdb4-4.8.30-13.el7.x86_64 from epel    libdb4-utils-4.8.30-13.el7.x86_64 from epelOS information:$ less /etc/os-releaseNAME="Amazon Linux AMI"VERSION="2018.03"ID="amzn"ID_LIKE="rhel fedora"VERSION_ID="2018.03"PRETTY_NAME="Amazon Linux AMI 2018.03"ANSI_COLOR="0;33"CPE_NAME="cpe:/o:amazon:linux:2018.03:ga"HOME_URL="http://aws.amazon.com/amazon-linux-ami/"Please advise.FollowComment"

Answer: "0Accepted AnswerThe error log is saying the EPEL repository (with el7 packages) is causing conflicts with Amazon Linux.According to https://aws.amazon.com/premiumsupport/knowledge-center/ec2-enable-epel/, el7 packages may work for Amazon Linux 2....and el6 packages may work for Amazon Linux (1).So you'd want to switch to a EPEL 6 repositoryEdited by: JimmyFitbux on Dec 16, 2019 6:00 PMCommentShareJimmyFitbuxanswered 3 years ago0Thanks JimmyFitbux, it worked for me.I just edited /etc/yum.repos.d/epel.repo and replaced all 7 into 6.Then ran 'yum install cpan' and it performed successfully.As I only needed to install cpan, my question is, should I leave /etc/yum.repos.d/epel.repo as is or should I change it back to 7 ?Please advise.Edited by: ymarkiv on Dec 17, 2019 8:07 AMCommentSharemarchelloanswered 3 years ago0I believe Amazon Linux 1 comes with epel.repo set to EPEL 6 by default. So you should leave it at 6.i.e. The /etc/pki/rpm-gpg directory only contains a file for RPM-GPG-KEY-EPEL-6.CommentShareJimmyFitbuxanswered 3 years ago0Thanks JimmyFitbux.CommentSharemarchelloanswered 3 years ago0I had the same issue. Sharing what worked for me for the benefit of someone else. Please note that I am no server expert.I removed epel completely using yum remove epel-release (Thanks to: https://serverfault.com/a/939946)Then did sudo yum update -yHope that helps someone.CommentSharearunbasillalanswered 2 years ago"


Question: Chime Media Capture and Concatenation APIs are missing in AWS Java SDK - 2.19.5

I am trying to make the chime video recording using aws sdk.I couldn't find the class - CompositedVideoArtifactsConfigurationhttps://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/services/chimesdkmediapipelines/model/ArtifactsConfiguration.htmlAlso I couldn't find the startMediaConcatenation API in chime client.I added the below lines in gradleimplementation(platform("software.amazon.awssdk:bom:2.19.5"))implementation("software.amazon.awssdk:chime")Any insights on this will be super helpful.FollowComment

Answer: "1Accepted AnswerMedia pipeline concatenation and compositing are only available in the ChimeSDKMediaPipelines namespace -- not Chime.So, I think you need:implementation("software.amazon.awssdk:chimesdkmediapipelines")See this doc for more detail: https://docs.aws.amazon.com/chime-sdk/latest/dg/migrate-pipelines.htmlCommentShareDougLanswered 5 months ago"


Question: how to provide my name for exam?

"Kindly help me to enter my name details for the AWS Exams correctly.My name is xxx yyy z z z ("z for Initials") as per my driving license. And xxx yyy z... z.. z...(expanded intitals)  as per other proof.So, how should i provide my name for the AWS exam. Please help me with this.Thank you.FollowComment"

Answer: "0To change your name on your AWS Certification Account, please submit a ticket to the AWS Training and Certification Support team (https://support.aws.amazon.com/#/contacts/aws-training). Select "Account Assistance" as the inquiry type and "Name Change" as the additional details and include the requested information in the description. If needed, our Support team will request documentation to process the edit. Once all necessary information is submitted, please allow up to two days for the change to be processed.CommentShareronald_lanswered 8 months ago"


Question: How is downstreamXRayEnabled used in captureHTTPs?

I am looking at the doc here:https://docs.aws.amazon.com/xray-sdk-for-nodejs/latest/reference/module-http_p.htmlThere is a downstreamXRayEnabled parameter but I don't think I understand what exactly it does. I looked at the source code to try to understand what it does. All I can see is that it added a traced attribute but it isn't apparent to me how the attribute is used. I also tried searching for usage of it by others but there aren't any meaningful results.So what's the effect of this flag exactly?ThanksFollowComment

Answer: "0Accepted AnswerHi lawlau,This flag is consumed by the backend service of X-Ray. It can be set by the user if they know the downstream service(s) being called with the captured HTTP client are instrumented with X-Ray, and will therefore generate their own segments when called. The backend uses it to determine whether traces are incomplete, or "partial," by checking to see if segments exist yet for the downstream service marked with downstreamXRayEnabled. For example, if service A calls service B like so:// In service Aconst https = AWSXRay.captureHTTPs(require('https'), true);https.get(serviceB, options...);Then the trace created from that transaction would be marked as partial until it included a segment from serviceB. You can filter by whether a trace is partial in the X-Ray console. Read more about filtering: https://docs.aws.amazon.com/xray/latest/devguide/xray-console-filters.html#console-filters-booleanThis flag is very seldom used by customers and not even implemented in most of our SDKs, since it is basically just a way to give a more strict definition of what is "complete" and what is "partial" for your traces, and it requires you to know which downstream services are instrumented with X-Ray, making it a fairly edge use case. I hope this helps!CommentShareAWS-User-2079090answered 4 years ago"


Question: IAM Policy To Create Domain in OpenSearch

"I am trying to create Domain in open search, I used the Below IAM permission but everytime it is giving me this error-:Before you can proceed, you must enable a service-linked role to give Amazon OpenSearch Service permissions to create and manage resources on your behalfI have also attached the Service Linked Role but still I am facing the IssueI am using this IAM policy{"Version": "2012-10-17","Statement": [{"Effect": "Allow","Action": ["es:ESHttpDelete","es:ESHttpGet","es:ESHttpHead","es:ESHttpPost","es:ESHttpPut","es:ESHttpPatch","ec2:AuthorizeSecurityGroupIngress","ec2:CreateNetworkInterface","ec2:CreateSecurityGroup","ec2:DeleteNetworkInterface","ec2:DeleteSecurityGroup","ec2:DescribeAvailabilityZones","ec2:DescribeNetworkInterfaces","ec2:DescribeSecurityGroups","ec2:DescribeSubnets","ec2:DescribeVpcs","ec2:ModifyNetworkInterfaceAttribute","ec2:RevokeSecurityGroupIngress","elasticloadbalancing:AddListenerCertificates","elasticloadbalancing:RemoveListenerCertificates"],"Resource": ""},{"Effect": "Allow","Action": ["es:AddTags","es:AssociatePackage","es:CreateDomain","es:CreateOutboundConnection","es:DeleteDomain","es:DescribeDomain","es:DescribeDomainAutoTunes","es:DescribeDomainConfig","es:DescribeDomains","es:DissociatePackage","es:ESCrossClusterGet","es:GetCompatibleVersions","es:GetUpgradeHistory","es:GetUpgradeStatus","es:ListPackagesForDomain","es:ListTags","es:RemoveTags","es:StartServiceSoftwareUpdate","es:UpdateDomainConfig","es:UpdateNotificationStatus","es:UpgradeDomain"],"Resource": ""},{"Effect": "Allow","Action": ["es:AcceptInboundConnection","es:CancelServiceSoftwareUpdate","es:CreatePackage","es:CreateServiceRole","es:DeletePackage","es:DescribeInboundConnections","es:DescribeInstanceTypeLimits","es:DescribeOutboundConnections","es:DescribePackages","es:DescribeReservedInstanceOfferings","es:DescribeReservedInstances","es:GetPackageVersionHistory","es:ListDomainNames","es:ListDomainsForPackage","es:ListInstanceTypeDetails","es:ListInstanceTypes","es:ListNotifications","es:ListVersions","es:PurchaseReservedInstanceOffering","es:RejectInboundConnection","es:UpdatePackage"],"Resource": ""},{"Sid": "AllowCreationOfServiceLinkedRoleForOpenSearch","Effect": "Allow","Action": ["iam:CreateServiceLinkedRole","iam:PassRole"],"Resource": ["arn:aws:iam:::role/aws-service-role/opensearchservice.amazonaws.com/AWSServiceRoleForAmazonOpenSearchService*","arn:aws:iam:::role/aws-service-role/es.amazonaws.com/AWSServiceRoleForAmazonOpenSearchService"],"Condition": {"StringLike":{"iam:AWSServiceName": ["opensearchservice.amazonaws.com","es.amazonaws.com"]}}}]}FollowComment"


Question: How do I ensure multiple people own a Workdocs file?

"How do I ensure multiple people own a Workdocs file? Just want to make sure that in case an employee leaves the company or group, that several others have ownership of a shared folder. How do I do this? How do I view existing permissions?FollowComment"

Answer: "0Hello,I would recommend to create the access for individuals. This way you can block access for individual users, e.g. if an employee of your supplier leaves the company. It also allows you to attribute log entries to the person that caused them.You would start by collecting a list of email addresses of the people you want to invite to your work-docs deployment. This has be done by a Work-docs Administrator: https://docs.aws.amazon.com/workdocs/latest/adminguide/invite_user.htmlIf you assign these users the role "Guest users" no costs will be induced, but they can only view the data that you share with them. If you want them to commend / update / create files you need to grant them the "User" role, which is a payed user type (currently 5 USD/month): https://docs.aws.amazon.com/workdocs/latest/adminguide/users_ovw.htmlAfter that I would recommend to create a folder structure by external party. On this level you can create the necessary permissions for the invited employees of that company. This will be inherited by every subfolder and file that you create: https://docs.aws.amazon.com/workdocs/latest/adminguide/permissions.htmlCommentShareSUPPORT ENGINEERAWS-User-Chiraganswered 9 months ago"


Question: Is there a way to get the total execution time of an ECS task?

"Hi, I need to get the execution time of  an ECS task. With CloudTrail, I'm able to get the start time of the task but can't find any tag with stop/finish execution timestamp information. How can I achieve that?Thank you very much.FollowComment"

Answer: "1Accepted AnswerRecent tasks are visible on the ECS Tasks List. You will need to filter on Desired Status=Stopped. For historical task information, you can use the CloudWatch Container Insights. Please see here for a step by step  guide.CommentShareAhmet Akananswered a month agoEXPERTkentradreviewed a month agoPablo AB a month agoAwesome link you provided. Thank you very much. Finally, is there a way to convert the total execution time into a Metric?Share"


Question: Can't run 'rails console' on Elastic Beanstalk Amazon Linux 2

"I'm working on upgrading a Rails 6 EB environment to Amazon Linux 2.The app is working fine, but I'm having trouble running rails console on the environment.Normally, I'd do something like this:eb sshcd /var/app/currentsudo subundle exec rails cBut now, on Amazon Linux 2, it throws an error that my gems aren't installed. They seem to be installed in the vendor directory as part of the deployment, but bundler isn't recognising these.To work around this, I have to manually run bundle install - which adds a couple of minutes whenever I have to run a console command.Is there a solution to get this working again as easily as it did on Amazon Linux 1?FollowComment"

Answer: 0Accepted AnswerThe problem is that my application's environment variables are no longer set on the ec2-user when logging in.There's a knowledge base article about how to get envvars loading by using an .ebextension file. This solves the problem.CommentSharetallytarikanswered a year ago