Questions[amazon-elasticache](server)

We started an AWS Elasticache instance on a cache.t2.micro instance. How many connections will it accept?

I have been reading up on Redis with AWS Elasticache and am a little confused on security. So far, it seems the only security is to create a Redis Security Group that only allows access from either a specific security group or IP address.

Is there any additional security I can/should add?

Is there any way to attatch Redis access security to IAM Roles?

I have a cloud formation script shown below, I hope to create a Security Group and Elasti Cache. However I get an error shown below CREATE_FAILED AWS::ElastiCache::CacheCluster CacheSecurityGroup not found: elasticacheta....

I use cloudformation routinely but never with the cache. I do not want to use a VPC in my scenario and have gone through the documentation http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-elasticache-cache-cluster.html and related links but with no luck - help appreciated.

AWSTemplateFormatVersion: '2010-09-09'
Resources:
  ElasticacheSecurityGroup:
    Type: AWS::EC2::SecurityGroup
    Properties:
      GroupDescription: "Access from webservers only"
      SecurityGroupIngress:
      - IpProtocol: tcp
        CidrIp: 0.0.0.0/0
        FromPort: '11211'
        ToPort: '11211'
  ElasticacheCluster:
    Type: "AWS::ElastiCache::CacheCluster"
    DependsOn: ElasticacheSecurityGroup
    Properties:
      AutoMinorVersionUpgrade: "true"
      Engine: "memcached"
      CacheNodeType: "cache.t1.micro"
      NumCacheNodes: "1"
      CacheSecurityGroupNames:
      - Ref: ElasticacheSecurityGroup

I'm trying to write a CloudFormation template that subscribes a Lambda function to a CloudWatch Logs LogGroup. This Lambda function should then parse the logs and put them in to an Amazon ES cluster.

The subscription etc. is all working nicely, but the one bit I can't get my head around is how to pass in the Amazon ES cluster endpoint to the Lambda function. The template that AWS provides when you walk through the console includes a line:

var endpoint = 'my-aws-es-endpoint.amazonaws.com';

I'll obviously need to update this each time the CloudFormation template runs, as each time I'll get a different cluster with a different end point. I don't want to manually update this, but want to be able to use CloudFormation functions like 'Fn::GetAtt' to get the end point and pass it in to Lambda. I just can't figure out how.

I am using AWS Elastic Beanstalk, it is easy to start with deploying Java based web app, which is great.

However, I want to install Memcached on every instance locally so they can be used for caching, but seems it validated the principle of Elastic Beanstalk?

Is it possible to deploy memcached locally and automatically, together with Elastic Beanstalk's auto scale feature?

(I know I can use Elastic Cache but want to save some money but still take the advantage of auto scaling)

Thanks.