I'm trying to use AWS Location Service to geocode a real address, but it's not working.
Address:
1141 Av. A
San Juan, Puerto Rico, 00915
Seems like AWS is limited in it's ability to locate an address as compared to other platforms... Any thoughts on how to get around this with AWS?
I even tried the AWS website and it didn't work either.
https://us-east-2.console.aws.amazon.com/location/explore/home?region=us-east-2#/place
Related
I am using AWS ELK(amazon managed elastic) and my Kibana health status is red, trying to browse to the kibana URL i get "Kibana server is not ready yet".
I have tried to fix the problem but without luck, I think it all start when I changed my ELK settings from 1 availability zones with 1 instances to 2 Availability zones or another option is that I have streamed large amount of data in the last day.
As part of trials to fix the problem I returned to 1 availability zones with 1 instances but that didn't fix the problem.
Also I have Enabled the error logs and seen that I receive in cloudwatch:
"publishing cluster state with version [68816] failed for the
following nodes"
"failed to connect to node"
Any help solving this problem will help.
More info(about my current setup):
Domain status:Active
Elasticsearch version: 6.7
Availability zones:1
Instance type:r5.large.elasticsearch
Number of instances:1
Storage type:EBS
EBS volume type:General Purpose (SSD)
EBS volume size:1000 GB
Encryption at rest:Disabled
Node-to-node encryption:Disabled
Amazon Cognito for authentication:Disabled
Service software release:R20190724-P1
in the cluster health tab of the domain I can see:
Cluster status:green
MasterReachableFromNode:green
AutomatedSnapshotFailure:green
KibanaHealthyNodes:red
and in the InvalidHostHeaderRequests I have about 60% of requests that are InvalidHostHeaderRequests out of ElasticsearchRequests (but I guess that is unrelated):
CPUUtilization: is about 8%
JVMMemoryPressure: is about 20%
SysMemoryUtilization:98%
KibanaHealthyNodes is red possibly your kibana is down. Have you updated to AWS Elasticsearch v6.7 recently? Looks like the kibana needs to be restarted on the elasticsearch cluster for which AWS support team can help you with. Or in case you dont have support plan might be if you post on AWS forum someone from AWS can take a look and assist you with the same.
InvalidHostHeaderRequests will not cause the issue with kibana. AWS ES will throw this error when your application is trying to send the request on IPs of the nodes. Please check and use the domain endpoint in the request else this error will come up.
https://docs.aws.amazon.com/elasticsearch-service/latest/developerguide/es-managedomains.html
Website slow response slow from some locations
I have a web server hosted in AWS Oregon region.
Our customer are accessing this website from a different part of the world (mostly from US, UK, and Dubai)
static assets are already on the AWS CloudFront
Now a day most of the customer from Dubai and UK are complaining that our web site is very slow but in the same time, we tried to access the website from the USA and other location but its fast.
what cloud be the best solution to make the site fast for all the customer in different locations.
web server is under ELB and we are using the SSL (ACM) certificate on the ELB for https.
Please suggest me the best solution. what about the Route53 latency bases routing .. will this work for my case.
In AWS you have a lot of regions. Many of them closer to your costumers. So, why not replicate the server to a closer region to match your costumers location. It's a looong way from Oregon to UK and Dubai.
EDIT:
shahid: "so your saying we have to setup to on web server on every region.whihc will cost us a lot more."
#shahid it's not in all aws regions, maybe just one it's enough for your problem. For your example (uk and dubai) , you can set an instance in France or London that are a lot closer than Oregon. This is what it's cloud. And this is why cloud was created. Since you already have the assets in cloud front you have to do the same with servers, and the way to do that is to clone the instance to the closest region. Without this solution you are going back to the old times (one server for all the world) = no cloud = large traveling times
EDIT2:
you can try use some tool like pingdom to check the differences response times across the world. With this you can check and verify that the connection is a lot faster from Oregon that was from UK and Dubai. You will also see the response times from cloudfront, to check that it's working as it should
We are building IVR based application where user can talk to voice bot to get his query resolved. as our Team decided to go with amazon connect and amazon lex to build this application.
But our client is from saudi arabia region and we are not sure that does it work In there region.
Please help.
Please find below the list of region Lex is available,
http://docs.aws.amazon.com/lex/latest/dg/API_Reference.html
and list of region-specific services - https://aws.amazon.com/about-aws/global-infrastructure/regional-product-services/
Still, you can connect to API of the available region and can pass date of the time zone you want to use.
To set the time zone used to resolve dates so that it is relative to the user's time zone, use the x-amz-lex:time-zone request attribute. If you do not specify a time zone in the x-amz-lex:time-zone attribute, the default is America/New York.
I have a project with Web part on both areas (EU and China) and i have two account on both AWS (Global and AWS China).
Can i make private channel between Chinese Zone and any Zone in Global AWS (for example Signapore) for replication of DB/Sync data and other issues.
I need something like that private channel because ping and connect between that zones via public DNS almost already bad.
Maybe someone have some experience with some architecture like this.
Thank you.
Note in most cases this works poorly for China because VPNs generally are not stable across the GFW interface; you can stay up for a while but IPSEC, etc. are not stable. Some companies can do cross-connects such as Aryaka and CBC, and of course MPLS - expect $1-3K/month to start.
Ideally you would use an official third party connection with DirectConnect to connect Singapore with one of the AWS China regions. I know China Mobile International can do this.
I'm looking for a way to pick the best AWS region to host a Proof of Concept installation for a potential customer in India.
For this, I'd like to try to ping the customer's web site (I verified that it's hosted in India, I assume by the customer itself since that's part of their business) from multiple AWS regions and see which one gives best results.
I found multiple tools which would allow me to run ping from my own browser to multiple AWS locations (e.g. https://cloudharmony.com/speedtest, http://www.cloudping.info/) but none which will allow me to ping between all AWS regions and a specific third party.
Does such a tool exist, or is my only option to run up an EC2 instance in each region and try to ping from it?
You might want to check the answers to this very similar question.
Keep in mind that not all regions have all AWS services available at this time, so make sure the region you pick has all the services that you plan to use. Also, Amazon has said that an India region is in the works.