AWS Fargate Obtainable in Asia Pacific (Hong Kong) Region

AWS Fargate is Amazon ECS compute engine which enables you to execute containers excluding the need to control servers or clusters. You do not have to provision, configure, and scale clusters of virtual machines to execute containers with AWS Fargate. This erase the necessity to select server types, determine when to scale your clusters, or optimize cluster packing. Also AWS Fargate discards the requirement for you to connect with or think about servers or clusters. AWS Fargate allows you concentrate on planning and creating your applications rather than handling the infrastructure which executes them. AWS Fargate smoothly integrates with Amazon ECS. You only describe your application like you do for Amazon ECS. Now this AWS Fargate is accessible in Hong Kong AWS Region of Asia Pacific. There are no upfront charges for AWS Fargate, you only charge for the resources which you utilize. To know the pricing details of AWS Fargate, refer Pricing Details. And to get the complete list of AWS Region wherer AWS Fargate is accessible, refer Region table.

Multiple Load Balancer Target Groups Service Supported By Amazon ECS

Amazon Elastic Container Service (Amazon ECS) is a highly scalable, fast, container management service which is simple to execute, stop, and handle Docker containers on a cluster. Amazon ECS allows you initiate and stop container-based applications with simple API calls, enables you to obtain the condition of your cluster from a centralized service, and provides you access to numerous Amazon EC2 features. Now you can connect many target groups to your Amazon ECS services which are executing on either Amazon EC2 or AWS Fargate. Target groups are utilized to route requests to one or more registered targets when utilizing a load balancer. Connecting numerous target groups to your service lets you to clarify infrastructure code, lessen costs and expand manageability of your ECS services. Earlier, you could join solely one target group to an Amazon ECS service. This indicated you had to produce many copies of the service for use cases like serving traffic from internal and external facing Application or Network load balancers and revealing different ports. With this feature, you can join numerous target groups per ECS service. Refer documentation to learn more about registering multiple target groups.

AWS Step Functions Allows Access to Workflow Metadata

AWS Step Functions lets you to add flexible workflow automation to your applications. The steps of your workflow can exist anywhere, covering in AWS Lambda functions, on Amazon EC2, or on-premises. Besides, AWS Step Functions is integrated with Amazon ECS, AWS Fargate, Amazon DynamoDB, Amazon SNS, Amazon SQS, AWS Batch, AWS Glue, and Amazon SageMaker. You can join and correlate all these services in minutes—without writing code. Now AWS Step Functions allows access to metadata about workflow executions so that you can directly find associated resources. For example, your workflow can fetch its execution ID or a timestamp showing when an activity began. This helps to connect logs for quick debugging and to calculate workflow performance data. Your workflows pass metadata to tasks by referencing a context object available with each workflow execution. To get entire list of regions refer AWS Regions where AWS Step Functions is available. To know further on Step Functions, visit AWS Step Functions Developer Guide. To know about accessing workflow metadata, refer the AWS Step Functions Context Object.

Now Splunk Log Driver Supported By AWS Fargate PV1.3

AWS Fargate is a compute engine for Amazon ECS which enables you to execute containers without needing to handle servers or clusters. You do not have to provision, configure, and scale clusters of VMs to execute containers with the AWS Fargate. AWS Fargate discards the requirement to select server types, consider when to scale your clusters, or optimize cluster packing. Besides, it also discards the requirement for you to link with or consider about servers or clusters. AWS Fargate allows you concentrate on designing and creating your applications rather than handling the infrastructure which executes them. Now you can utilize the Splunk log driver to transport container logs from AWS Fargate activities to a Splunk endpoint. By defining the endpoint and other log configuration at the time of authoring task definitions, you can incorporate logs created by containers working in Fargate to Splunk. Moreover, you can reference fragile data like the splunk-token as a reference to data saved in AWS Secretes Manager or AWS Systems Manager Parameter Store. To know further about passing fragile data to log driver configuration here and grasp more in the API Configuration documentation.