I'm trying to create AWS, API, however, I got the following error Network Failure after pressing create button. What might be an issue? Thanks in advance.enter image description here
Related
I have registered a CA certificate in AWS IoT Core. Additionally I have registered (via JITP) device certificates that are signed with the CA certificate.
Up until four hours ago my devices where able to connect to AWS IoT. Currently only devices using AWS issued certificates are able to connect.
When reading details (AWS IoT > Secure > Certificates > cert_id) for my own registered certificates AWS console responds:
An unexpected error has occurred.
Cannot read public key. OID is not RSA.
Also the console won't respond anymore without browser refresh.
I also tried to register a certificate again. That doesn't work because AWS knows the certificate is already registered.
Any pointers what could be wrong?
I only have basic support plan from AWS so I didn't find a way to ask AWS directly.
Ilkka
This is an error when using the new console experience, and has been escalated to be researched and resolved. This has no impact on any use of the ECC certificates. I created and registered an ECC certificate using the CLI and mosquitto on 22-Jan-2022 and all was working then. If you do have connectivity problems, enable logging from the AWS IoT Console->Settings, and then review the logs in CloudWatch Logs.
In the meantime, you can turn off the new console experience from the AWS IoT Console at the bottom of the left menu pane, under the Documentation link.
I am new to AWS IoT core and I have just created one simple thing and created certificate and also attached a policy to certificate and my thing.
when I go to my certificate page I can see it has my policy attached to it and also my thing attached to it. (the policy has all resource * and has all IoT:* actions)
I think I am doing all correctly but when on AWS IoT portal I go to test, I always get "Mqtt connection lost. Reconnect." on nitrification panel.
I have also come up with some python codes and used the private key and certificate which I created from above but again my client program can not connect to AWS IoT.
I am not sure why the test doesn't work at all and I always get "Mqtt connection lost"?
#Luckylukee -
Thanks for the screenshot!
My experience says that your MQTT connection error has nothing to do with the configuration of your IoT devices/certificates/policies.
Reason I say it is.. without any devices created in AWS IoT, you should still be able to click on 'Test' button and subscribe to topics without issues.
The error you reported is something very "core" between AWS IoT Test Tool and AWS IoT Server Endpoint (specific to your AWS account).
Can you try these?
Use a different browser (not in private-mode) to do the same test.
Use a different AWS Account (at least temporarily) to see if this TEST button works there! (Because, new AWS account will get you a new IoT Core Endpoint).
Good Luck!
In AWS API Gateway I am trying to deploy API to new stage, and im getting error "An unknown error occurred". I am assuming it most likely because of permission. But i have API Gateway administrator permissions.
How do find out exactly which permissions are missing? Does aws api gateway logs any deployment related events? Where do i find whats going on.
Answering your question of Api Gateway deployment events, below are typical steps I do on what's happening.
Any operation you perform on Console or SDK is essentially calling AWS APIs.
For Console failures, you can always check on client side by going to Developer Tools provided by browsers. Typically F12 key --> Network tab, replicate the issue and see which AWS Endpoint gave error or go to Console tab and see any JavaScript errors logged.
If I am still not able to determine the cause, I enable CloudTrail logs and see which user and which API call gave any error responses for which operation. CloudTrail Guide to ApiGateway.
If there is specific role or policy issue having issue, I use Policy Simulator to test policies for the role once permissions are added.
While creating a platform application when I tried to create application and push notification platform select GCM then add API key I got the following.
Invalid parameter: Attributes Reason: Platform credentials are invalid
(Service: AmazonSNS; Status Code: 400; Error Code: InvalidParameter;
Request ID: 44a04d15-c58b-5bf8-859e-0311947aac6c)
What does this mean and how can I fix this?
I got exactly same error message as yours. It seems google is migrating Firebase Cloud Messaging (FCM) to Google Cloud Messaging, and the API Key created via Credentials in API Manager of Google Cloud Platform is not working.
And here is how I get it to work.
Go to Firebase Console and import Google Cloud Project.
Go to Project settings on Firebase Console and you should see the Web API
Key of your project.
Go back to your Google Cloud Platform, and go to Credentials of API Manager, you should see there are two API keys have been generated. Browser key (auto created by Google Service) and Server key (auto created by Google Service)
The Server key (auto created by Google Service) is what you need to
use on the Amazon SNS.
Hope it can resolve your problem, and hope it is only a temporary solution that after Google done the migration, we can directly use the API key created in API Manager.
I have looked for resources on this particular problem with little luck so far so I thought I would try here.
I am attempting to create an Amazon Web Service Simple Notification Service app in the AWS-SNS console using GCM. I have created the APNS app for the iOS version with no troubles, however, when attempting to create the GCM version I receive the error: "The credentials you entered are invalid. Please enter valid credentials and try again."
In the Google APIs - API Access dashboard I have created both a key for server app and a key for android app. Below are a few screenshots to illustrate the problem.
Any suggestions as to what the problem may be or any instructional documentation recommendations would be tremendously appreciated.
More on what Rohan has said, it would be on Google's end rather than Amazon's.
Delete the Server API Key in the Google API Console, and create a new one, allowing all IP addresses. Add the new key in AWS SNS, and you should be good to go!
Amazon documentation is very old and not accurate anymore.
When you created your Application and the Credentials on Google Developers Console, from the left menu on Google developer console select:
APIs & auth -> APIs -> Google Cloud Messaging for Android -> Enable API
Google recently migrated a lot of the GCM service/credential handling to Firebase. As a result you need to create a Server Key in the Firebase Console now.
See: Amazon SNS: "Platform credentials are invalid" when re-entering a GCM API key that previously worked
You need to use the API key listed under Key for server apps (with IP locking) in the Google Console. The key listed under Android app will not work.
The Amazon SNS Getting Started with GCM documentation provides step-by-step guidance on setting up your app. If you are still having issues, please contact us via AWS Support or the Amazon SNS forum and we can troubleshoot further.
full disclosure: I am an Amazon SNS engineer.