fargate-service | new book Rapid Docker on AWS Written for DevOps | Continuous Deployment library

I've got an existing FargateCluster with a running service and a running task definition created by the great aws-cdk.

I wonder what is the best way to deploy a new docker image to this existing Fargate-Service within a seperate AWS CDK routine/script/class? The docker image gets a new version (not latest) and I like to keep all the parameters configured in the existing task-definition and just deploy the new docker image. What I like to do in detail is geting the existing task-definition and just change the name of the image and let Fargate deploy it.

Is there any working example for this?

Any help will be appreciated.....

Regards

Christian

I have deployed the docker image of my spring boot application over aws ECR, following creation of AWS fargate cluster. PFA screenshots of the configurations stating task, security, service and cluster definition.I can ping my public ip successfully. But I can't access my application over neither load balancer nor public ip. The urls I tried to access application were

public_ip:8081/my_rest_end_point

and

load_balancer_public_dns:8081/my_reset_end_point

I have tested running my docker image on local host using port 8081 and the same 8081 port I have configured for port mapping in my Fargate container configuration (reference: service definition). How can I access my application? I have followed almost all the articles over Medium and AWS.

Tutorials followed: https://medium.com/underscoretec/deploy-your-own-custom-docker-image-on-amazon-ecs-b1584e62484

https://medium.com/faun/aws-fargate-services-deployment-with-continuous-delivery-pipeline-b67d33407c88

I'm having trouble creating a dynamic block in Terraform. I'm trying to create an ECS service using a module. In the module I want to specify that network_configuration block should be created only if a variable is present. Here's my module code:

I'd like to use Fargate to run two containers - one for the main project's backend, and another for the database (MongoDB). The basic example included in the GitHub repo shows how to run a single container on Fargate using CDK, however I still have 2 issues:

1. The example doesn't show how to run two containers.
2. I'd like to scale the database containers but have them share the data storage (so that the data gets stored in a central place and stays synchronized between the different containers).

I've figured out how to (sort of) fixed the first issue, similarly to how ecs.LoadBalancedFargateService is implemented, however the second issue still remains.

For reference, this is what I have so far in stack.ts (the rest is the basic boilerplate cdk init app --language typescript generates for you):

The documentation for ServiceDiscovery::PrivateDnsNamespace states that:

When you create a private DNS namespace, AWS Cloud Map automatically creates an Amazon Route 53 private hosted zone that has the same name as the namespace.

In CloudFormation, is there any way to access the created HostedZone (as a Route53::HostedZone) so I can add additional Route53:RecordSets to it?

• Is the ID the same?
• Can I include a Route53::HostedZone with the same name to get the right ID?
• Is there some other trick?

For example, I'd like to expose my RDS and ElastiCache (Redis) instance at private DNS entries. I realize this could be the XY problem, but I'm accessing these systems at standard locations in my legacy code and am trying minimize the customization (and thus potential bugs) in my first ECS attempt.

WARNING: While AWS Service Discovery strategies can be used to expose services like DB and RDS, there are several qualifications:

• AWS Service Discovery requires the syntax . so you can't simply expose the services at db and redis. Your best odds for a 'standard' domain is something like redis.local and db.local. While local is a reserved TLD, there's some hostility to its use.
• RDS SSL certificates are tied to the RDS domain name and custom SSL certificates are not supported so you can't expose it at db..com. If you don't use the RDS CNAME, you won't be able to connect to these instances over trusted SSL connection.