You need to add a tag with key `Name` to the cloud formation template.  Like this...

    &quot;ec2-instance&quot; : {
        &quot;Type&quot; : &quot;AWS::EC2::Instance&quot;,
        &quot;Properties&quot; : {
            &quot;ImageId&quot; : &quot;ami-0102022,
            &quot;SecurityGroupIds&quot; : [{ &quot;Ref&quot; : &quot;SecurityGroup&quot; }],
            &quot;SubnetId&quot; : { &quot;Ref&quot; : &quot;Subnet&quot; },
            &quot;InstanceType&quot; : &quot;m1.medium&quot;,
            &quot;Tags&quot; : [
                {&quot;Key&quot; : &quot;Name&quot;, &quot;Value&quot; : &quot;Instance name&quot;},
                {&quot;Key&quot; : &quot;Environment&quot;, &quot;Value&quot; : { &quot;Ref&quot; : &quot;Environment&quot; }},
                {&quot;Key&quot; : &quot;Owner&quot;, &quot;Value&quot; : { &quot;Ref&quot; : &quot;Owner&quot; }}
            ]
        }
    }

In my application I need to convert my arraylist to a string of an array. However, I am getting an error:

    ClassCastException: java.lang.Object[] cannot be cast to java.lang.String[] android


At the line with `listofurls` I am getting the error: `listofurls = (String[])image_urls.toArray();`

