DOC-426 (hotfix): Correct stale EFS limitations (access points, mount targets, tags) - #933
Merged
quetzalliwrites merged 1 commit intoSep 10, 2026
Conversation
… tags) Verified against src/data/coverage/efs.json and localstack-pro:latest (2026-09-01, per the linked ticket): CreateAccessPoint/DeleteAccessPoint/ DescribeAccessPoints and CreateMountTarget/DeleteMountTarget/ DescribeMountTargets are all implemented, contradicting the docs' claim that mount targets and access points are unsupported. Tagging is mixed: the legacy CreateTags/DeleteTags/DescribeTags operations are not implemented, but TagResource/UntagResource/ListTagsForResource are, so qualify that precisely instead of a blanket "generating tags" claim. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
quetzalliwrites
requested review from
HarshCasper,
bentsku and
pinzon
as code owners
September 9, 2026 19:34
Deploying localstack-docs with
|
| Latest commit: |
b5b9383
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://3be29011.localstack-docs.pages.dev |
| Branch Preview URL: | https://doc-426-efs-docs-incorrectly.localstack-docs.pages.dev |
quetzalliwrites
changed the title
quetzalliwrites
deleted the
doc-426-efs-docs-incorrectly-list-access-point-configuration-as
branch
September 10, 2026 13:43
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
A customer (flagged via NISC evaluation trial) ruled out EFS access points based on our docs, then found they actually work. The ticket confirmed against
localstack-pro:lateston 2026-09-01: creating an access point on a file system succeeds (LifeCycleState: available, confirmed viaDescribeAccessPoints).The docs' "Current Limitations" section made one sentence with three claims: "lacks support for functionalities like creating mount targets, configuring access points, and generating tags." While fixing the access-points part, I cross-checked all three against
src/data/coverage/efs.json:CreateAccessPoint/DeleteAccessPoint/DescribeAccessPointsallimplemented: trueCreateMountTarget/DeleteMountTarget/DescribeMountTargetsallimplemented: trueCreateTags/DeleteTags/DescribeTagsareimplemented: false, but the modernTagResource/UntagResource/ListTagsForResourceareimplemented: trueSo all three parts of the claim were stale or imprecise. Removed the access-points and mount-targets claims entirely, and replaced the blanket "generating tags" claim with the precise legacy-vs-modern tagging API distinction the coverage data actually supports.
Linear ticket
https://linear.app/localstack/issue/DOC-426/efs-docs-incorrectly-list-access-point-configuration-as-unsupported
Test plan
npx astro buildcompletes successfully (417 pages built)src/data/coverage/efs.json