By using AWS re:Post, you agree to the Terms of Use

Welcome to AWS re:Post

re:Post gives you access to a vibrant community that helps you become even more successful on AWS

Learn AWS faster by following popular topics

see all
1/18

Recent questions

see all
1/18

Amazon SES production access denied without any important reason

Amazon SES production access denied without any important reason. My Case ID 9489919231 was deny without any important reason, if Amazon SES service is so rude for new customers, why it's not described in SES docs? Why in SES docs everything look's very easy? I'm doubling here my request look at them and tell me please, someone, WHAT IS REASON? "Production access request Service: SES Sending Limits Region: us-west-2 Please enable production access ------------ Use case description: First of all, we want to say you Hello! We plan use SES to send messages, transactional messages to our members. You can look here: https://peretz-centre.org/join-us/ This is way, how visitors become members and how they being add to recipient list. All bounces, complaints and unsubscribe requests we plan to track with SNS service, when our app receive message from SNS - we will stop any sending to this address. Please enable production access on our account. Mail Type: TRANSACTIONAL Website URL: https://peretz-centre.org Replied to first deny: Usually we send messages every day, because for one year of our membership we have already about 350.000 members. So every day we receive new members requests. About recipient list maintaining, we take several tools to proceed that: 1. Service for validation and list cleaning. 2. We track all bounces and spam rates of our campaign. 3. Using segmentation and personalisation. 4. We dont send spam, only high quality content. All bounces, complaints and unsubscribe requests we plan to track with SNS service, when our app receive message from SNS - we will stop any sending to this address. We will setup serverless-ly (SNS + SQS + Lambda) so the cost should be next to nothing. And it's very effective solution. There is a lot of information from AWS how to do this - and we will do this after you enable production access on account. Thank you for attention, have a nice day!" Tell me, when Amazon Web Services will already respect customers and new users? If SES only for old users or for users with big budget - NOTIFY about that.
0
answers
0
votes
2
views
AWS-User-6191652
asked 9 hours ago

metadata service is unstable: connection timeout, Failed to connect to service endpoint etc

start from recently, our long running job are hitting metadata issue frequently. The exceptions various, but the all point to EC2 metadata service. It's either failed to connection the endpoint, or timeout to connect to the service, or complaining that I need to specify the region while building the client. The job is running on EMR 6.0.0 in Tokyo, with correct Role set, and the job has been running fine for months, just started from recent, it became unstable. So my question is: how can we monitor the healthy the metadata service? request QPS, success rate, etc. A few callstacks ``` com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.SdkClientException: Unable to load AWS credentials from any provider in the chain: [com.amazon.ws.emr.hadoop.fs.guice.UserGroupMappingAWSSessionCredentialsProvider@4a27ee0d: null, com.amazon.ws.emr.hadoop.fs.HadoopConfigurationAWSCredentialsProvider@76659c17: null, com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.auth.InstanceProfileCredentialsProvider@5c05c23d: Failed to connect to service endpoint: ] at com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.auth.AWSCredentialsProviderChain.getCredentials(AWSCredentialsProviderChain.java:136) ``` ``` com.amazonaws.SdkClientException: Unable to find a region via the region provider chain. Must provide an explicit region in the builder or setup environment to supply a region. at com.amazonaws.client.builder.AwsClientBuilder.setRegion(AwsClientBuilder.java:462) at com.amazonaws.client.builder.AwsClientBuilder.configureMutableProperties(AwsClientBuilder.java:424) at com.amazonaws.client.builder.AwsSyncClientBuilder.build(AwsSyncClientBuilder.java:46) ``` ``` com.amazonaws.SdkClientException: Unable to execute HTTP request: mybucket.s3.ap-northeast-1.amazonaws.com at com.amazonaws.http.AmazonHttpClient$RequestExecutor.handleRetryableException(AmazonHttpClient.java:1189) ~[aws-java-sdk-bundle-1.11.711.jar:?] Caused by: java.net.UnknownHostException: mybucket.s3.ap-northeast-1.amazonaws.com at java.net.InetAddress.getAllByName0(InetAddress.java:1281) ~[?:1.8.0_242] at java.net.InetAddress.getAllByName(InetAddress.java:1193) ~[?:1.8.0_242] at java.net.InetAddress.getAllByName(InetAddress.java:1127) ~[?:1.8.0_242] ``` ``` com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.SdkClientException: Failed to connect to service endpoint: Caused by: java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) ```
0
answers
0
votes
0
views
Hubery
asked 18 hours ago

SageMaker AutoML generates ExpiredTokenException

Hi, I can train models using different AWS SageMaker estimators, but when I use SageMaker AutoML Python SDK the following error occurs about 15 minutes into the model training process: "botocore.exceptions.ClientError: An error occurred (ExpiredTokenException) when calling the DescribeAutoMLJob operation: The security token included in the request is expired" The role used to create the AutoML object is associated with the following AWS pre-defined policies as well as one inline policy. Can you please let me know what I’m missing that's causing this ExpiredTokenException error? AmazonS3FullAccess AWSCloud9Administrator AWSCloud9User AmazonSageMakerFullAccess Inline policy: { "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": [ "iam:PassRole" ], "Resource": "*", "Condition": { "StringEquals": { "iam:PassedToService": "sagemaker.amazonaws.com" } } }, { "Effect": "Allow", "Action": [ "sagemaker:DescribeEndpointConfig", "sagemaker:DescribeModel", "sagemaker:InvokeEndpoint", "sagemaker:ListTags", "sagemaker:DescribeEndpoint", "sagemaker:CreateModel", "sagemaker:CreateEndpointConfig", "sagemaker:CreateEndpoint", "sagemaker:DeleteModel", "sagemaker:DeleteEndpointConfig", "sagemaker:DeleteEndpoint", "cloudwatch:PutMetricData", "logs:CreateLogStream", "logs:PutLogEvents", "logs:CreateLogGroup", "logs:DescribeLogStreams", "s3:GetObject", "s3:PutObject", "s3:ListBucket", "ecr:GetAuthorizationToken", "ecr:BatchCheckLayerAvailability", "ecr:GetDownloadUrlForLayer", "ecr:BatchGetImage" ], "Resource": "*" } ] } Thanks, Stefan
0
answers
0
votes
0
views
AWS-User-9933965
asked 18 hours ago