#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
- @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 =)
12024-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 =)
12024-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
Hey @Alex this is the general channel. Looks like you’re using our reference architecture (based on the state backend name). Best to use refarch
Hey everyone, give a warm welcome to our newest members!
- @Alex
- @Andrea Cavagna
- @jacob673
Good to have you here =)
2024-05-17
Hey everyone, give a warm welcome to our newest members!
- @vishal.devops31
- @kvapss
Good to have you here =)
22024-05-18
Hey everyone, give a warm welcome to our newest members!
- @donovan734
Good to have you here =)
2024-05-19
Hey everyone, give a warm welcome to our newest members!
- @Jay Prasad
Good to have you here =)
2024-05-20
Hi - I’m working on a project to evaluate IaC alternatives to Terraform. We need to be multi cloud and want for developers to be able to create their own infra as much as possible. Would you know a good resource that compares several multicloud alternatives? I personally know of Pulumi and Terraform and not many more that aim at our stack opf multicloud kubernetes deployments (so basically network setup, whatever kubernetes setup exists on the cloud and other storage or event stuff like databases, queues, etc.)
Can you suggest alternatives to Pulumi and Terraform for our use cases, some good resources (most “compare X to Y articles on the web suck big time”) , or some comparison matrix between this type of IaC?
Something like https://www.crossplane.io/ ? and\or https://cluster-api.sigs.k8s.io/user/quick-start.html for cluster management
But terraform is popular for a reason - big community, lots of modules.
Pulumi is nice as a concept - but when you let developers create their own infra, you will end up with lots of semi-built infra implementations. And then someone will have to manage them 0/10, not recommended…
thanks
“multicloud” is implementation myth. there is no solution to abstract away details of several cloud providers. you always have to develop things with constraints and features of each provider. there won’t be a parity
2024-05-21
Hey everyone, give a warm welcome to our newest members!
- @andrew.nemiroff
- @Enrique Lopez
Good to have you here =)
12024-05-22
Hey everyone, give a warm welcome to our newest members!
- @Luke Hsiao
- @Mehak
- @Mitchell
- @Christof Bruyland
- @pom
- @Jack Hwang
- @Angie Brandt
Good to have you here =)
12024-05-23
This message was deleted.
Hey everyone, give a warm welcome to our newest members!
- @Amaresh Ray
- @veer
- @Viktor Ek
Good to have you here =)
12024-05-24
Hey everyone, give a warm welcome to our newest members!
- @ksushants
- @sharma.mohit332
- @Prabhu
- @calinflorescu3
- @Chris Schagen
- @theherk
Good to have you here =)
12024-05-25
What does everybody do on their commute to work? What have you tried (or not) to make it productive? (I’m most interested in driving vs public transit.)
Audiobooks (or podcasts when I am not in the mood for a business book). My biggest regret is not starting that when I was younger. I started listening in my 30s, way too late and it would have accelerated everything in my career and business.
Hey everyone, give a warm welcome to our newest members!
- @morguldir
- @Jascha
- @andrewadev
- @davidhankinson
- @Dmitry
Good to have you here =)
32024-05-26
Hey everyone, give a warm welcome to our newest members!
- @davidhankinson
- @abhimalik7196
- @harshwardhan.choudhar
- @sstewart
Good to have you here =)
5
Is https://github.com/cloudposse/lambdas-ssm-sync still necessary for cross account syncing of ssm parame even tho aws can natively share ssm params via ram share ?
@Matt Calhoun
2024-05-27
Hey everyone, give a warm welcome to our newest members!
- @shijesh87
- @oliver.wiegers
Good to have you here =)
12024-05-28
Hey everyone, give a warm welcome to our newest members!
- @Olivier Martinez
- @Eligio Mariño
- @marckhair
- @rodstewart
- @Narayanaperumal Gurusamy
Good to have you here =)
312024-05-29
Hey everyone, give a warm welcome to our newest members!
- @Sumeet
Good to have you here =)
212024-05-30
Hey everyone, give a warm welcome to our newest members!
- @shayyanmalik13
- @shashanklmur
- @Sairam
Good to have you here =)
212024-05-31
Oh, hello!
Hey everyone, give a warm welcome to our newest members!
- @Nathan Joshi
Good to have you here =)
21