[Response Ops][Connectors][Email] xpack.actions.email.services.ses.host/port kibana config#221389
Conversation
|
Pinging @elastic/response-ops (Team:ResponseOps) |
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8296[✅] x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/connectors/with_aws_ses_kibana_config/config.ts: 100/100 tests passed. |
…ana into issue-220286-email-ses-kbn-cfg
|
Can we add this to |
src/platform/test/plugin_functional/test_suites/core_plugins/rendering.ts
Show resolved
Hide resolved
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
Done in 5b776e7 |
There was a problem hiding this comment.
I tested the creation of the connector with the new configuration and it works as expected. I left some comments. Also:
-
I noticed that based on the docs, if the service is set and is a well-known service, nodemailer will override the host and port even if they are passed. Should we handle that before sending the email?
-
Could you please run the flaky test runner?
| expect(result.email?.domain_allowlist).toEqual(['a.com', 'b.c.com', 'd.e.f.com']); | ||
| }); | ||
|
|
||
| test('email.services.ses', () => { |
There was a problem hiding this comment.
nit: Let's create one test for each assertion. I know this is what we did above, but I think it is more readable and better to reason about the tests if each assertion is on its own test.
There was a problem hiding this comment.
Could you please add some tests in x-pack/platform/plugins/shared/actions/server/actions_config.test.ts?
.../platform/plugins/shared/stack_connectors/server/routes/get_well_known_email_service.test.ts
Show resolved
Hide resolved
| if (config.tenantId == null) { | ||
| throw new Error('[tenantId] is required'); | ||
| } | ||
| } else if (config.service === AdditionalEmailServices.AWS_SES) { |
There was a problem hiding this comment.
This validation here is a breaking change. Before this PR I could create the following connector without issues:
{
"name": "test",
"config": {
"from": "foo@foo.com",
"service": "ses",
"host": "foo.com",
"port": 123,
"secure": true,
"hasAuth": false
},
"secrets": {},
"connector_type_id": ".email"
}
Should we validate only if the configuration is set or even not at all? @pmuellr wdyt?
There was a problem hiding this comment.
But what's the point then in having defaults for this service? Also, in the UI that was not possible. Shouldn't you use "other" for that?
There was a problem hiding this comment.
You can validate only when the configuration is set. This is not a breaking change. Here we validate even if the validation is not set (aside the defaults), right?
| Data type: `string` | ||
|
|
||
| `xpack.actions.email.services.ses.host`  | ||
| : The hostname for an Amazon Simple Email Service (SES) service provider that can be used by email connectors. |
There was a problem hiding this comment.
| : The hostname for an Amazon Simple Email Service (SES) service provider that can be used by email connectors. | |
| : The SMTP endpoint for an Amazon Simple Email Service (SES) service provider that can be used by email connectors. |
Monstly to emphasize that HTTPS is not supported and to be more inline with the AWS terminology.
7bfacf8 to
7707502
Compare
| : The SMTP endpoint for an Amazon Simple Email Service (SES) service provider that can be used by email connectors. | ||
|
|
||
| ::::{warning} | ||
| This setting alone is insufficient to override system defaults for the SES SMTP endpoint. You must also configure the `xpack.actions.email.services.ses.port` setting |
There was a problem hiding this comment.
Hey @nastasha-solomon, could you review it again, please? I did some changes + this warning section is new
There was a problem hiding this comment.
Just a couple minor edits - thanks!
| This setting alone is insufficient to override system defaults for the SES SMTP endpoint. You must also configure the `xpack.actions.email.services.ses.port` setting | |
| This setting alone is insufficient for overriding system defaults for the SES SMTP endpoint. You must also configure the `xpack.actions.email.services.ses.port` setting. |
cnasikas
left a comment
There was a problem hiding this comment.
LGTM! I tested various scenarios with and without configuration and everything is working as expected!
Flaky Test Runner Stats🎉 All tests passed! - kibana-flaky-test-suite-runner#8363[✅] x-pack/test/functional_with_es_ssl/apps/triggers_actions_ui/connectors/with_aws_ses_kibana_config/config.ts: 100/100 tests passed. |
💚 Build Succeeded
Metrics [docs]Page load bundle
History
|
|
Starting backport for target branches: 8.19 https://github.com/elastic/kibana/actions/runs/15614985008 |
💔 All backports failedManual backportTo create the backport manually run: Questions ?Please refer to the Backport tool documentation |
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
…ost/port` kibana config (elastic#221389) ## Summary Closes elastic#220286 ## Release note New AWS SES Email configuration options `xpack.actions.email.services.ses.host` and `xpack.actions.email.services.ses.port`. --------- Co-authored-by: Lisa Cawley <lcawley@elastic.co> (cherry picked from commit f5b6aa2) # Conflicts: # docs/reference/configuration-reference/alerting-settings.md # docs/settings-gen/source/kibana-alert-action-settings.yml
…s.ses.host/port` kibana config (#221389) (#223870) # Backport This will backport the following commits from `main` to `8.19`: - [[Response Ops][Connectors][Email] `xpack.actions.email.services.ses.host/port` kibana config (#221389)](#221389) <!--- Backport version: 10.0.0 --> ### Questions ? Please refer to the [Backport tool documentation](https://github.com/sorenlouv/backport) <!--BACKPORT [{"author":{"name":"Julian Gernun","email":"17549662+jcger@users.noreply.github.com"},"sourceCommit":{"committedDate":"2025-06-12T15:38:08Z","message":"[Response Ops][Connectors][Email] `xpack.actions.email.services.ses.host/port` kibana config (#221389)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/220286\n\n## Release note\n\nNew AWS SES Email configuration options\n`xpack.actions.email.services.ses.host` and\n`xpack.actions.email.services.ses.port`.\n\n---------\n\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>","sha":"f5b6aa241f08723282c84cb877c7a470611915ed","branchLabelMapping":{"^v9.1.0$":"main","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["Team:ResponseOps","release_note:feature","backport:version","v9.1.0","v8.19.0"],"title":"[Response Ops][Connectors][Email] `xpack.actions.email.services.ses.host/port` kibana config","number":221389,"url":"https://github.com/elastic/kibana/pull/221389","mergeCommit":{"message":"[Response Ops][Connectors][Email] `xpack.actions.email.services.ses.host/port` kibana config (#221389)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/220286\n\n## Release note\n\nNew AWS SES Email configuration options\n`xpack.actions.email.services.ses.host` and\n`xpack.actions.email.services.ses.port`.\n\n---------\n\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>","sha":"f5b6aa241f08723282c84cb877c7a470611915ed"}},"sourceBranch":"main","suggestedTargetBranches":["8.19"],"targetPullRequestStates":[{"branch":"main","label":"v9.1.0","branchLabelMappingKey":"^v9.1.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/221389","number":221389,"mergeCommit":{"message":"[Response Ops][Connectors][Email] `xpack.actions.email.services.ses.host/port` kibana config (#221389)\n\n## Summary\n\nCloses https://github.com/elastic/kibana/issues/220286\n\n## Release note\n\nNew AWS SES Email configuration options\n`xpack.actions.email.services.ses.host` and\n`xpack.actions.email.services.ses.port`.\n\n---------\n\nCo-authored-by: Lisa Cawley <lcawley@elastic.co>","sha":"f5b6aa241f08723282c84cb877c7a470611915ed"}},{"branch":"8.19","label":"v8.19.0","branchLabelMappingKey":"^v(\\d+).(\\d+).\\d+$","isSourceBranch":false,"state":"NOT_CREATED"}]}] BACKPORT--> --------- Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
…ost/port` kibana config (elastic#221389) ## Summary Closes elastic#220286 ## Release note New AWS SES Email configuration options `xpack.actions.email.services.ses.host` and `xpack.actions.email.services.ses.port`. --------- Co-authored-by: Lisa Cawley <lcawley@elastic.co>
…c#228215) Available since 9.1 - 8.19 - elastic#223363 - elastic#221389 - elastic#221389 - elastic#222507 (cherry picked from commit 39dda35)
…c#228215) Available since 9.1 - 8.19 - elastic#223363 - elastic#221389 - elastic#221389 - elastic#222507
…c#228215) Available since 9.1 - 8.19 - elastic#223363 - elastic#221389 - elastic#221389 - elastic#222507
Summary
Closes #220286
Release note
New AWS SES Email configuration options
xpack.actions.email.services.ses.hostandxpack.actions.email.services.ses.port.