Skip to content

feat(rds): EnableHttpEndpoint, DisableHttpEndpoint and HttpEndpointEnabled - #5736

Merged
pgermosen merged 3 commits into
floci-io:mainfrom
avison9:feat/5732-rds-http-endpoint
Oct 15, 2026
Merged

pgermosen merged 3 commits into
floci-io:mainfrom
avison9:feat/5732-rds-http-endpoint

Conversation

@avison9

@avison9 avison9 commented Oct 15, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Closes #5732.

EnableHttpEndpoint and DisableHttpEndpoint answered UnsupportedOperation, and DBCluster carried no HttpEndpointEnabled. A cluster always read as having the Data API off, whatever Terraform's enable_http_endpoint, CDK's enableDataApi or aws rds enable-http-endpoint had asked for.

aws --endpoint-url http://localhost:4566 rds enable-http-endpoint \
    --resource-arn arn:aws:rds:us-east-1:000000000000:cluster:app
# before: An error occurred (UnsupportedOperation) ...
# after:  {"ResourceArn": "arn:aws:rds:us-east-1:000000000000:cluster:app", "HttpEndpointEnabled": true}

What changed:

  • Model. DbCluster.httpEndpointEnabled, reported as HttpEndpointEnabled in every DBCluster response. It defaults to off, so clusters persisted before this change load with it off.
  • EnableHttpEndpoint / DisableHttpEndpoint take the cluster's ARN and return ResourceArn and HttpEndpointEnabled, with the errors the model lists:
    • ResourceNotFoundFault (404) for an ARN that names no cluster in the caller's account and Region, including an instance ARN, another Region or account, or a malformed ARN;
    • InvalidResourceStateFault for a cluster that is not available;
    • MissingParameter without ResourceArn.
  • CreateDBCluster / ModifyDBCluster EnableHttpEndpoint. A modify that leaves the parameter out leaves the flag as it is. The AWS::RDS::DBCluster EnableHttpEndpoint property sets it on create and on update (No interruption). A template that drops the property turns the endpoint off.
  • Engines. AWS offers the Data API for Aurora PostgreSQL and Aurora MySQL. Turning it on for another engine is InvalidParameterCombination, and a create or CloudFormation stack checks this before the cluster exists. Turning it off is always accepted.
  • Routing. Both actions are in RDS_ACTIONS.
  • Docs.
    • A "Data API endpoint" section and the action rows in docs/services/rds.md.
    • The rds-data.md line that said the flag "is not modeled locally" now says it is recorded but not checked.
    • The RDS count in docs/services/index.md, 98 to 100.

Deliberately not in this PR:

  • Enforcement in rds-data. AWS refuses Data API calls to a cluster with the endpoint off. Doing that here would break every current Floci user who calls the Data API without enabling it, so the flag is recorded and reported only. Enforcement could follow behind a setting if wanted.
  • ModifyDBCluster EnableHttpEndpoint is accepted for any Aurora cluster, although AWS documents it for Aurora Serverless v1 only. Floci does not model Serverless v1 separately, and refusing would only break tools.

Type of change

  • Bug fix (fix:)
  • New feature (feat:)
  • Breaking change (feat!: or fix!:)
  • Docs / chore

AWS Compatibility

Request and response shapes and errors follow the RDS API reference for EnableHttpEndpoint, DisableHttpEndpoint and the EnableHttpEndpoint member of CreateDBCluster / ModifyDBCluster. The new SDK compatibility test RdsControlPlaneTest.sdkTogglesTheDataApiEndpoint enables, describes and disables the endpoint through the AWS SDK for Java, and gets ResourceNotFoundException for an unknown ARN.

Checklist

  • ./mvnw test passes locally
  • New or updated integration test added
  • Commit messages follow Conventional Commits
  • I have no more than 2 open, non-draft pull requests and no more than 4 open pull requests in total (drafts included) in this repository (maintainers and dependency bots are exempt).

…abled

EnableHttpEndpoint and DisableHttpEndpoint answered UnsupportedOperation
and DBCluster carried no HttpEndpointEnabled, so Terraform's
enable_http_endpoint and CDK's enableDataApi never read back what they
set.

Clusters now record the flag and report it. The two actions take the
cluster's ARN and raise ResourceNotFoundFault and
InvalidResourceStateFault as the model lists them; CreateDBCluster,
ModifyDBCluster and the AWS::RDS::DBCluster EnableHttpEndpoint property
set it too. Turning it on is refused for engines other than Aurora
PostgreSQL and Aurora MySQL. The Data API itself does not check the
flag, so existing callers keep working.

