Skip to content
By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post
About re:Post

ECS TASK Timeout Error-Code Build-Fargate

0

I have been attempting to deploy an application in our production environment using Code Pipeline, but the deployment procedure fails with the following Error "The action failed because a job worker exceeded its time limit. If this is a custom action, make sure that the job worker is configured correctly." In our development environment the ECS containers are deployed without a problem. The differences between both environments are what SQL DBs are the containers supposed to connect to, and that the production is using a customer managed KMS key instead of the AWS managed KMS key. FYI, KMS permissions in IAM role have been checked. Someone please help

When reviewing the logs for the ECS task I noticed the following error/ warning:

    • "No XML encryptor configured. Key{......} may be persisted to storage in unencrypted form."
    • "Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed."
    • "warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]"
    • "info: Microsoft.Hosting.Lifetime[0]"
    • "Application is shutting down..."
Topics
ContainersSecurity, Identity, & ComplianceDeveloper Tools
Tags
AWS FargateAWS CodeDeployAWS Key Management ServiceAmazon Elastic Container Service
Language
English

asked 3 years ago625 views

1 Answer
0

To address these log messages and improve your application's security and data persistence, you can take the following steps:

Configure an XML encryptor: Implement an XML encryptor for the application's data protection. This will ensure that sensitive information, such as keys, is stored in an encrypted format. You can refer to the relevant documentation or code examples for your specific framework or library to configure the XML encryptor correctly.

Consider alternative key storage: Instead of relying on a directory within the container for key storage, consider using a more persistent and secure storage solution, such as a key management service or external storage like AWS Secrets Manager or Azure Key Vault. This will help ensure that protected data remains accessible even if the container is destroyed or restarted.

answered 3 years ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Relevant content