I am new AWS user.
I want to use aws SES feature using java api.
When i tried to execute sample SES code of EC2 java api then it gives me following exception:-
"Status Code: 400,
AWS Service: AmazonSimpleEmailService,
AWS Request ID: 191f7c11-8652-11e2-be1c-6dd0975de4df,
AWS Error Code: RequestExpired,
AWS Error Message: Request timestamp: Wed, 06 Mar 2013 01:06:01 GMT expired.
It must be within 300 secs/ of server time."
Why this exception comes?
Please help me to solve this issue.
Thank you.
Amazon Forums have several posts approaching this issue. Please have a look at this specific thread.
In general, your server might be out of sync with UTC, and Amazon servers are not accepting your requests because of a much different timestamp.
Related
I'm trying to create a cloud profile to start an EC2 instance in TeamCity. But I get Failed to connect to Amazon EC2. null (Service: AmazonEC2; Status Code: 400; Error Code: 400 Bad Request; Request ID: null) There is no any explanations about this. As you can see I have changed serverURL to https://google.com, but it produces the same error even when using the correct TeamCity server.
I checked outbound connections of the EC2 instance where TeamCity is deployed and it's fine. Also tried by changing the region.
Any thoughts?
Cheers!
Does SNS support token based connection to APNs?
I see the AWS documentation on certificate based connection to APNs, but don't see any way to connect via tokens.
Is this available? If so, is there any AWS documentation on this because I can't find it.
Currently (i.e as of 07th March 2020) Amazon Simple Notification Service (SNS) doesn't support Token Based Connection (.p8) to APNs
I would like to refer you to another AWS service called Amazon Pinpoint which I know support Token Based Connection (.p8) to APNs.
SNS now supports token-based authentication for APNs, using .p8 files. You can find more information about it here: https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-sns-token-authentication-api-mobile-notifications/
My application shuts down sometime with the following error in the console:
PlatformApplicationDisabledException
I've reached out to aws service team to investigate what I was doing wrong in my program.
So, they have replied that:
PlatformApplicationDisabledException is triggered when the downstream
push-notification service rejects the credentials provided with the
request.
In your case, the downstream provider is APNS_SANDBOX. Ensure that you
are using valid Sandbox credentials with your APNS SNS application.
Apple rejected your credentials, likely due to them being expired, or
for a production application.
Can someone guide me to resolve this issue.
Thank you.
I setup my Jasper Report Server. As well as I already schedule my reports and every things was working fine with me. During the setup, I was using my personal Gmail accounts to share the emails witch associated with gmail.smtp.com
I changed the SMTP setup to my domain account (Corporate Microsoft Exchange Server) but emails stopped working. I believe there is issue with the SMTP configuration.
Whenever I change the setup to my personal email, everything working fine but when I swap it to my domain account, which is corporate Microsoft Exchange server, it is not working. My domain account Microsoft outlook base, I believe there should not be any issue. Using same credential, I can access from the web.
I check following provided URL from Jasper Community and it seems I am following the same.
URL: https://community.jaspersoft.com/wiki/configuring-report-scheduler
What could be the issue?
Here is the error details, which I got:
Subject: The job failed to execute. Review its parameters.
Date: Today
Component: Report Scheduler
Message:
Job: Immediate Execution2323 (ID: 3889) Report unit: /reports/Paid_Violation_of_last_week_ Quartz Job: ReportJobs.job_3889 Quartz Trigger: ReportJobs.trigger_3886_0 Error Message: There was an error on the server. Try again or contact site administrators. (Error UID: 4d89f7cc-28cc-4d1d-86cb-cd0c764e1348).
I would appreciate if someone will share his/her experience if he/she face the same before.
I have an AWS API Gateway endpoint that uses lambda proxy integration to retrieve data from an AWS RDS instance.
I use a yaml file to re-deploy the api, Once the API is re-deployed, The endpoint, illustrated above, throws an "Internal Server Error" every time I re-deploy the api.
The error goes off if I uncheck and then check the lambda proxy integration option/tick-box on the endpoint. This manual step is cumbersome and extremely unintuitive and can raise serious production issues.
Anyone facing similar issue know how to solve it without the additional "unchecking and checking" (manual) step?
What change in YAML can solve this problem ?
Under your AWS::ApiGateway::Method resource, make your Integration.Type as AWS_PROXY
https://docs.aws.amazon.com/apigateway/api-reference/resource/integration/#type