Change instance type aws,resize ec2-instance

Please find below steps to “Change instance type aws,resize ec2-instance

  1. Login into AWS console.
  2. Go to EC2 Dashboard -> Instances.
  3. Select Instance which is you need to change type or size.
  4. Select Actions -> Instance State -> Stop.
  5. It will give one popup window “Stop Instance” like “Are you sure you want stop these Instance?”. Click on “Yes, Stop“.
  6.  When instance stoped Public DNS, Public DNS set to empty.
  7. Next go to Actions -> Instance Settings -> Change Instance Type -> Select instance type like example “m3-medium“.
  8. Next Select Actions -> Instance State -> Start.
  9. After change Instance Type -> Public DNS, Public DNS changed to new.

Find video here


AWS EC2 server connect through filezilla

Please find below steps to connect “AWS EC2 server connect through filezilla”.

  1. Download “PPK file” from AWS ec2 server. (AWS allow only once allowed to download PPK file)
  2. Copy public url from ec2 instance like this “ec2-**-**-***-***.*********”.
  3. Open filezilla go to “Edit” -> “Settings” -> select connection type “SFTP” and the add downloaded PPK file here.
  4. Next go to “File” -> “Site Manager” -> create new site.
  5. Paste Host with copied url from ec2 from 2nd step.
  6. Select Protocol “SFTP-SSH File Transfer Protoaol” and Logon Type is “ASK for Password” after the paste user name that will get from AWS ec2 server.
  7. Final step is click on connect it will ask “Password”.

Domain name setup to aws hosting

Please follow steps below specified….

  1. AWS services  ->  Route 53  -> Hosted zones.
  2. Click on “Create Hosted Zone” fill domain name with “Public hosted zone”.
  3. Copy NS records from Route 53.
  4. Login into domain registration like Godaddy  ->  Name servers  ->  Add NS records which are copied from Route 53.
  5. AWS services  ->  Route 53  -> Hosted zones.
  6. Select created hosted zone.  ->  Create Record Set  ->  Name with “www” and value with public IP which is founded in ec2 instance.
  7. It’s will take time to propagate wait some time and then check domain name.

Successful Upload to S3 but error on /system/ajax

I’m trying to use S3 CORS for my project and I’m encountering the error below:

An AJAX HTTP request terminated abnormally.
Debugging information follows.
Pagh: /system/ajax
StatusTest: n/a
Error message
Warning: filesize(): stat failed for s3://file-name.txt in file_save() (line 605 of /srv/bindings/ 8583c5f5083a475a9d644d64d843b077/code/includes/
PDOException: SQLSTATE[2300]: Integrity constraint violation: 1062 Duplicate entry ‘s3://file-name.txt’ for key ‘uri’: INSERT INTO {file_managed} (uid, filename, uri, filemie, filesize, status, timestamp, type) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_4, :db_insert_placeholder_5, :db_insert_placeholder_6, :db_insert_placeholder_7); Array(
[:db_insert_placeholder_0] = > 1
[:db_insert_placeholder_1] = > file-name.txt
[:db_insert_placeholder_2] = > s3://file-name.txt
[:db_insert_placeholder_3] = > text/plain
[:db_insert_placeholder_4] = > 0
[:db_insert_placeholder_5] = > 0
[:db_insert_placeholder_6] = > 1398930781
[:db_insert_placeholder_7] = > default
in drupal_write_record() (line 7211 of /srv/bindings/8583c5f5083a475a9d644d64d843b077/code/includes/

The website encountered an unexpected error. Please try again later.


Ready State: undefined


Below provided some of alternatives to check this error.

1. Insert the same filename into multiple times.
2. Cause of this issue can be having multiple CORS3 Upload fields on a single form.


Getting AWS Access Key ID and Secret Access Key

AWS(Amazon Web Services)

  1. Open the IAM console.
  2. From the navigation menu, click Users.
  3. Select your IAM user name.
  4. Click User Actions, and then click Manage Access Keys.
  5. Click Create Access Key.Your keys will look something like this:
    • Access key ID example: AKIAIOSFODNN7EXAMPLE

    • Secret access key example: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY

  6. Click Download Credentials, and store the keys in a secure location.Your secret key will no longer be available through the AWS Management Console; you will have the only copy. Keep it confidential in order to protect your account, and never email it. Do not share it outside your organization, even if an inquiry appears to come from AWS or No one who legitimately represents Amazon will ever ask you for your secret key.