Welcome!

@CloudExpo Authors: Elizabeth White, Zakia Bouachraoui, Liz McMillan, Yeshim Deniz, Pat Romanski

Related Topics: @CloudExpo

@CloudExpo: Blog Post

Our Experience with AWS

We have been working with Amazon Web Services for the last couple of months for various things

We have been working with Amazon Web Services for the last couple of months for various things and thouhgt of sharing our key findings with you all.

First of all, I would like to thank Amazon for providing such a great experience to us , a simple webservice call , an instance of a computer up and running. When we started our exploration, we got an account with Amazon and working with S3 for quite some time. It is an another service for storage and works well for its cause.

Then we decided to explore EC2 and started browsing various AMI's (Amazon Machine Image) that are available. First we tried with Fedora Core 4 and we could successfully load that AMI into an instance. also, allowed SSH and Web server port to be available for public access.



After following the procedures for setting up Putty given by AWS , we tried accessing our instance using Putty. We could connect but we were not able to use the instance due to frequent disconnection. After all our effort it went on drain.

Then stopped exploring AMI's for a week time and started reading the available articles. Even after going through bunch of documents , we couldn't really figure out why there was a disconnection?

Again we got charged and wanted to try a different AMI, by then we got an information in AWS forum about a stable Ubuntu release (Thanks to Eric) and tried it. This time it was great success, it worked as it is expected and never faced any disconnection.

Once we are done with our initial setup, we wanted to go further and create our own AMI for Jboss. Because at that time we couldn't really find any compeling AMI with bare minimum Ubuntu.

When we started the AMI intially we were fine with Ubuntu as a bare minimum OS and it worked perfectly fine, but then we were finding difficulties to download files, browsing a webse site using a text based web browser..etc. So we had to use apt-get to download lynx and install it. As soon as we got the lynx, started downloading the following necessary softwares for our Jboss AMI.

  1. Java 1.6 - SDK and runtime requires to run any java applications.

  2. Jboss 4.2 As - J2EE application server, requires to run any Java 2 Enterprise
    applications.

  3. Apache 2.4 - Web server require to front end any request with realted to web and
    webservices.

  4. S3Cmd - This tool is used to perform S3 related operations using command line.

Setting up apache 2.4 is an interesting story, we have download Httpd from apache webiste and tried configuring it. The configure command was complaining about the non availability of the gcc compiler. Then we had to install gcc and gcc-lib using the command apt-get command.

Then our installation went fine and successfully setup Apache 2.4. After that installed Java 1.6 and Jboss 4.2 AS. There was no problem setting up both of them.

The mod_jk connector for apache was downloaded and setup the workers.properties to connect Apache and Tomcat.

After all these setup we were able to see our Jboss home. and we thought it will be a good AMI to share and applied with Amazon. Hopefully you will have this in your hand soon.

Read the original blog entry...

More Stories By Ezhil Arasan Babaraj

At present building a start-up called Qruize Technologies. Qruize is an Information & Communication Technology Start-up based out of Chennai, India. The company comprises of two strategic business units, Qruize Labs- boutique technology research & consulting services and Qruize Apps- social media products and services. We are currently establishing our own operations in the USA and entering into strategic partnerships in the EMEA region.
Website : http://qruize.com, http://qruizemedia.com
blog : http://qruizetech.wordpress.com
Specialties Technology Strategy Consulting, Cloud Computing, Grid Computing, Enterprise Portal Architecture, Software Architecture, Application Framework Design and Development

CloudEXPO Stories
The Internet of Things will challenge the status quo of how IT and development organizations operate. Or will it? Certainly the fog layer of IoT requires special insights about data ontology, security and transactional integrity. But the developmental challenges are the same: People, Process and Platform and how we integrate our thinking to solve complicated problems. In his session at 19th Cloud Expo, Craig Sproule, CEO of Metavine, demonstrated how to move beyond today's coding paradigm and share the must-have mindsets for removing complexity from the development process, accelerate application delivery times, and ensure that developers will become heroes (not bottlenecks) in the IoT revolution.
CloudEXPO New York 2018, colocated with DXWorldEXPO New York 2018 will be held November 11-13, 2018, in New York City and will bring together Cloud Computing, FinTech and Blockchain, Digital Transformation, Big Data, Internet of Things, DevOps, AI, Machine Learning and WebRTC to one location.
The best way to leverage your Cloud Expo presence as a sponsor and exhibitor is to plan your news announcements around our events. The press covering Cloud Expo and @ThingsExpo will have access to these releases and will amplify your news announcements. More than two dozen Cloud companies either set deals at our shows or have announced their mergers and acquisitions at Cloud Expo. Product announcements during our show provide your company with the most reach through our targeted audiences.
What are the new priorities for the connected business? First: businesses need to think differently about the types of connections they will need to make – these span well beyond the traditional app to app into more modern forms of integration including SaaS integrations, mobile integrations, APIs, device integration and Big Data integration. It’s important these are unified together vs. doing them all piecemeal. Second, these types of connections need to be simple to design, adapt and configure. Plus, with the proliferation of IoT, there is an explosion in the number of devices requiring interconnection - both in terms of asset monitoring and spatial analytics.