27.2. S3_PING Configuration Options Red Hat JBoss Data Grid works with Amazon Web Services in two ways: In Library mode, use JGroups' default-configs/default-jgroups-ec2.xml file (see Section 26.2.2.3, "default-jgroups-ec2.xml" for details) or use the S3_PING protocol. In Remote Client-Server mode, use JGroups' S3_PING protocol. In Library and Remote Client-Server mode, there are three ways to configure the S3_PING protocol for clustering to work in Amazon AWS: Use Private S3 Buckets. These buckets use Amazon AWS credentials. Use Pre-Signed URLs. These pre-assigned URLs are assigned to buckets with private write and public read rights. Use Public S3 Buckets. These buckets do not have any credentials. Report a bug 27.2.1. Using Private S3 Buckets This configuration requires access to a private bucket that can only be accessed with the appropriate AWS credentials. To confirm that the appropriate permissions are available, confirm that the user has the following permissions for the bucket: List Upload/Delete View Permissions Edit Permissions Ensure that the S3_PING configuration includes the following properties: either the location or the prefix property to specify the bucket, but not both. If the prefix property is set, S3_PING searches for a bucket with a name that starts with the prefix value. If a bucket with the prefix at the beginning of the name is found, S3_PING uses that bucket. If a bucket with the prefix is not found, S3_PING creates a bucket using the AWS credentials and names it based on the prefix and a UUID (the naming format is {prefix value} - {UUID} ). the access_key and secret_access_key properties for the AWS user. Note If a 403 error displays when using this configuration, verify that the properties have the correct values. If the problem persists, confirm that the system time in the EC2 node is correct. Amazon S3 rejects requests with a time stamp that is more than 15 minutes old compared to their server's times for security purposes. Example 27.1. Start the Red Hat JBoss Data Grid Server with a Private Bucket Run the following command from the top level of the server directory to start the Red Hat JBoss Data Grid server using a private S3 bucket: Replace {server_ip_address} with the server's IP address. Replace {s3_bucket_name} with the appropriate bucket name. Replace {access_key} with the user's access key. Replace {secret_access_key} with the user's secret access key. Report a bug 27.2.2. Using Pre-Signed URLs For this configuration, create a publically readable bucket in S3 by setting the List permissions to Everyone to allow public read access. Each node in the cluster generates a pre-signed URL for put and delete operations, as required by the S3_PING protocol. This URL points to a unique file and can include a folder path within the bucket. Note Longer paths will cause errors in S3_PING . For example, a path such as my_bucket/DemoCluster/node1 works while a longer path such as my_bucket/Demo/Cluster/node1 will not. Report a bug 27.2.2.1. Generating Pre-Signed URLs JGroup's S3_PING class includes a utility method to generate pre-signed URLs. The last argument for this method is the time when the URL expires expressed in the number of seconds since the Unix epoch (January 1, 1970). The syntax to generate a pre-signed URL is as follows: Replace {operation} with either PUT or DELETE . Replace {access_key} with the user's access key. Replace {secret_access_key} with the user's secret access key. Replace {bucket_name} with the name of the bucket. Replace {path} with the desired path to the file within the bucket. Replace {seconds} with the number of seconds since the Unix epoch (January 1, 1970) that the path remains valid. Example 27.2. Generate a Pre-Signed URL Ensure that the S3_PING configuration includes the pre_signed_put_url and pre_signed_delete_url properties generated by the call to S3_PING.generatePreSignedUrl() . This configuration is more secure than one using private S3 buckets, because the AWS credentials are not stored on each node in the cluster Note If a pre-signed URL is entered into an XML file, then the & characters in the URL must be replaced with its XML entity ( &amp; ). Report a bug 27.2.2.2. Set Pre-Signed URLs Using the Command Line To set the pre-signed URLs using the command line, use the following guidelines: Enclose the URL in double quotation marks ( " " ). In the URL, each occurrence of the ampersand ( & ) character must be escaped with a backslash ( \ ) Example 27.3. Start a JBoss Data Grid Server with a Pre-Signed URL In the provided example, the {signatures} values are generated by the S3_PING.generatePreSignedUrl() method. Additionally, the {expiration_time} values are the expiration time for the URL that are passed into the S3_PING.generatePreSignedUrl() method. Report a bug 27.2.3. Using Public S3 Buckets This configuration involves an S3 bucket that has public read and write permissions, which means that Everyone has permissions to List , Upload/Delete , View Permissions , and Edit Permissions for the bucket. The location property must be specified with the bucket name for this configuration. This configuration method is the least secure because any user who knows the name of the bucket can upload and store data in the bucket and the bucket creator's account is charged for this data. To start the Red Hat JBoss Data Grid server, use the following command: Report a bug 27.2.4. Troubleshooting S3_PING Warnings Depending on the S3_PING configuration type used, the following warnings may appear when starting the JBoss Data Grid Server: In each case, ensure that the property listed as missing in the warning is not needed by the S3_PING configuration. Report a bug

Commands:
bin/clustered.sh -Djboss.bind.address= {server_ip_address} -Djboss.bind.address.management= {server_ip_address} -Djboss.default.jgroups.stack=s3 -Djgroups.s3.bucket= {s3_bucket_name} -Djgroups.s3.access_key= {access_key} -Djgroups.s3.secret_access_key= {secret_access_key}
String Url = S3_PING.generatePreSignedUrl(" {access_key} ", " {secret_access_key} ", " {operation} ", " {bucket_name} ", " {path} ", {seconds} );
String putUrl = S3_PING.generatePreSignedUrl(" access_key ", " secret_access_key ", "put", " my_bucket ", " DemoCluster/node1 ", 1234567890 );
bin/clustered.sh -Djboss.bind.address= {server_ip_address} -Djboss.bind.address.management= {server_ip_address} -Djboss.default.jgroups.stack=s3 -Djgroups.s3.pre_signed_put_url="http:// {s3_bucket_name} .s3.amazonaws.com/ node1?AWSAccessKeyId= {access_key} \&Expires= {expiration_time} \&Signature= {signature} "-Djgroups.s3.pre_signed_delete_url="http:// {s3_bucket_name} .s3.amazonaws.com/ node1?AWSAccessKeyId= {access_key} \&Expires= {expiration_time} \&Signature= {signature} "
bin/clustered.sh -Djboss.bind.address= {server_ip_address} -Djboss.bind.address.management= {server_ip_address} -Djboss.default.jgroups.stack=s3 -Djgroups.s3.bucket= {s3_bucket_name}
15:46:03,468 WARN [org.jgroups.conf.ProtocolConfiguration] (MSC service thread 1-7) variable "USD{jgroups.s3.pre_signed_put_url}" in S3_PING could not be substituted; pre_signed_put_url is removed from properties
15:46:03,469 WARN [org.jgroups.conf.ProtocolConfiguration] (MSC service thread 1-7) variable "USD{jgroups.s3.prefix}" in S3_PING could not be substituted; prefix is removed from properties
15:46:03,469 WARN [org.jgroups.conf.ProtocolConfiguration] (MSC service thread 1-7) variable "USD{jgroups.s3.pre_signed_delete_url}" in S3_PING could not be substituted; pre_signed_delete_url is removed from properties