Skip to content

Conversation

@MiroDojkic
Copy link
Member

  • refactor of the ECS service
  • enable multiple container definitions
  • enable multiple port mappings
  • provide volume separately from container's mount points - instead of providing persistentStorageConfig

@MiroDojkic MiroDojkic force-pushed the feature/multi-container-ecs branch 4 times, most recently from 4e0f2d2 to 5c09b05 Compare April 7, 2025 11:49
const logGroup = new aws.cloudwatch.LogGroup(
`${this.name}-log-group`,
{
retentionInDays: 14,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this hardcoded? Shouldn't this be indefinite (which is set by default) for the production env?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good question. This was inherited from the original service.
I don't think we should have it infinite though, as it impact storage cost and the risk of retaining sensitive information too long.

I suggest we make this configurable with options for staging and prod environments, as we did with sizes, in a separate PR - for example 3, 14, and 90 days.

@MiroDojkic MiroDojkic force-pushed the feature/multi-container-ecs branch from f2eacef to 1c033c3 Compare April 7, 2025 16:19
@droguljic droguljic merged commit 28cf69b into master Apr 7, 2025
1 check passed
@droguljic droguljic deleted the feature/multi-container-ecs branch April 7, 2025 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants