AWS java project creation error - amazon-web-services

I have installed aws plugins from http://aws.amazon.com/eclipse.
While creating aws java project, next and finish buttons are not enabling.
While opening eclipse, I am getting below errors.
Couldn't read regions file,
Failed to cache regions file,
Unable to check status of AWS SDK for Java download and Unable to refresh security groups: Unable to execute HTTP request: peer not authenticated.

The problem is,your AWS SDK is not installed and updated properly . Just click on >Help in eclipse and then click on >Installation Details and from that reinstall AWS Eclipse plugin .
Please make sure that url of plugin is appropriated for your eclipse version.
It will solve your problem.

Try using a new workspace and you will be good to go.
Let know if the problem still persists.

Related

AWS full-stack react app. Build failed to complete successfully

I'm trying to make an SPA in React with AWS.
While I was going through the basic steps here (Step 3 ADD AUTHENTICATION ) :
I deployed the changes to the live environment, but the build failed.
I'm getting this error.
Can anyone please explain to me what caused this error?
This seems to be a known issue in the Amplify GitHub and can happen when the Amplify CLI version used by the Amplify Console is mismatched with the version you are using locally. Here is some more information: https://github.com/aws-amplify/amplify-cli/issues/6117#issuecomment-794176834
Compare your Amplify App -> Build Settings -> Build image settings -> Amplify CLI version with your version installed on your development machine by running amplify --version
Other than checking for version matching, I also have found out if amplify backend doesn't have a role attached to it, the built process is going to fail. to do that you follow the link bellow directions: https://docs.aws.amazon.com/amplify/latest/userguide/how-to-service-role-amplify-console.html
However, before that, go to the General tab under App settings to see if the role is empty or not. You might already have a role, if not follow that link.

Google Cloud SDK installation fails on Windows

Tried installing Google SDK on Windows 2016 machine using both online and offline install. In both the cases installation fails with below error. Machine is behind firewall.
ERROR: (gcloud.components.update) Failed to fetch component listing from server. Check your network settings and try again.
When the error: "ERROR: (gcloud.components.list)" appears, it means that GCloud is attempting to make a request to the following url: "https://dl.google.com/dl/cloudsdk/channels/rapid/components-2.json". It seems that your configuration prevents this URL from being fetched, and there could be many factors for this behavior.
My suggestion is to:
Check if dl.google.com is part of the allowed IPs in your firewall rules.
According to the official documentation if you are behind a proxy/firewall, the components that the Cloud SDK installers download from the internet may not work correctly.
Sometimes this error is caused because SSL Cert Verification is failing for the component listing request from Google's servers. I have found a post where someone from the community resolved this issue.
Also, I found this other thread with a similar problem.
For a simpler installation process when proxy configuration is necessary, you might follow these instructions to install the SDK using self-contained versioned archives.
I have found another post where a user with the same error message was able to resolve it only disabling the IPv6, you can use the follow the next guide to disable your IPv6 on windows

Authentication Error when Trying to Log into WSO2 IoT Server - Device Management Console in wso2-iot-3.3.0

I followed the instructions in the link (https://docs.wso2.com/display/IOTS330/Enterprise+IoT+solution) in Windows to start WSO2 IoT server. So, broker, iot-server and analytics are started. But, when I'm trying to log in to the device management console using admin login or the login credentials I created, it gives me an authentication error.
I tried the solutions in this answer (Not able to access WSO2 IoTS Device Management Console in wso2-iot-3.3.0 when logged in 'admin') also (Reducing Java version to 1.8.0_144 and making the compression parameter to off in all the catalina-server.xml files). But any of it didn't work for me.
I have attached the screen shots of the error. Please help me to go through this! Thank you.
Error in browser
Error description in iot-server console-Part 1
Error description in iot-server console-Part 2
This is related to the issue mentioned in the github issue mentioned below and it seems, it is already fixed in latest master.
As a quick workaround you could try to modify the startup script files (bat files in this case) and add the changes mentioned in the above git issue.
For example, you can change the file modules/distribution/src/core/bin/iot-server.bat at line number 73 as below.
FOR %%D in ("%CARBON_HOME%\wso2\lib\commons-lang*.jar") DO set CARBON_CLASSPATH=!CARBON_CLASSPATH!;".\wso2\lib\%%~nD%%~xD"
Similarly do the same change as above for files mentioned below as well.
modules/distribution/src/core/resources/profiles/backend/iot-server.bat
modules/distribution/src/core/resources/profiles/keymanager/iot-server.bat
modules/distribution/src/core/resources/profiles/manager/iot-server.bat
This should resolve the issues you are facing.
Related github issue - https://github.com/wso2/product-iots/pull/1838/files

Ionic AWS Error

I am attempting to connect my Ionic mobile app to AWS backend and keep getting the same error.
Cannot find module "../aws-exports"
I've checked the node-modules folder and this is missing, but I have no idea what I should put here to fix this error.
The same code is in a lot of files in this app.
const aws_exports = require('../aws-exports').default;
I'm not sure what this code does exactly. If anyone has an experience with Ionic that could help that would be great.
Thanks,
Matthew.
You need to follow the steps in the README. Specifically, the section on Creating AWS Mobile Hub Project. When you init the AWSMobile project, aws-imports is created for you.
P.S. aws-amplify has introduced some changes in the last couple of weeks that cause the ionic starter to not work. Follow these steps to fix the errors.
If you sign into your Amazon console and you go to your Mobile Hub.
https://console.aws.amazon.com/mobilehub/home#/
You can click on your project and it will return the ID in the URL as follows:
https://console.aws.amazon.com/mobilehub/home#/YOUR_ID_HERE/build
You can then run the following command:
awsmobile init <mobile-hub-project-id>
The AWS Mobile Hub scripts should then fetch all relative dependencies and make the appropriate installations to rectify the issue.

WS02 GREG ERROR when deploying carbon archive

I am trying to upload a carbon archive in the registry. Everything seems to be OK when I add a new application, but the log show the following error:
An error occurred while determining the latest version of the resource at the given path:
/_system/governance/trunk/wsdls/.... (path to the wsld deployed)
org.wso2.carbon.registry.core.exceptions.RegistryException: Failed to obtain the user realm for tenant: -1
I log with the admin user and everything that should be upload is in the registry.
Any help?
Thanks,
I tried to reproduce this with WSO2 G-Reg 4.1.1 but unable to reproduce it.
Please indicate the G-Reg version you have tried out this scenario.
When you upload the CAR file from Management Console, make sure to remove the previous version of the same CAR file before you upload the newer version.
This error seems to be related versioning.
Since you remove the previous version of the CAR file, the aforementioned suggestion will solve your problem.
Thanks and Regards,
Harshana
WSDLs are stored in the /_system/governance/../trunk/wsdl/.. location if you upload them via management console or upload the resource from Developer Studio Registry Browser.
But when you deploy a WSDL via a C-App, when creating the registry resource from Developer Studio, you specify a location to deploy. Hence the WSDLs deployed via C-Apps are deployed to this specified location but not the other location.
Therefore from your proxy service, you should refer the location you have mentioned to deploy your WSDL but not the default location.
Once you fix this, your Proxy service will work fine.
Thanks and Regards,
Harshana