updated security docs - https connection method #708
Merged
Conversation
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
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
fiquick
changed the title
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
| * Connections using private endpoints are one-way. | ||
| Aura VPCs can't initiate connections back to your VPCs. | ||
| * In AWS region us-east-1, we do not support the Availability Zone with ID use1-az3 for private endpoints. | ||
| AWS region `us-east-1` does not support private endpoints in the `use1-az3` Availability Zone. |
There was a problem hiding this comment.
Suggested change
| AWS region `us-east-1` does not support private endpoints in the `use1-az3` Availability Zone. | |
| In the AWS region `us-east-1`, the Availability Zone with ID `use1-az3` is not supported for private endpoints. |
I'm unsure about this one, but it is Neo4j that doesn't support this, not AWS, right?
There was a problem hiding this comment.
Changing it to "In AWS region us-east-1, we do not support the Availability Zone with ID use1-az3 for private endpoints."
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
Co-authored-by: Jessica Wright <[email protected]>
| * Connections using private endpoints are one-way. | ||
| Aura VPCs can't initiate connections back to your VPCs. | ||
| * In AWS region us-east-1, we do not support the Availability Zone with ID use1-az3 for private endpoints. | ||
| In AWS region `us-east-1`, we do not support the Availability Zone with ID `use1-az3` for private endpoints. |
There was a problem hiding this comment.
Suggested change
| In AWS region `us-east-1`, we do not support the Availability Zone with ID `use1-az3` for private endpoints. | |
| In AWS region `us-east-1`, the Availability Zone with ID `use1-az3` is not supported for private endpoints. |
Remember the "we vs. you" rule in docs, avoid "we" at all costs!
There was a problem hiding this comment.
Come to think of it, you could also say:
In AWS region us-east-1, Neo4j does not support the Availability Zone with ID use1-az3 for private endpoints.
|
Thanks for the documentation updates. The preview documentation has now been torn down - reopening this PR will republish it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.