Skip to Content.
Sympa Menu

per-entity - Re: [Per-Entity] A little MDQ mvp in AWS

Subject: Per-Entity Metadata Working Group

List archive

Re: [Per-Entity] A little MDQ mvp in AWS


Chronological Thread 
  • From: Christopher Hubing <>
  • To: Tom Scavo <>
  • Cc: Per-Entity Metadata Working Group <>
  • Subject: Re: [Per-Entity] A little MDQ mvp in AWS
  • Date: Fri, 14 Oct 2016 15:48:44 +0000
  • Authentication-results: spf=none (sender IP is ) ;
  • Ironport-phdr: 9a23:l/0s6BG6MG0+X69kPWJbDJ1GYnF86YWxBRYc798ds5kLTJ75p8iwAkXT6L1XgUPTWs2DsrQf1LqQ7vurADFIyK3CmU5BWaQEbwUCh8QSkl5oK+++Imq/EsTXaTcnFt9JTl5v8iLzG0FUHMHjew+a+SXqvnY6Uy/yPgttJ+nzBpWaz4Huj7jzqNXvZFB0gz/1Wrh7MhL++RnLrcIfn4xKK6AtxwHPr2cSPela2DU7C0iUmkPX5t2x54Jk6yRdoboB6sRBV6qyK684ULZZCjsOMmYp6dftuAWZCwaD+y1PAS0tjhNUDl2dv1nBVZDrv36/77Il1Q==
  • Spamdiagnosticmetadata: NSPM
  • Spamdiagnosticoutput: 1:99



On Thu, 13 Oct 2016, Tom Scavo wrote:

that would push these signed entity descriptors out. Right now, this just
grabs the aggregate from
http://md.incommon.org/InCommon/InCommon-metadata.xml and pushes it into
DynamoDB.

Right, let me explain a bit more. The MDQ server doesn't do anything
except serve static files according to the spec (which is pretty much
what Scott was saying). Ops will sign the metadata on current
infrastructure and push the signed files to the MDQ server. In your
case, it seems the files need to be pushed directly into DynamoDB. Can
that be done remotely?

Yep, that can be done in a couple different ways depending on how best it would integrate with the new process. But, easily doable I think.

And, an IAM policy could be created for that process that would only allow it to modify that specific table.

e.g.:

{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"dynamodb:PutItem",
"dynamodb:Scan",
"dynamodb:Query",
"dynamodb:GetItem",
"dynamodb:DeleteItem"
],
"Effect": "Allow",
"Resource":
"arn:aws:dynamodb:us-east-1::table/mdq"
}
]
}




Tom




Archive powered by MHonArc 2.6.19.

Top of Page