Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Validate that SMTP Brokerpak handles multi-tenancy #2991

Closed
1 task done
Tracked by #2512
jameshochadel opened this issue Apr 22, 2024 · 1 comment
Closed
1 task done
Tracked by #2512

Validate that SMTP Brokerpak handles multi-tenancy #2991

jameshochadel opened this issue Apr 22, 2024 · 1 comment
Assignees

Comments

@jameshochadel
Copy link
Contributor

jameshochadel commented Apr 22, 2024

The existing deployment(s) of the SMTP brokerpak mentioned in #2988 were designed for use by single customers who run the Cloud Service Broker as a Supplemental Service Broker, brokering services to one organization only. Our CSB deployment will be available to all customers, so we must make sure the provisioning & binding code creates resources scoped to the tenant that created them.

Acceptance Criteria:

  • Validate that binding credentials have access to only one SES identity and document the reasoning or results
@jameshochadel
Copy link
Contributor Author

Per AWS, a user cannot send to an identity without an IAM policy or Sending Authorization Policy that allows it. The brokerpak implements this with an IAM policy, which includes a Resource constraint with the ARN of their identity and configuration set. This prevents cross-identity, and therefore cross-tenant, access.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant