Why AWS SQS and SNS policies require “ID” element?
The AWS documentation just mentions it is required and be unique, but doesn't explain beyond that.
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_id.html
amazon-web-services amazon-sqs amazon-sns
add a comment |
The AWS documentation just mentions it is required and be unique, but doesn't explain beyond that.
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_id.html
amazon-web-services amazon-sqs amazon-sns
1
This feels like a XY Problem - meta.stackexchange.com/questions/66377/what-is-the-xy-problem . Why are you asking?
– mjwills
Nov 19 at 22:05
The most plausible explanation is that the aforementioned AWS services need unique ID's in order to work properly, which is why they are required. I'm not a member of the AWS teams and I didn't sit in on their requirements stakeholder meetings, so I can't say for sure. But Amazon SNS is a "subscriber-based" service, so it makes sense that it would require unique ID's (per subscriber).
– Robert Harvey♦
Nov 19 at 22:11
Are you encountering a specific problem or limitation related to this? Is the ID requirement impacting you in any way that you need help with?
– Krease
Nov 27 at 0:36
None of other resource based policies like the ones for S3 and KMS require this ID element. Even for SQS and SNS they are allowing duplicate ID values. Just curious why they made this ID element as mandatory in the case of SQS and SNS.
– yerraven
Nov 28 at 18:03
add a comment |
The AWS documentation just mentions it is required and be unique, but doesn't explain beyond that.
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_id.html
amazon-web-services amazon-sqs amazon-sns
The AWS documentation just mentions it is required and be unique, but doesn't explain beyond that.
https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_elements_id.html
amazon-web-services amazon-sqs amazon-sns
amazon-web-services amazon-sqs amazon-sns
edited Nov 19 at 23:12
asked Nov 19 at 21:59
yerraven
42
42
1
This feels like a XY Problem - meta.stackexchange.com/questions/66377/what-is-the-xy-problem . Why are you asking?
– mjwills
Nov 19 at 22:05
The most plausible explanation is that the aforementioned AWS services need unique ID's in order to work properly, which is why they are required. I'm not a member of the AWS teams and I didn't sit in on their requirements stakeholder meetings, so I can't say for sure. But Amazon SNS is a "subscriber-based" service, so it makes sense that it would require unique ID's (per subscriber).
– Robert Harvey♦
Nov 19 at 22:11
Are you encountering a specific problem or limitation related to this? Is the ID requirement impacting you in any way that you need help with?
– Krease
Nov 27 at 0:36
None of other resource based policies like the ones for S3 and KMS require this ID element. Even for SQS and SNS they are allowing duplicate ID values. Just curious why they made this ID element as mandatory in the case of SQS and SNS.
– yerraven
Nov 28 at 18:03
add a comment |
1
This feels like a XY Problem - meta.stackexchange.com/questions/66377/what-is-the-xy-problem . Why are you asking?
– mjwills
Nov 19 at 22:05
The most plausible explanation is that the aforementioned AWS services need unique ID's in order to work properly, which is why they are required. I'm not a member of the AWS teams and I didn't sit in on their requirements stakeholder meetings, so I can't say for sure. But Amazon SNS is a "subscriber-based" service, so it makes sense that it would require unique ID's (per subscriber).
– Robert Harvey♦
Nov 19 at 22:11
Are you encountering a specific problem or limitation related to this? Is the ID requirement impacting you in any way that you need help with?
– Krease
Nov 27 at 0:36
None of other resource based policies like the ones for S3 and KMS require this ID element. Even for SQS and SNS they are allowing duplicate ID values. Just curious why they made this ID element as mandatory in the case of SQS and SNS.
– yerraven
Nov 28 at 18:03
1
1
This feels like a XY Problem - meta.stackexchange.com/questions/66377/what-is-the-xy-problem . Why are you asking?
– mjwills
Nov 19 at 22:05
This feels like a XY Problem - meta.stackexchange.com/questions/66377/what-is-the-xy-problem . Why are you asking?
– mjwills
Nov 19 at 22:05
The most plausible explanation is that the aforementioned AWS services need unique ID's in order to work properly, which is why they are required. I'm not a member of the AWS teams and I didn't sit in on their requirements stakeholder meetings, so I can't say for sure. But Amazon SNS is a "subscriber-based" service, so it makes sense that it would require unique ID's (per subscriber).
– Robert Harvey♦
Nov 19 at 22:11
The most plausible explanation is that the aforementioned AWS services need unique ID's in order to work properly, which is why they are required. I'm not a member of the AWS teams and I didn't sit in on their requirements stakeholder meetings, so I can't say for sure. But Amazon SNS is a "subscriber-based" service, so it makes sense that it would require unique ID's (per subscriber).
– Robert Harvey♦
Nov 19 at 22:11
Are you encountering a specific problem or limitation related to this? Is the ID requirement impacting you in any way that you need help with?
– Krease
Nov 27 at 0:36
Are you encountering a specific problem or limitation related to this? Is the ID requirement impacting you in any way that you need help with?
– Krease
Nov 27 at 0:36
None of other resource based policies like the ones for S3 and KMS require this ID element. Even for SQS and SNS they are allowing duplicate ID values. Just curious why they made this ID element as mandatory in the case of SQS and SNS.
– yerraven
Nov 28 at 18:03
None of other resource based policies like the ones for S3 and KMS require this ID element. Even for SQS and SNS they are allowing duplicate ID values. Just curious why they made this ID element as mandatory in the case of SQS and SNS.
– yerraven
Nov 28 at 18:03
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383249%2fwhy-aws-sqs-and-sns-policies-require-id-element%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53383249%2fwhy-aws-sqs-and-sns-policies-require-id-element%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
This feels like a XY Problem - meta.stackexchange.com/questions/66377/what-is-the-xy-problem . Why are you asking?
– mjwills
Nov 19 at 22:05
The most plausible explanation is that the aforementioned AWS services need unique ID's in order to work properly, which is why they are required. I'm not a member of the AWS teams and I didn't sit in on their requirements stakeholder meetings, so I can't say for sure. But Amazon SNS is a "subscriber-based" service, so it makes sense that it would require unique ID's (per subscriber).
– Robert Harvey♦
Nov 19 at 22:11
Are you encountering a specific problem or limitation related to this? Is the ID requirement impacting you in any way that you need help with?
– Krease
Nov 27 at 0:36
None of other resource based policies like the ones for S3 and KMS require this ID element. Even for SQS and SNS they are allowing duplicate ID values. Just curious why they made this ID element as mandatory in the case of SQS and SNS.
– yerraven
Nov 28 at 18:03