This is the full code:

    public class Test2 extends AsyncTask&lt;Void, Void, Void&gt; 
    {
      String[] listofurls ;
      private static final String url = &quot;http://www.tts.com/album_pro/array_to_encode&quot;;
      JSONParser jParser = new JSONParser();
      ArrayList&lt;String&gt; image_urls = new ArrayList&lt;String&gt;();
        
      protected void onPreExecute() {
        //Log.e(LOG_CLASS, &quot;in side assyntask&quot;);
      }
    
      protected Void doInBackground(Void... voids) {
        Log.v(&quot;Async&quot;,&quot;Async&quot;);
        JSONObject json = jParser.getJSONFromUrl(url);
    
        try {
          JSONObject seo = json.getJSONObject(&quot;SEO&quot;);
          JSONArray folio = seo.getJSONArray(&quot;Folio&quot;);
    			
          // JSONArray image_urls1 = new JSONArray();
          //String s1=seo.getString(&quot;Folio&quot;);
    
          for(int i=0;i&lt;folio.length();++i) {
            String m = folio.getString(i);
            Log.v(&quot;M&quot;+i,m);
            image_urls.add(m);
            Log(&quot;test-url&quot;+image_urls);
          }
        } catch(Exception e) {
          e.printStackTrace();
        }
            
        listofurls = (String[])image_urls.toArray();  //ERROR OCCURS HERE
    		            
        return null;
      }
      
      private void Log(String string) {
        Log.v(&quot;Test&quot;,string);
      }
    
      protected void onProgressUpdate(Integer... progress) { }
    
      protected void onPostExecute(Void result) {
        mAdapter = new ImagePagerAdapter(getSupportFragmentManager(),listofurls.length );
        mAdapter.setImageurls(listofurls);
        mPager.setAdapter(mAdapter);
      }

ClassCastException: java.lang.Object[] cannot be cast to java.lang.String[] android

    git filter-branch --env-filter &#39;
    export GIT_AUTHOR_EMAIL=&quot;foo@example.com&quot;
    export GIT_AUTHOR_NAME=&quot;foo&quot;&#39; -- commita..commitb

Results in `Which ref do you want to rewrite?`

So it seems that `filter-branch` doesn&#39;t allow you to &lt;s&gt;use range notation&lt;/s&gt; use a range between two arbitrary refs.

What is the most straight forward way of running a filter over a range of consecutive commits (somewhere within the history of a branch) if this approach isn&#39;t possible.

Running filter-branch over a range of commits

I have a template that works and generates a stack but I cannot find a property to set or something else that allows me to give a Name to the EC2 Instance I have created. When it is generated the Name is blank.

Name an EC2 Instance in the CloudFormation template?

<p>I have a template that works and generates a stack but I cannot find a property to set or something else that allows me to give a Name to the EC2 Instance I have created. When it is generated the Name is blank.</p>


I have an Amazon RDS instance. Freeable Memory has been declining since setup over 1-2 weeks, starting from 15GB of memory down to about 250MB. As it has dropped this low in the last days, it has started to resemble a sawtooth pattern where Freeable Memory drops to this range (250 - 350MB) and then goes back up agin to 500 - 600MB in a sawtooth pattern. 

There has not been any notable decline in application quality. However, I am worried that the DB will run out of memory and crash. 

Is there a danger that the RDS instance will run out of memory? Is there some setting or parameter I should be looking at to determine if the instance is set up correctly? What is causing this sawtooth pattern? 

![Freeable Memory Declining][1]


  [1]: http://i.stack.imgur.com/ZX71y.jpg

Amazon RDS running out of freeable memory. Should I be worried?

I am a newbie to us cloud hosting. I want to know which is better to start with, either Google app engine or Amazon web service.

My questions are:

 1. My application is based on java, Database is MySQL. Do they support this?
 2. What are the free offers from both of them and which one is better to start? 
 3. How easy would it be to migrate from one platform to another?
 4. Any good link for getting started with these service as I am a novice here.

Additionally, I&#39;d appreciate some good links for getting started with these services as I am a novice here, and a high level view on how this works.

Google app engine or amazon web services

At the end of last week I noticed a problem on one of my medium AWS instances where Nginx always returns a HTTP 499 response if a request takes more than 60 seconds.  The page being requested is a PHP script

I&#39;ve spent several days trying to find answers and have tried everything that I can find on the internet including several entries here on Stack Overflow, nothing works.

I&#39;ve tried modifying the PHP settings, PHP-FPM settings and Nginx settings. You can see a question I raised on the NginX forums on Friday (http://forum.nginx.org/read.php?9,237692) though that has received no response so I am hoping that I might be able to find an answer here before I am forced to moved back to Apache which I know just works.

This **is not** the same problem as the HTTP 500 errors reported in other entries.

I&#39;ve been able to replicate the problem with a fresh micro AWS instance of NginX using PHP 5.4.11.

To help anyone who wishes to see the problem in action I&#39;m going to take you through the set-up I ran for the latest Micro test server.

You&#39;ll need to launch a new AWS Micro instance (so it&#39;s free) using the AMI ami-c1aaabb5

This PasteBin entry has the complete set-up to run to mirror my test environment. You&#39;ll just need to change *example.com* within the NginX config at the end

http://pastebin.com/WQX4AqEU

Once that&#39;s set-up you just need to create the sample PHP file which I am testing with which is


    &lt;?php
    sleep(70);
    die( &#39;Hello World&#39; );
    ?&gt;

Save that into the webroot and then test.  If you run the script from the command line using php or php-cgi, it will work.  If you access the script via a webpage and tail the access log */var/log/nginx/example.access.log*, you will notice that you receive the HTTP 1.1 499 response after 60 seconds.

Now that you can see the timeout, I&#39;ll go through some of the config changes I&#39;ve made to both PHP and NginX to try to get around this.  For PHP I&#39;ll create several config files so that they can be easily disabled

**Update the PHP FPM Config to include external config files**

    sudo echo &#39;
    include=/usr/local/php/php-fpm.d/*.conf
    &#39; &gt;&gt; /usr/local/php/etc/php-fpm.conf

**Create  a new PHP-FPM config to override the request timeout**

    sudo echo &#39;[www]
    request_terminate_timeout = 120s
    request_slowlog_timeout = 60s
    slowlog = /var/log/php-fpm-slow.log &#39; &gt;
    /usr/local/php/php-fpm.d/timeouts.conf

**Change some of the global settings to ensure the emergency restart interval is 2 minutes**

    # Create a global tweaks
    sudo echo &#39;[global]
    error_log = /var/log/php-fpm.log
    emergency_restart_threshold = 10
    emergency_restart_interval = 2m
    process_control_timeout = 10s
    &#39; &gt; /usr/local/php/php-fpm.d/global-tweaks.conf

Next, we will change some of the PHP.INI settings, again using separate files

    # Log PHP Errors
    sudo echo &#39;[PHP]
    log_errors = on
    error_log = /var/log/php.log
    &#39; &gt; /usr/local/php/conf.d/errors.ini

    sudo echo &#39;[PHP]
    post_max_size=32M
    upload_max_filesize=32M
    max_execution_time = 360
    default_socket_timeout = 360
    mysql.connect_timeout = 360
    max_input_time = 360
    &#39; &gt; /usr/local/php/conf.d/filesize.ini

As you can see, this is increasing the socket timeout to 3 minutes and will help log errors.

Finally, I&#39;ll edit some of the NginX settings to increase the timeout&#39;s that side

First I edit the file */etc/nginx/nginx.conf* and add this to the http directive
    fastcgi_read_timeout 300;

Next, I edit the file */etc/nginx/sites-enabled/example* which we created earlier (See the pastebin entry) and add the following settings into the **server** directive

    client_max_body_size    200;
    client_header_timeout   360;
    client_body_timeout     360;
    fastcgi_read_timeout    360;
    keepalive_timeout       360;
    proxy_ignore_client_abort on;
    send_timeout            360;
    lingering_timeout       360;

Finally I add the following into the *location ~ \.php$* section of the server dir

	fastcgi_read_timeout 360;
	fastcgi_send_timeout 360;
	fastcgi_connect_timeout 1200;

Before retrying the script, start both nginx and php-fpm to ensure that the new settings have been picked up. I then try accessing the page and still receive the HTTP/1.1 499 entry within the NginX example.error.log.

So, where am I going wrong?  This just works on apache when I set PHP&#39;s max execution time to 2 minutes.

I can see that the PHP settings have been picked up by running **phpinfo()** from a web-accessible page.  I just don&#39;t get, I actually think that too much has been increased as it should just need PHP&#39;s *max_execution_time*, *default_socket_timeout* changed as well as NginX&#39;s *fastcgi_read_timeout* within just the server-&gt;location directive.

##Update 1##

Having performed some further test to show that the problem is not that the client is dying I have modified the test file to be

    &lt;?php
    file_put_contents(&#39;/www/log.log&#39;, &#39;My first data&#39;);
    sleep(70);
    file_put_contents(&#39;/www/log.log&#39;,&#39;The sleep has passed&#39;);
    die(&#39;Hello World after sleep&#39;);
    ?&gt;

If I run the script from a web page then I can see the content of the file be set to the first string. 60 seconds later the error appears in the NginX log. 10 seconds later the  contents of the file changes to the 2nd string, proving that PHP is completing the process.

##Update 2##
Setting **fastcgi_ignore_client_abort on;** does change the response from a HTTP 499 to a HTTP 200 though nothing is still returned to the end client.

##Update 3##
Having installed Apache and PHP (5.3.10) onto the box straight (using apt) and then increasing the execution time the problem does appear to also happen on Apache as well.  The symptoms are the same as NginX now, a HTTP200 response but the actual client connection times out before hand.

I&#39;ve also started to notice, in the NginX logs, that if I test using Firefox, it makes a double request (like this https://stackoverflow.com/questions/13261327/php-script-executes-twice-when-longer-than-60-seconds). Though that does appear to be the client requesting upon the script failing


NginX issues HTTP 499 error after 60 seconds despite config. (PHP and AWS)

While creating a new AWS EC2 instance using the EC2 command line API, I passed some user data to the new instance.

How can I know whether that user data executed or not?



How to check whether my user data passing to EC2 instance is working

I am using AWS ec2 instance.  On this instance I&#39;m resulting some files. These operations are done by user data.

Now I want to store those files on s3 by writing code in user data itself.

- So how can I store those files on s3?
- Have any tutorials on it?

How to transfer files between AWS s3 and AWS ec2

I have an EC2 instance running and I am able to SSH into it. 

However, when I try to rsync, it gives me the error Permission denied (publickey). 

The command I&#39;m using is: 

    rsync -avL --progress -e ssh -i ~/mykeypair.pem ~/Sites/my_site/* root@ec2-XX-XXX-XXX-XXX.us-west-2.compute.amazonaws.com:/var/www/html/

I also tried

    rsync -avz ~/Sites/mysite/* -e &quot;ssh -i ~/.ssh/id_rsa.pub&quot; root@ec2-XX-XXX-XXX-XXX.us-west-2.compute.amazonaws.com:/var/www/html/



Thanks,


Rsync to Amazon Ec2 Instance

I have created an AWS EC2 Instance and I want to be able to upload files to the server directory using FileZilla in the simplest and most straightforward fashion possible. 

Connect to Amazon EC2 file directory using Filezilla and SFTP

From EC2 instance i-78a8df00, I&#39;m trying to connect to RDS instance mysql.************.us-east-1.rds.amazonaws.com. They are both in the U.S. East region. I added the security group of EC2 instance (sg-********) to the RDS security group, but that didn&#39;t help. It appears to be a firewall/DNS issue as it is timing out when running this command:

    ubuntu@ip-10-195-189-237:~$ mysql -h mysql.************.us-east-1.rds.amazonaws.com
&gt; ERROR 2003 (HY000): Can&#39;t connect to MySQL server on &#39;mysql.************.us-east-1.rds.amazonaws.com&#39; (110)

I can connect to RDS instance fine from my local machine using the same line as above. I tried various forum solutions but those don&#39;t help.

Can&#39;t connect to RDS instance from EC2 instance

I would like to know what are the advantages and disadvantages of using AWS OpsWorks vs AWS Beanstalk and AWS CloudFormation?

I am interested in a system that can be auto scaled to handle any high number of simultaneous web requests (From 1000 requests per minute to 10 million rpm.), including a database layer that can be auto scalable as well.

Instead of having a separate instance for each app, Ideally I would like to share some hardware resources efficiently. In the past I have used mostly an EC2 instance + RDS + Cloudfront + S3

The stack system will host some high traffic ruby on rails apps that we are migrating from Heroku, also some python/django apps and some PHP apps as well.

Thanks in advance.

AWS OpsWorks vs AWS Beanstalk vs AWS CloudFormation?

I&#39;m trying out [Serverless][1] to create AWS Lambdas and while creating a project using the command `serverless project create` I&#39;m getting the following error.

    AccessDenied: User: arn:aws:iam::XXXXXXXXX:user/XXXXXXXXX is not authorized to perform: cloudformation:CreateStack on resource: arn:aws:cloudformation:us-east-1:XXXXXXXXX:stack/XXXXXXXXX-development-r/*

I have created a user and granted the following permissions to the user. 

 1. AWSLambdaFullAccess
 2. AmazonS3FullAccess
 3. CloudFrontFullAccess
 4. AWSCloudFormationReadOnlyAccess ( There was no `AWSCloudFormationFullAccess` to grant )

How can I proceed? What else permissions I have to grant? 

  [1]: http://serverless.com

User is not authorized to perform: cloudformation:CreateStack

Here&#39;s (the DynamoDB part of) my Troposphere-generated JSON:

    &quot;sandbox&quot;: {
            &quot;Properties&quot;: {
                &quot;AttributeDefinitions&quot;: [
                    {
                        &quot;AttributeName&quot;: &quot;audit_id&quot;,
                        &quot;AttributeType&quot;: &quot;S&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;status&quot;,
                        &quot;AttributeType&quot;: &quot;S&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;filename&quot;,
                        &quot;AttributeType&quot;: &quot;S&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;file_detected_dt&quot;,
                        &quot;AttributeType&quot;: &quot;S&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;time_taken&quot;,
                        &quot;AttributeType&quot;: &quot;N&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;number_rows_processed_file&quot;,
                        &quot;AttributeType&quot;: &quot;N&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;number_rows_created_db&quot;,
                        &quot;AttributeType&quot;: &quot;N&quot;
                    },
                    {
                        &quot;AttributeName&quot;: &quot;info_messages&quot;,
                        &quot;AttributeType&quot;: &quot;S&quot;
                    }
                ],
                &quot;KeySchema&quot;: [
                    {
                        &quot;AttributeName&quot;: &quot;audit_id&quot;,
                        &quot;KeyType&quot;: &quot;HASH&quot;
                    }
                ],
                &quot;ProvisionedThroughput&quot;: {
                    &quot;ReadCapacityUnits&quot;: {
                        &quot;Ref&quot;: &quot;ReadCapacityUnits&quot;
                    },
                    &quot;WriteCapacityUnits&quot;: {
                        &quot;Ref&quot;: &quot;WriteCapacityUnits&quot;
                    }
                }
            },
            &quot;Type&quot;: &quot;AWS::DynamoDB::Table&quot;
        }

CloudFormation gives me this error on trying to spin up the VPC:  `Property AttributeDefinitions is inconsistent with the KeySchema of the table and the secondary indexes`.

But ... is it? I&#39;m specifying `audit_id` as a lone key, and it definitely exists within the AttributeDefinitions list. I&#39;m very new to CF (and Dynamo, for that matter) so I may well be missing something extremely obvious, but it&#39;s not apparent to me at the moment.

I&#39;ve googled around and only really found one mention of this error, and it was more to do with a layer between developer and CF, rather than CF itself.

Can anyone point out what&#39;s wrong with my template?

CloudFormation insists my DynamoDB creation JSON is invalid .. but I can&#39;t see how

Is there a way to specify the CloudWatch log group that an AWS lambda logs to?  It seems to be generated directly from the lambda name; however, it would be especially convenient to, for example, aggregate multiple lambdas to a single log group.  We are especially interested in specifying the log group when the lambda is created by a CloudFormation template.

Specify log group for an AWS lambda?

When creating a stack with CloudFormation, I get this error:

&gt; Stack update error: Requires capabilities : [CAPABILITY_IAM]

I can&#39;t find a template for adding `CAPABILITIES_IAM` to the CloudFormation configuration.

What are the options for resolving `CAPABILITIES_IAM` errors?

Content Type	Original Author	Original Content on Stackoverflow
Question	A.G.	View Question on Stackoverflow
Solution 1 - Amazon Web-Services	Pete - MSFT	View Answer on Stackoverflow

Name an EC2 Instance in the CloudFormation template?

Amazon Web-Services Problem Overview

Amazon Web-Services Solutions

Solution 1 - Amazon Web-Services

Running filter-branch over a range of commits

ClassCastException: java.lang.Object[] cannot be cast to java.lang.String[] android

Attributions