#general (2024-05)
General conversations related to DevOps/Automation
General Discussions
2024-05-01
Hey everyone, give a warm welcome to our newest members!
- @Nidhin
- @sachin.chini
- @Prince Pathria
- @Dillon
- @fmera
- @Larry Warren
- @Pradeepvarma Senguttuvan
- @Thian
- @Noah Coker
- @smats004
Good to have you here =)
22024-05-02
Hey everyone, give a warm welcome to our newest members!
- @Meysam
- @Karthik
- @Nicolas
- @Emily Burak
Good to have you here =)
22024-05-03
Hey everyone, give a warm welcome to our newest members!
- @Duleendra Shashimal
- @dinodam
- @sergeyro
- @Rene Kuhn
- @Nate
Good to have you here =)
12024-05-04
Hey everyone, give a warm welcome to our newest members!
- @Vijay Dhama
Good to have you here =)
12024-05-05
Hey everyone, give a warm welcome to our newest members!
- @Zekeriya Sirin
Good to have you here =)
12024-05-06
Hey everyone, give a warm welcome to our newest members!
- @s_ellis
- @npcykgog0
- @Antonia
- @Vin
- @Eithan Reed
- @Jim Park
Good to have you here =)
212024-05-07
Hey everyone, give a warm welcome to our newest members!
- @Nasr Ladib
- @d_kim
- @Bartek Boniecki
Good to have you here =)
112024-05-08
Hi All,
Any ECS experts, I am trying to deploy an application with 12 different containers with some dependency on other containers, Also I want to create service for each containers. I am trying deploying with 2 approaches, but both having challenges.
1.If I go with individual Task Definitions(TD) - I can easily relate the TD to each service but challenge is I couldn’t configure the dependency to the other containers in other TD. 2.If I go with 1 TD for all containers, dependency is possible but I couldn’t create individual services for the containers, as service will look for TD.
Can someone give some suggestions? how can I proceed with this?
Tbh, I’d almost suggest going the EKS route instead for this. 12 containers seems excessive though. Perhaps you could condense things?
I couldn’t configure the dependency to the other containers in other TD.
This sounds like the fundamental problem.
“a tightly coupled distributed monolith”
The notion that one container cannot start with out the other container running is a liability for stability.
Hey everyone, give a warm welcome to our newest members!
- @Ray Finch
- @Joe Taylor
- @Adam
- @the arman
- @Jeff D
Good to have you here =)
112024-05-09
Hey everyone, give a warm welcome to our newest members!
- @Jacob Greenbow
- @Kaushik Santhanam
- @Fran
- @Tega McKinney
- @Alex T.
- @lunev432
- @gb12335
Good to have you here =)
312024-05-10
Hey everyone, give a warm welcome to our newest members!
- @Craig
Good to have you here =)
12024-05-12
Hey everyone, give a warm welcome to our newest members!
- @Hansel Christopher
- @georgiosd
- @Prabin
- @Morgan
Good to have you here =)
112024-05-13
Hey everyone, give a warm welcome to our newest members!
- @Peter
- @Sage
- @mo
- @wyntbrown
Good to have you here =)
212024-05-14
Hey everyone, give a warm welcome to our newest members!
- @Sean Patnode
- @srsharma
- @sijo.jose39
- @Alexander Pesetski
Good to have you here =)
2024-05-15
Hey everyone, give a warm welcome to our newest members!
- @Enrique Lopez
- @Prasanna
- @Borys Syczewski
- @Kamila Piech
- @Sergio
- @Jackie Virgo
Good to have you here =)
2024-05-16
trying to deploy privileged stack for AWS-Config, under superadmin role, got error:
Planning failed. Terraform encountered an error while generating this plan.
╷
│ Error: error configuring S3 Backend: IAM Role (arn:aws:iam::xxx:role/xx-core-gbl-root-tfstate-ro) cannot be assumed.
│
│ There are a number of possible causes of this - the most common are:
│ * The credentials used in order to assume the role are invalid
│ * The credentials do not have appropriate permission to assume the role
│ * The role ARN is not valid
│
│ Error: NoCredentialProviders: no valid providers in chain. Deprecated.
│ For verbose messaging see aws.Config.CredentialsChainVerboseErrors