AWS SDK doesn't work on Azure Web App service - amazon-web-services

I am working on a web app in .net core and deployed it on Azure (App Service). As a part of the app, I am creating AWS RDS MySql db. The code works well on my machine but not on the Azure. Following code snippet which is exposed as a REST API is causing a problem.
logger.LogInfo("In AWSRDS.cs->PushToCloud()");
AmazonRDSClient client = new AmazonRDSClient(awsAccessKeyId:"xxxxxxxxxxxxxx",
awsSecretAccessKey:"xxxxxxxxxxxxx");
logger.LogInfo("In AWSRDS.cs-> client created");
The above lines are wrapped with try-catch block. I get first line in the log file and nothing thereafter. No processing, no exception.
I alrady tried
re-deployments
restarting the app a few times
manually installing dotnet package via console on the Azure web app (even if the DLL exists)
Created another Azure web app (with linux hosting) only to observe same behaviour
Any clue will be greatly appreciated.

Not sure why you aren't getting any error message but I suspect the SDK is failing to resolve what AWS region to make requests to. When running in AWS the compute environment will be configured for the region the code is running and I suspect locally you have a default region configured.
Can you switch to the constructor that takes in a region enum and pass in the region you want to connect to?

Related

RavenDB on Restored AWS instance

I have a UAT ENVIRONMENT where I am using NServiceBUS endpoints. Everything works. Then when we moved to Production, the method we used to make the environment was to make an IMAGE of the UAT server and restore on a new AWS server instance
We reinstalled RAVENDB but on Windows authentication page in manage server, we are seeing the authentication from the old server. I have removed the RavenSITE folder and uninstalled RavenDB, restarted the server and tried installing again, but the old authentication line items are still coming up. Where are these getting stored? So I can go delete them.
The endpoints are also not registering with the instance and the databases are not getting created for each endpoint
Please assist!
These are stored in the System database.

How to migrate from heroku to Amazon Web Services while using parse server

I am developing an android app and was using parse.com until they shut down. I had successfully migrated from parse to Heroku but I'm now considering migrating from Heroku to AWS (due to pricing and scalability concerns). I have searched everywhere in the internet but haven't found a site that gives you the step by step instructions on how to do so. I have seen that both Heroku and AWS use mlab as a database so it can't be that hard. Detailed help will really be appreciated as I am still new to programming. Here is what I have attempted in Elastic Beanstalk:
When I was done creating the environment It said that the health was degraded, even after I copied the server variables from parse and added them to the configuration.
Do you have your server codes which u published onto Heroku? If i guessed correctly, you are using the parse-server-master template for your server right?
In that case, migration is easy. Just zip up the contents and go over to AWS Elastic Beanstalk and upload your zip. It will work ;)

WSO2 IS 5.2.0 Admin SOAP Services response time compared to WSO2 IS 5.0.0

I recently updated my environment from WSO2 IS 5.0.0 to WSO2 IS 5.2.0. My environment consists of one machine deployed on EC2 AWS instance. I am using MySQL(not the default H2 database). The machine on which the IS is deployed is Windows Server 2012 R2.
I also have a solution which wraps the IS Admin Soap services and allows me to automate some of the processes like:
-- Service Provider creation and configuration
-- User creation and configuration
-- Tenant creation and configuration
After upgrading to WSO2 IS 5.2.0 I started experiencing delays in the responses of the admin SOAP Services. Since I am using AWS I double checked whether I am using the most appropriate region to have the IS machine. Indeed it was - I am using the Frankfurt region.
I decided to do a simple test to see whether there is delay and if so how it affect my applications. So I created a simple Console Application which was hosted on my local machine and configured the Service References first against my new DEV IS 5.2.0 machine(Frankfurt region). For my test purposes I am using RemoteUserStoreManagerService?wsdl and I am trying to create a user. Ran the test several times and it seems that it takes about 6-7 seconds to create user.
Then I used the exact same conditions in order to run the test against DEV IS 5.0.0 machine which is also hosted in the same region (Frankfurt) and is using the exact same machine configuration (t2.large). Once again the Console Application was hosted on my local machine. The result from the second test was - 1 second to create the user using the very same admin SOAP service and the exact same logic in the Console Application under the same conditions the first test was executed.
Please find below image that displays some of the test results:
https://www.dropbox.com/s/h6rrhnczrutmmxw/IS5.2%20vs%20IS%205.0%20SOAP%20Service.png?dl=0
Is this a known behavior, or some sort of configuration should be applied to avoid such delays from the admin SOAP services?
Thanks in advance.
It turned out to be a configuration issue. In the following file:
"[wso2is-5.2.0_HOME]\repository\conf\identity\identity.xml"
There is a section named "EventListeners" and in there the following listener:
<EventListener type="org.wso2.carbon.user.core.listener.UserOperationEventListener" name="org.wso2.carbon.identity.mgt.IdentityMgtEventListener" orderId="50" enable="true"/>
Once I disabled this listener, all my issues regarding the delays in the responses of the SOAP admin services disappeared.
I did basic search to see what is the purpose of this listener and was able ti find the following:
http://pushpalankajaya.blogspot.bg/2016/02/account-deactivation-with-wso2-identity.html

Parse Dashboard on AWS and adding cloud code

I configured a parse server on my AWS elastic beanstalk using this guid I've tested it and it all works fine
Now I can't find a way to deploy parse dashboard on my server.
I did deployed parse dashboard on my local host and connected it to the application on server, But this way I cannot manage (Add and remove) my apps.
Another problem is that parse dashboard missing cloud code on default, I found this on git, but I cant understand where do I add the requested endpoints, is it something like adding app.use('/scripts', express.static(path.join(__dirname, '/scripts'))); on the index.js file?
in order to deploy parse-dashboard to your EC2 you need to follow the Deploying Parse Dashboard section in parse-dashboard github page
parse-dashbard github page
Please make sure that when you deploy parse-dashboard you are using https and also basic authentication (it is also part of the guide)
Now regarding the cloud code: the ability to deploy cloud code via parse CLI and to view the nodejs code in parse dashboard are not available in parse-server but those are parse.com features. Cloud code in parse-server is handled by modifying the main.js file which exist under the cloud folder and deployment should be done manually by you but the big advantage in parse-server cloud code is that you can use any NodeJS module that you want from there and you are not restricted to the modules that were used by parse.com .
Another point about the dashboard. What you can do is to create an express application and then add parse-server and parse-dashboard as a middleware to your express application and deploy the whole application to AWS and then you can enjoy both parse-server (that will be available under the /parse path, unless you changed it to something else) and parse dashboard that will be available under the /dashboard path
Enjoy :)

Umbraco Accelerator successfully deployed but wont connect

I have download the umbraco accelerator to try get an azure based CMS up and running, I have managed to change the configuration file and the command prompt log upon running the .bat files does not generate any errors.
I have created the storage and azure database and hosted service but when I look at the hosted service there is no way for me to connect into this as the connect button has been disabled. Has anyone else went through the setup and if so have you encoutnered this issue? The URL displayed in azure http://appname.cloudapp.net/umbraco/default.aspx does not work
Which Umbraco version are you deploying? AFAIK the accelerator is deprecated, but I could be wrong if you're doing something in particular, or something I haven't heard of (could be lots!) with web/hosted services.
I've deployed Umbraco 4-6 CMS through WebMatrix 2-3 to azure as a website with relative ease. I didn't need it to be a hosted service/cloudapp.
Is that url not a generic placeholder, do you have a Domain registered to point at it?
Y'know, the more I type, the more I realise I have only a shaky grasp of what you're talking about. Are you sure you need a cloudapp, will an azure website not do?