Closes floci-io#5732
@qodo-code-review

Copy link
Copy Markdown

PR Summary by Qodo

Support RDS cluster Data API endpoint controls and status

✨ Enhancement 🐞 Bug fix 🧪 Tests 📝 Documentation 🕐 40+ Minutes

Grey Divider

AI Description

• Enable ARN-based Data API endpoint toggles and report their status on RDS clusters.
• Support endpoint configuration through cluster creation, modification, and CloudFormation without
 gating Data API calls.
• Validate engine and resource errors, and cover SDK, persistence, and control-plane behavior.
Diagram

graph TD
  Router["Query router"] --> Handler["RDS Query handler"] --> Service["RDS service"] --> Model["DBCluster model"] --> Storage["Persistent storage"]
  Provisioner["CFN provisioner"] --> Service
  Model --> Response["Cluster XML responses"]
Loading
High-Level Assessment

The following are alternative approaches to this PR:

1. Enforce the flag in RDS Data API
  • ➕ More closely matches AWS endpoint availability.
  • ➖ Would break existing local Data API callers that have not enabled the endpoint.
2. Set the flag within cluster create and modify operations
  • ➕ Could make cluster creation and endpoint configuration atomic.
  • ➖ Would broaden existing service APIs and their callers for a narrowly scoped flag.

Recommendation: Use the PR's shared service setter and leave Data API enforcement out of scope to preserve existing callers. The separate create-then-set path is a reasonable trade-off, though atomic configuration would be worth considering if more cluster properties need the same treatment.

Files changed (12) +370 / -2

Enhancement (5) +113 / -0
AwsQueryController.javaRoute the two endpoint actions to RDS +1/-0

Route the two endpoint actions to RDS

• Adds EnableHttpEndpoint and DisableHttpEndpoint to the RDS Query dispatch action set.

src/main/java/io/github/hectorvent/floci/core/common/AwsQueryController.java

RdsCfnProvisioner.javaReconcile CloudFormation EnableHttpEndpoint +9/-0

Reconcile CloudFormation EnableHttpEndpoint

• Validates the engine before creating an enabled cluster and reconciles the property on create and update. Omitting the property on an update disables a previously enabled endpoint.

src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java

RdsQueryHandler.javaHandle endpoint actions and cluster flag parameters +29/-0

Handle endpoint actions and cluster flag parameters

• Adds enable and disable responses, accepts EnableHttpEndpoint during cluster creation and modification, and includes HttpEndpointEnabled in cluster XML responses.

src/main/java/io/github/hectorvent/floci/services/rds/RdsQueryHandler.java

RdsService.javaValidate and persist endpoint state changes +69/-0

Validate and persist endpoint state changes

• Adds ARN-scoped cluster lookup, state and engine validation, and shared methods for changing the flag. Missing, malformed, or out-of-scope resource ARNs produce resource-not-found errors.

src/main/java/io/github/hectorvent/floci/services/rds/RdsService.java

DbCluster.javaStore the cluster endpoint-enabled flag +5/-0

Store the cluster endpoint-enabled flag

• Adds a boolean HttpEndpointEnabled model property that defaults to false for new and previously persisted clusters.

src/main/java/io/github/hectorvent/floci/services/rds/model/DbCluster.java

Tests (4) +240 / -0
RdsControlPlaneTest.javaVerify endpoint toggling through the AWS Java SDK +27/-0

Verify endpoint toggling through the AWS Java SDK

• Adds a cluster lifecycle test that enables and disables the endpoint, checks describe readback, and verifies a missing ARN raises the SDK's resource-not-found exception.

compatibility-tests/sdk-test-java/src/test/java/com/floci/test/RdsControlPlaneTest.java

RdsCfnProvisionerTest.javaTest CloudFormation endpoint reconciliation +37/-0

Test CloudFormation endpoint reconciliation

• Covers enabling the endpoint on create, disabling it when an update omits the property, and rejecting a non-Aurora engine before cluster creation.

src/test/java/io/github/hectorvent/floci/services/cloudformation/RdsCfnProvisionerTest.java

RdsHttpEndpointIntegrationTest.javaExercise endpoint actions and validation through RDS Query +156/-0

Exercise endpoint actions and validation through RDS Query

• Tests default and changed flags, create and modify behavior, ARN and missing-parameter errors, stopped-cluster rejection, and engine restrictions.

