aws-samples / java-spring-boot-ecs-fargate-redis-caching Goto Github PK

Within the file java-spring-boot-ecs-fargate-redis-caching/cfn/applications/java-spring-boot-service.yaml there is a resource named AutoScalingTarget of type AWS::ApplicationAutoScaling::ScalableTarget. At issue here are two things:

1. A AWS provided IAM Managed Policy with the ARN arn:aws:iam::aws:policy/aws-service-role/AWSApplicationAutoscalingECSServicePolicy already exists.
2. The particular policy referenced above includes one permission (cloudwatch:DeleteAlarm) that the existing policy used in the document does not include.

I would suggest modifying the AWS::IAM::Role resource as follows:

AutoScalingRole:
  Type: AWS::IAM::Role
  Properties:
    RoleName: !Join ['', [ !Sub "${AWS::StackName}-${ServiceName}", AutoScalingRole]]
    AssumeRolePolicyDocument:
      Statement:
        - Effect: Allow
          Principal:
            Service: application-autoscaling.amazonaws.com
          Action: sts:AssumeRole
    ManagedPolicyArns:
      - arn:aws:iam::aws:policy/aws-service-role/AWSApplicationAutoscalingECSServicePolicy

Could you provide some explanation on the differences in running Redis on Fargate as in this example, or using the same Spring Boot application with ElastiCache (AWS-managed Redis)? Is there any documentation on this, or articles discussing the benefits and tradeoffs?

Actually I'm a bit confused whether this example is showing running Redis in Fargate or via ElastiCache. There is a CloudFormation template for ElastiCache, but the fargate_metadata.json seems to refer to Redis as a Fargate image.

Could you give an explanation on which approach this example uses to access Redis, and what factors should be considered when choosing between Redis on Fargate vs ElastiCache?