Amazon Neptune now supports global condition keys in AWS IAM policies
You can now customize your AWS Identity and Access Management (IAM) policies that control access to your Amazon Neptune resources, like Neptune clusters or instances, with AWS global condition context keys. You can use AWS global condition context keys, which are specified in the Condition element of an IAM policy, to allow or disallow access to Neptune resources based on the set conditions.
You can now customize your AWS Identity and Access Management (IAM) policies that control access to your Amazon Neptune resources, like Neptune clusters or instances, with AWS global condition context keys. You can use AWS global condition context keys, which are specified in the Condition element of an IAM policy, to allow or disallow access to Neptune resources based on the set conditions.
For example, you can create a policy statement with the aws:SourceIp condition key to limit access to specific source IP addresses or ranges of IP addresses. You can also create a policy statement using the aws:SecureTransport condition key to limit access to requests sent over a Secure Sockets Layer (SSL) connection. The policy statement is effective only when the specified conditions are true.
To learn more about global condition context keys supported by Neptune, see the documentation. For more information on pricing and region availability, refer to the Neptune pricing page and AWS Region Table.