src/test/java/io/github/hectorvent/floci/services/rds/RdsHttpEndpointIntegrationTest.java

DbClusterPersistenceTest.javaTest endpoint flag persistence and legacy defaults +20/-0

Test endpoint flag persistence and legacy defaults

• Verifies that enabled state survives a storage reload and that older cluster records load with the endpoint disabled.

src/test/java/io/github/hectorvent/floci/services/rds/model/DbClusterPersistenceTest.java

Documentation (3) +17 / -2
index.mdIncrease the documented RDS operation count +1/-1

Increase the documented RDS operation count

• Changes the RDS operation count from 98 to 100 for the two supported endpoint actions.

docs/services/index.md

rds-data.mdClarify that Data API requests do not check the endpoint flag +1/-1

Clarify that Data API requests do not check the endpoint flag

• Explains that RDS records HttpEndpointEnabled while local Data API availability remains independent of it.

docs/services/rds-data.md

rds.mdDocument RDS Data API endpoint controls +15/-0

Document RDS Data API endpoint controls

• Lists the new actions and describes supported engines, cluster properties, error behavior, and the absence of Data API enforcement.

docs/services/rds.md

@qodo-code-review

qodo-code-review Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (1) 📎 Requirement gaps (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

Grey Divider


Action required

1. Unsupported engines enable the endpoint ✓ Resolved
Description
RdsService.requireDataApiEngine accepts any lower-case engine name beginning with aurora, rather
than restricting it to aurora-postgresql and aurora-mysql. A bare or unrecognized Aurora engine
can therefore pass the new endpoint validation during enable or modification instead of producing
InvalidParameterCombination.
Code

src/main/java/io/github/hectorvent/floci/services/rds/RdsService.java[R9796-9800]

+    public static void requireDataApiEngine(String engine) {
+        String name = engine == null ? "postgres" : engine.toLowerCase(Locale.ROOT);
+        if (!name.startsWith("aurora")) {
+            throw new AwsException("InvalidParameterCombination", "The Data API (HTTP endpoint) is available for "
+                    + "Aurora PostgreSQL and Aurora MySQL DB clusters only, not for engine " + name + ".", 400);
Relevance

●●● Strong

Recent RDS precedent restricts engine-specific features rather than allowing broad Aurora-name
matches.

PR-#5206

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The endpoint engine validator accepts every name beginning with aurora, while the ticket-derived
requirement limits the feature to Aurora PostgreSQL and Aurora MySQL.

Support HTTP endpoint enable and disable actions
src/main/java/io/github/hectorvent/floci/services/rds/RdsService.java[9796-9801]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The endpoint validation accepts every engine whose name starts with `aurora`, although the Data API is supported only for `aurora-postgresql` and `aurora-mysql`. Unsupported or malformed Aurora engine names can pass validation instead of returning `InvalidParameterCombination`.

## Fix Focus Areas
- src/main/java/io/github/hectorvent/floci/services/rds/RdsService.java[9796-9801]

## Recommended Fix
Replace the `startsWith("aurora")` check with an exact membership check for `aurora-postgresql` and `aurora-mysql`, using the normalized engine name. Add regression coverage for a non-supported Aurora engine name and verify that enabling the endpoint is rejected.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools



Remediation recommended

2. Invalid templates can turn the endpoint off ✓ Resolved
Description
provisionDbCluster reads EnableHttpEndpoint through parseBoolProp, which converts every value
other than true to false without rejecting it. When an update supplies an invalid string such as
"yes" for an enabled cluster, the template proceeds and the endpoint is disabled.
Code

src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[445]

+        boolean httpEndpoint = parseBoolProp(props, "EnableHttpEndpoint", engine);
Relevance

●●● Strong

Recent CloudFormation precedent favors validating supplied boolean properties instead of silently
coercing invalid values.

PR-#5390

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
Resource properties reach the provisioner without Boolean schema validation. The helper uses
Boolean.parseBoolean, and the new reconciliation persists its false result when the existing flag
is true.

src/main/java/io/github/hectorvent/floci/services/cloudformation/CloudFormationService.java[1729-1745]
src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[1075-1077]
src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[445-459]
src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[477-480]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
Malformed CloudFormation endpoint values silently become false and can disable an existing endpoint.
## Fix Focus Areas
- src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[445-449]
- src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[1075-1077]
## Recommended Fix
Parse this property strictly: accept resolved Boolean true and false values, preserve false for omission or `AWS::NoValue`, and raise a validation error for any other supplied value. Test an invalid value during an update to an enabled cluster.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools


3. A failed update leaves the endpoint changed 🐞 Bug ☼ Reliability
Description
provisionDbCluster persists an in-place EnableHttpEndpoint change without recording its previous
value for rollbackUpdate. If a later stack resource fails, rollback neither restores the flag nor
redeploys the old template, and the stack enters UPDATE_ROLLBACK_FAILED with the cluster still in
the failed update's state.
Code

src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[R479-480]

+        if (httpEndpoint != cluster.isHttpEndpointEnabled()) {
+            cluster = rdsService.setHttpEndpoint(region, cluster.getDbClusterIdentifier(), httpEndpoint);
Relevance

●●● Strong

Recent precedent consistently accepts rollback snapshots for in-place mutations affecting later
stack-resource failures.

PR-#5656
PR-#4599

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The added call persists the new flag. The stack's rollback delegates to the RDS provisioner, whose
rollback handles replacement and metadata records but not this flag; an unhandled in-place update is
marked failed.

src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[477-481]
src/main/java/io/github/hectorvent/floci/services/rds/RdsService.java[9776-9789]
src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[192-221]
src/main/java/io/github/hectorvent/floci/services/cloudformation/CloudFormationService.java[2454-2474]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
An in-place CloudFormation endpoint update survives a failed stack update and leaves rollback incomplete.
## Fix Focus Areas
- src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[478-481]
- src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[192-221]
## Recommended Fix
Record the prior endpoint flag before changing it, restore that flag in `rollbackUpdate` for in-place cluster updates, and clear the rollback record after a successful update. Add a stack-level test in which a later resource fails.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗



Informational

4. Cleanup failures leave clusters behind 📘 Rule violation ☼ Reliability
Description
The new compatibility test catches every Exception from deleteDBCluster and only logs it at
warning level. If deletion fails after the test has created the cluster, the test still completes
while the cluster remains in the shared environment.
Code

compatibility-tests/sdk-test-java/src/test/java/com/floci/test/RdsControlPlaneTest.java[R785-790]

+        } finally {
+            try {
+                rds.deleteDBCluster(b -> b.dbClusterIdentifier(clusterName).skipFinalSnapshot(true));
+            } catch (Exception e) {
+                LOG.log(Level.WARNING, "Failed to clean up RDS cluster " + clusterName, e);
+            }
Relevance

● Weak

Recent RDS precedent rejects broad cleanup suppression; unexpected deletion failures must propagate.

PR-#5367

ⓘ Recommendations generated based on similar findings in past PRs

Evidence
The added test creates an RDS cluster, then catches Exception around deletion and continues after
logging. This suppresses non-benign cleanup failures contrary to the broad-exception handling
requirement.

Rule 3865600: Do not swallow exceptions broadly; suppress only known benign errors
compatibility-tests/sdk-test-java/src/test/java/com/floci/test/RdsControlPlaneTest.java[785-790]

Agent prompt
The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The test suppresses all cleanup exceptions after creating an RDS cluster, so a failed deletion can leave a persistent cluster behind and contaminate later tests or incur resource cost.

## Fix Focus Areas
- compatibility-tests/sdk-test-java/src/test/java/com/floci/test/RdsControlPlaneTest.java[785-790]

## Recommended Fix
Do not broadly catch and suppress cleanup failures. Preserve the original test failure when one exists, but propagate a deletion failure when cleanup is the only failure; alternatively catch only the specific expected idempotent deletion error and fail the test for all other exceptions.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗


Grey Divider

Context sources
✅ Compliance rules (platform): 8 rules
✅ Cross-repo context — repo relationships
  Explored: repo: floci-io/floci-ui (sha: ba041ac4) — View relationship
Review mode: Auto: 🧠 Deep: Confidence 3/5; multiple RDS paths create several independent edge-case risks.

Grey Divider

Tip of the day
💡 Did you know, you can hide the parts of a finding you never read, like the evidence or the agent prompt

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

Grey Divider

Qodo Logo

Comment on lines +479 to +480
if (httpEndpoint != cluster.isHttpEndpointEnabled()) {
cluster = rdsService.setHttpEndpoint(region, cluster.getDbClusterIdentifier(), httpEndpoint);

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Remediation recommended

2. A failed update leaves the endpoint changed 🐞 Bug ☼ Reliability

provisionDbCluster persists an in-place EnableHttpEndpoint change without recording its previous
value for rollbackUpdate. If a later stack resource fails, rollback neither restores the flag nor
redeploys the old template, and the stack enters UPDATE_ROLLBACK_FAILED with the cluster still in
the failed update's state.
Agent Prompt
## Issue description
An in-place CloudFormation endpoint update survives a failed stack update and leaves rollback incomplete.
## Fix Focus Areas
- src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[478-481]
- src/main/java/io/github/hectorvent/floci/services/cloudformation/provisioners/RdsCfnProvisioner.java[192-221]
## Recommended Fix
Record the prior endpoint flag before changing it, restore that flag in `rollbackUpdate` for in-place cluster updates, and clear the rollback record after a successful update. Add a stack-level test in which a later resource fails.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

Dismiss ↗ | View ↗

@pgermosen pgermosen added rds Amazon Relational Database Service (RDS) enhancement New feature or request cloudformation AWS CloudFormation labels Oct 15, 2026

@pgermosen pgermosen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@avison9 thanks, the shapes and errors match the EnableHttpEndpoint and DisableHttpEndpoint reference, and recording the flag without enforcing it in rds-data is a sensible line to draw.

One thing: clusterForResourceArn repeats what clusterIdentifierFromArnOrName in the same class already does, the ARN parse, the cluster: prefix and the region and account check, and only the error differs. Please pull that into one helper that both call, each throwing its own error.

@pgermosen pgermosen added the waiting-author Review posted; waiting on the PR author to respond label Oct 15, 2026
clusterForResourceArn repeated the ARN parsing, cluster: prefix and
account and Region check of clusterIdentifierFromArnOrName; both now
call clusterIdFromArn, each raising the error its API documents.

The Data API engine check takes aurora-postgresql, aurora-mysql and the
older aurora name exactly instead of any name starting with aurora, and
the AWS::RDS::DBCluster EnableHttpEndpoint property accepts true or
false only, so a malformed value fails instead of turning the endpoint
off.
@avison9

avison9 commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

Done in 3074d30. clusterIdFromArn now holds the ARN parse, the cluster: prefix and the Region and account check. clusterIdentifierFromArnOrName calls it with InvalidParameterValue and DBClusterNotFoundFault, and clusterForResourceArn calls it with ResourceNotFoundFault.

Two tightenings in the same commit:

  • Engine check. It now takes aurora-postgresql, aurora-mysql and the older aurora name exactly, instead of any name starting with aurora.
  • CloudFormation. EnableHttpEndpoint accepts only true or false, so a malformed value fails the resource instead of turning the endpoint off.

RdsHttpEndpointIntegrationTest, the restore suites that resolve source-cluster ARNs, and the RDS, RDS Data, Neptune, DocumentDB and CloudFormation RDS test classes pass: 1,633 tests, none failing.

@pgermosen pgermosen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@avison9 thanks, the shared ARN parser reads well, and making EnableHttpEndpoint strict was a good call.

One small thing left: drop the bare "aurora" from the Data API engine set. The API reference only lists aurora-mysql and aurora-postgresql, and resolveEngine already refuses the bare name for new clusters, so no cluster can carry it and the entry just makes the check look looser than it is. The engine test would then expect it to be refused.

Rolling the endpoint back on a failed stack update would be nice, but every in-place cluster property has the same gap today, so leave that for a separate PR on the provisioner.

The API reference lists those two engines, and new clusters cannot carry
the bare aurora name, so the check no longer accepts it.
@avison9

avison9 commented Oct 15, 2026

Copy link
Copy Markdown
Contributor Author

Done in 188f68d: DATA_API_ENGINES is aurora-mysql and aurora-postgresql only, and theDataApiTakesOnlyTheAuroraEngines now expects the bare aurora to be refused with InvalidParameterCombination. Leaving the stack-update rollback for a separate change, as suggested.

@pgermosen pgermosen left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @avison9, that closes the engine check. Good to go.

I tidied the description for the squash commit: dropped the run log and the test list, and put the first checklist line back to the template.

(follow-up, separate PR) A failed stack update still leaves EnableHttpEndpoint changed, the same as every other in-place DB cluster property (IAM auth, capacity, auto-pause, the master password). Fixing that needs a rollback design for the whole cluster resource, including how to restore a password without keeping it in the stack.

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

Labels

cloudformation AWS CloudFormation enhancement New feature or request rds Amazon Relational Database Service (RDS)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FEAT] rds: EnableHttpEndpoint, DisableHttpEndpoint and HttpEndpointEnabled on DB clusters

2 participants