Skip to main content

Deploy Rails Application on Amazon Elastic Bean

First Sign into the consle of the Amazon Web Services (AWS) and 

In the Navigation pane Select ElasticBean

Click on Applications and then on the Create Applicataion button and 

Name the appliation and click on Create

The will create the Application 

Now you need to Create the environment.

You need to select the Ruby version. I selected 2.6

It is must same as the the Ruby version in your local and the Ruby version on the AWS must be same otherwise it will fail while deploying

Also you need check the puma version it must also be that of the AWS.

 The PUma version is mentioned in the GEM file of the Rails app.

. Leave the rest and now click on Create 

Deploying the Application.


Go to your Local folder of the Rails project and run eb init on the root of the app. This will create ebbeanstalk environment folder 

You will be prompted to use Code Commit Choose Yes

Then run git add 

Then you will be prompted to create a repo . Create a new one 
Then select the master branch as shown in the instructions

Now run  git commit -m "First Commit"
At last run git push origin master.


select After the code is pushed run eb deploy. 

That's it your App will be deployed.

Comments

Popular posts from this blog

Facebook Bug Bounty $$$$ : Crossposting Live Videos | Facebook Live

In the Facebook Page Settings, you could setup the option for Crossposting Live videos from other pages.  The Attacker's page adds a Page (Victim's Page) for crossposting their videos Victim Page's Admin accepts the approval and the default option is Crossposting videos without further approval The Attacker starts live video and selects Victim's Page in the "Crosspost to more pages" Victim visits the Crossposting page in the Page settings and and removes Attacker's Page Attacker selects "Use camera" and clicks on "Go Live". The Victim's Page starts automatically crossposting the live video of Attacker,  Bug Bounty of $500

$1337 YouTube Community (Posts) bug

YouTube Community  is a feature that is only available for Channels with  1. Verified Phone numbers 2.  A significant history, more content for years. In the early June I started hunting for Security flaws on YouTube I was roaming around the features but most of the places have been found secure or already potential features had the bugs fixes in place. The Community Tab is now Posts So, I thought to exploit Youtube Community feature. I was trying to delete the Posts using IDOR attacks but it didn't work I was tired of trying various attacks but thought to compromise to the least "Privilege escalation".  The Security flaw... A user (victim) created a YT Community post, later an attacker while being an Admin of the same Channel has saved the HTTP Request that deletes a Community Post / Poll, then the attacker can replay that HTTP Request after he's demoted from Admin to Subtitle Editor  that would delete the Post / Poll. I exploited this flaw I tried after 15 ...

Google form setting Bypass - Making my way to the Google's Hall of Fame !

  G o o g l e ! Bug : Circumventing "Limit to 1 response" of  Google forms  ( Parameter Injection )        Discovered on: 30th, November 2016.            Research Time: 2:00 p.m to 9:30 p.m. Earn more by display ads on blog with  Lithific Ads The setting is "Limit to 1 response" which means only one response per user. Once you filled the form there will be no chance to edit the responses or again fill a new form. If you open the form to fill again, the response would be like the image below. There is no way to edit or fill another form (Hurdle 1). I created a test form and checked "Edit after submit". Once this test form is filled I can change the previous response.  I clicked on the "Edit your  response"and intercepted the request.  I changed the form id and forwarded the request. I was able to see the form that was submitted. When I edited the form and submitted, a blank form ...