By using AWS re:Post, you agree to the Terms of Use
/Front-End Web & Mobile/

Front-End Web & Mobile

AWS offers a broad set of tools and services to support development workflows for native iOS/Android, React Native, and JavaScript developers. Discover how easy it is to develop, deploy, and operate your app, even if you are new to AWS. And with the speed and reliability of AWS infrastructure, deliver secure apps that scale from prototype to millions of users, automatically.

Recent questions

see all
1/18

StartCallAnalyticsJob : User is not authorized to access this resource

Hi everybody, I wanna ask you about AWS Transcribe Analytics Call. API is well with AWS Transcribe but I need also sentiment Analysis, so I try to use AWS Transcribe Analytics. There is my code : ``` from __future__ import print_function import time import boto3 transcribe = boto3.client('transcribe', 'us-east-1') job_name = "my-first-call-analytics-job" job_uri = "PATH_S3_TO_WAV_WHO_HAD_WORD_FOR_AWS_TRANSCRIBE" output_location = "PATH_TO_CREATED_FOLDER" data_access_role = "arn:aws:s3:::MY_BUCKET_NAME_WHERE_WAV_FILES" transcribe.start_call_analytics_job( CallAnalyticsJobName = job_name, Media = { 'MediaFileUri': job_uri }, DataAccessRoleArn = data_access_role, OutputLocation = output_location, ChannelDefinitions = [ { 'ChannelId': 0, 'ParticipantRole': 'AGENT' }, { 'ChannelId': 1, 'ParticipantRole': 'CUSTOMER' } ] ) while True: status = transcribe.get_call_analytics_job(CallAnalyticsJobName = job_name) if status['CallAnalyticsJob']['CallAnalyticsJobStatus'] in ['COMPLETED', 'FAILED']: break print("Not ready yet...") time.sleep(5) print(status) ``` I had done aws configure and I use a IAM user who have AdministratorAccess. > **botocore.exceptions.ClientError: An error occurred (AccessDeniedException) when calling the StartCallAnalyticsJob operation: User: MY_ARN_USER is not authorized to access this resource** Any help please ? Thank you very much!
0
answers
0
votes
4
views
asked 12 hours ago

Amazon SES - Do not want mail forwarded to Amazon as it may cause lost mail

Hi, We have a (maybe) unique situation. Our company setup Amazon SES to send customer notifications, etc. This appears to be quite reliable! However, we have a potential issue that we hope we can resolve. We configured an MX record as required by Amazon. It is pretty simple to explain. We initially setup the MX records as required... mail.example.com (priority 5) And also: feedback-smtp.us-east-2.amazonses.com (priority 10) This exposes a potential issue: If we are receiving an email, and the server is rebooting for an update, or there is a temporary connection issue at the hosting provider, the server sending us the mail will then fall back to feedback-smtp.us-east-2.amazonses.com. But because there are a number of mailboxes in the company, there is no way we can receive mail at feedback-smtp.us-east-2.amazonses.com. We need it to not accept any connection, so the SMPT server that sent the mail will re-queue it and try to send it to us again. I deleted the MX Record to prevent this, then I got the message below from Amazon. "IMPORTANT: If Amazon SES cannot detect the required MX record in 3 days, you will no longer be able to use "example.com" as a MAIL FROM domain. Consequently, any verified identities that are configured to use this MAIL FROM domain will not be able to send emails unless they are configured to fall back to the Amazon SES default MAIL FROM domain." Is there any way to prevent feedback-smtp.us-east-2.amazonses.com from accepting any connection for incoming mail for our company, so it will not generate a permanent error? Yesterday there was an issue at our host with receiving connections from different regions (it appears). This caused Gmail to detect feedback-smtp.us-east-2.amazonses.com as our main server even though it was sent from mail.example.com, and it was bounced saying "The IP address sending this message does not have a 550-5.7.25 PTR record setup". In summary, is there a workaround to prevent Amazon from receiving mail should our regular server be rebooting or have a temporary connection issue. Hope this makes sense. Thanks, Steve
0
answers
0
votes
6
views
asked 14 hours ago

API GW HTTP API: Cross Account Access via IAM

Hi, I have an **API-GW HTTP API** (in account A) that uses **IAM** auth. I'm trying to invoke that API using an **IAM role** from another account (account B) I'm getting 403 responses when trying to invoke the **API-GW** from account B. I'm able to successfully invoke it from its own account (account A). The IAM role in **account B** has the following **policy** ``` { "Version": "2012-10-17", "Statement": [ { "Action": "execute-api:Invoke", "Resource": [ "arn:aws:execute-api:*:ACCOUNT-A-ID:*" ], "Effect": "Allow" } ] } ``` I have a "CrossAccountInvocationRole" in **account A** with **Policy** ``` { "Version": "2012-10-17", "Statement": [ { "Sid": "VisualEditor0", "Effect": "Allow", "Action": "execute-api:*", "Resource": "arn:aws:execute-api:*:ACCOUNT-A-ID:*/*/*/*" } ] } ``` with **Trusted Entities** ``` { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "AWS": [ "arn:aws:iam::ACCOUNT-B-ID:role/role-name" ] }, "Action": "sts:AssumeRole" } ] } ``` My **APIGW IAM Role in Account A** has the following **Policy** ``` { "Version": "2012-10-17", "Statement": [ { "Action": "sts:AssumeRole", "Resource": "arn:aws:iam::ACCOUNT-A-ID:role/CrossAccountInvocationRole", "Effect": "Allow" } ] } ``` and **Trusted entities** ```{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "apigateway.amazonaws.com" }, "Action": "sts:AssumeRole" } ] } ``` I tried attaching the above policy to the Lambda that is invoked by API-GW as well To test, I used the AWS CLI `sts assume-role` to get credentials for the IAM role and then used those credentials in a Lambda in account B as well as the Postman application. Both gave me 403 errors. Question: 1. Is it even possible to do cross account invocation on an API GW HTTP API with IAM? 2. If yes, what an I doing wrong?
1
answers
0
votes
28
views
asked 4 days ago

Popular users

see all
1/18

Learn AWS faster by following popular topics

1/4