83bytes
u/83bytes
The folks at Last9 have built a microsite to explain High Cardinality in layperson terms. They've taken the example of a bookshelf to showcase it, and it looks really cool, if i say so myself. (ps. I work at last9)
highcardinality.com/Catch Nishant Modak (CEO, Last9) quiz Ashutosh Agarwal (Chief Software Architect, JioCinema)
- What do #DevOps/#SREs do to prepare for massive events such as the IPL?
- How do engineering teams collaborate?
- What kind of edge cases do teams witness at scale?
This is an online event on Zoom.
Time: Feb 21, 2024; 9 PM IST / 11 AM EST
disclosure: I work at Last9 (SRE)
Hello,
I am trying to add some new cheatsheets to DDG.
I looked this up online and was pointed to an archived github repo (https://github.com/duckduckgo/zeroclickinfo-goodies/tree/master/share/goodie/cheat_sheets/json)
Also this cheat-sheet-reference is there (https://github.com/duckduckgo/duckduckhack-docs/blob/master/frontend-reference/cheat-sheet-reference.md)
Can anyone please point me to a source where I can read more about this topic ?
Thank You.
some more info.
I live in the Kothrud area. Im looking to rent 2-wheelers for some short trips on the weekends!
Any service/store nearby ?
I am reading about linux namespaces and how containers are built and I could not understand this part.
This is the setup
- The Host (H) has 0-65536 ports available.
- When I make a connection from this box to a server, the server sees the
host-ip:host:portof the host. - There are 2 containers running in the host
- Network mode is
bridge - Each of these containers have 0-65536 ports available each (since they are namespaced; essentially running completely isolated TCP stacks) (right ??)
- When I make an outbound connection to a server (A), then 'A' sees the
host-ip:host:port(this is because the interfaces in the container are attached to the docker bridge and are behind a NA
I am trying to generate IAM roles for my task definition from a CloudFormation Template.
In the CF template I have a "Fn::Join:" that joins different fields (like zone and AccountID) together to form the arn.
It looks like this.
Resource:
- Fn::Join:
- ''
- - 'arn:aws:dynamodb:'
- Ref: 'AWS::Region'
- ':'
- Ref: 'AWS::AccountId'
- ':table/'
- "table_name"
This part works.
However, when I try to replace the "join" with a "Fn::Sub:" I get a "legacy parse error"
Resource:
- !Sub 'arn:aws:dynamodb:${AWS::Region}:{AWS::AccountId}:table/table_name'
The Version for the PolicyDocument that I am using is `*2012-10-17`
I have a ECS task that needs to access resources in another aws account.
My ECS tasks are running in Account A and the resources that I need to access are in account B.
For this I have created a role in account B with necessary permission to the required resources and I have added a trust relationship with account A as well.
Now in account A where ECS is running I have added sts:AssumeRole to the Remote IAM role in account B.
This however is not working. My ECS task is still not being able to access resourcecs in account B.
How do i set up cross-account IAM roles/policies that work with ECS Task.



