similar to: AWS signatures

When I do an XMLRPC webservice call to retrieve a single Product, my DateTime fields in the products table do not get converted to a valid DateTime value, but remain as XMLRPC::DateTime structures. So, say my webservice call is: @product = @aws.get_product(1) Then my @product object looks like this: name: My product last_updated: #<XMLRPC::DateTime:0x37c5338> description: This is my

I am writing code to setup an AWS Server. I am able to test all the values accurately using web_service_scaffold :test, but when I try to connect by creating an XML-RPC client i am getting a timeout error = execution expired I am using delegated dispatching web_service_name: update_shipping method_name: update_product_status I am trying to test the function by implementing an XML-RPC client to

I''m building a users web service (direct dispatching) that will (I hope) allow several other applications to manage the same pool of users. Plus it will act as a single-sign-on solution for what I''m doing. But I''m having difficulty accessing the UserAPI. Here''s what I''ve done so far: $> rails usermanagement - "usermanagement" is the

In my tests, I want to invoke my webservice not using the default SOAP protocol, but using XmlRpc ... how do I do that? -- Posted via http://www.ruby-forum.com/.

OK. I think I found the issue. The key is to add rtp_symmetric=yes Here's what my final configuration looks like: [transport-udp] type=transport protocol=udp bind=0.0.0.0 ;; for within EC2 local_net=172.31.32.0/20 ;; For softphones within EC2 local_net=192.168.1.0/24 external_media_address=<publicIPOfEC2Instance> external_signaling_address=<publicIPOfEC2Instance>

I tried to establish connection to my aws s3 account like this in my irb console - AWS::S3::Base.establish_connection!(:access_key_id => ''my access key'', :secret_access_key => ''my secret key'', :server => " s3-ap-southeast-1.amazonaws.com") And it works well and prompt this - => #<AWS::S3::Connection:0x8cd86d0

Hello All, I have an Asterisk server v13.1.0 running on EC2 and I am able to connect and register SIP devices and "see" them on the asterisk CLI. I am also able to place calls, but I am not able to hear any audio on either end after the call is picked up. I was wondering if you can tell me what a minimal configuration for Asterisk on EC2 looks like. My current pjsip.conf configuration

This is an automated email from the git hooks/post-receive script. arrfab pushed a commit to branch master in repository centos/centos.org. The following commit(s) were added to refs/heads/master by this push: new 973d90a Added AWS as sponsor 973d90a is described below commit 973d90a1c09ad0ef6efdf200cc0e102f75442448 Author: Fabian Arrotin <arrfab at centos.org> AuthorDate: Tue Dec 3

Hello all, and thank you very much for the Centos 7 HVM AMI [1], greatly appreciated! This AMI does not work on the newly launched AWS Frankfurt region (eu-central-1). Any plans for fixing that? According to the AWS announcement [2], "The Region supports all sizes of T2, M3, C3, R3, and I2 instances". (We'll be running the CentOS 7 HVM AMI going forward, but looks like none of

On 04/12/2016 01:37 PM, Peter Steele wrote: > On 04/11/2016 11:33 AM, Laine Stump wrote: I wouldn't be too quick to > judgement. First take a look at tcpdump on the bridge interface that > the containers are attached to, and on the ethernet device that > connects the bridge to the rest of Amazon's infrastructure. If you see > packets from the container's IP going out

On 07/26/2017 09:29 AM, Stephan Koledin wrote: > Some additional info... > > AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS > team, not by AWS. Details and suggestions to contact this list for > assistance are published at both https://wiki.centos.org/Cloud/AWS and > https://wiki.centos.org/Cloud/AWS > > Basically, the maintainer of the Centos.org

Some additional info... AFAIK, the AMIs I'm referring to are owned/maintained by the CentOS team, not by AWS. Details and suggestions to contact this list for assistance are published at both https://wiki.centos.org/Cloud/AWS and https://wiki.centos.org/Cloud/AWS Basically, the maintainer of the Centos.org AWS account just needs to add/approve the current AMIs for the g3.* instance

Hi list, I've noticed that instance-backed AMIs are not available in AWS MP (only the EBS ones are there). Still though, also the instance-backed AMIs are listed as published and available on your wiki: http://wiki.centos.org/Cloud/AWS I've seen that the same question was asked already before but I'm not sure the answer given actually covered the whole question:

Tomorrow, I intend to push a change to mirrorlist.centos.org nodes that will have a (good) impact to CentOS EC2 instances running from AWS network. Thanks to AWS, sponsoring the required backend infra for this to happen, our mirrorlist nodes will redirect yum/dnf operations internally in the EC2/AWS network. What does that mean for you ? - faster updates (due to Cloudfront caching, and so most

to follow-up, I will give an example. Here is the listing for the official centos AMI: IMAGE ami-96a818fe aws-marketplace/CentOS 7 x86_64 (2014_09_29) EBS HVM-b7ee8a69-ee97-4a49-9e68-afaee216db2e-ami-d2a117ba.2 aws-marketplace available public [marketplace: aw0evgkw8e5c1q413zgy5pjce] x86_64 machineebs hvm xen BLOCKDEVICEMAPPING EBS /dev/sda1

This is not really a problem at all. when you launch your image for the first time, you can specify a larger / volume size and cloud-init-tools will take care of the rest. This is well documented in the AWS userguides. -- Kelly Prescott On Wed, 29 Apr 2015, Nico Kadel-Garcia wrote: > I'm staring at the free CentOS images on AWS, and seeing that whoever > set those up elected to use a

Hello, Am running build install on an existing project and I get this error: Installing aws-s3 (0.6.2) Errno::EACCES: Permission-denied - D:/RailsInstaller/Ruby1.9.3/lib/ruby/gems/1.9.1/gems/aws-s3-0.6.2/lib/aws/s3/bittorrent.rb An error occured while installing aws-s3 (0.6.2) and Bundler cannot continue, make sure that gem install aws-s3 -v ''0.6.2'' succeeds before bundling.

https://forums.aws.amazon.com/thread.jspa?messageID=481859&#481859 https://forums.aws.amazon.com/thread.jspa?messageID=453572&#453572 This is a timebomb waiting to strike so many people who like do daily snapshot backups and keep them for few weeks and not realizing their snapshots are useless if they had accidentally mess up some boot related file earlier on. Another scenario you mess

On Tue, May 12, 2020 at 8:02 PM Paul Heinlein <heinlein at madboa.com> wrote: > On Tue, 12 May 2020, Thomas Stephen Lee wrote: > > > Hi, > > > > I am user of CentOS 8. > > When can we expect an image on AWS? > > I am just learning AWS and would like to use CentOS 8 for that. > > I can't speak to AWS per se, but Digital Ocean has a CentOS 8

Hi, I launched an AWS instance `t2.medium` (use CentOS 7 image "ami-7abd0209", product code: https://aws.amazon.com/marketplace/pp/B00O7WM7QW), which is supposed to have 4GB Memory in total, but turn out it is only "3.5GB". ``` $ free -h total used free shared buff/cache available Mem: 3.5G 441M 1.4G 16M