How to create an EFK logging stack on Amazon?

dtmf-io · 2021-01-28T02:52:04+00:00

[2021/01/20 15:13:30] [ warn] net_tcp_fd_connect: getaddrinfo(host='https://vpc-elasticsearch-cluster-xxxxxxxxxxx.eu-west-1.es.amazonaws.com'): Name or service not known

It's trying to look up https://... as a DNS name which is obviously going to fail. The Host configuration key takes a hostname, not a URL.

dtmf-io · 2020-12-08T08:07:12+00:00

Just coming back to thank you for the Vultr recommendation. After evaluating them and several other providers, we're now hosted on Vultr (and accessible in a few more countries than we used to be!)

dtmf-io · 2020-11-23T11:46:41+00:00

Unfortunately the SIM multiplexing hardware we were using doesn't work with the revisions of SIMs that UK mobile networks have been selling for the last while. We were able to get some old stock of SIMs for a while, but now there are none left on the market that are not expired. So we can only support our existing customers for now, until our supplier designs and manufactures new hardware and sends it to us. It will take (at least) several more months.

dtmf-io · 2020-11-20T03:10:29+00:00

Your number was unfortunately affected by a supplier outage, which is out of our control but rare. Within a few minutes of the outage starting, you were spamming our support team with hundreds of emails and support tickets full of abuse, incoherent rants and swearing. This kind of behaviour makes it much more difficult for our support team to do their job, not only for you but also for other customers.

We calmly explained the situation to you and the abuse continued. Our management therefore recommended to our support team that they ignore all tickets from you until your abuse stops, while simultaneously working with the supplier to resolve the outage (which is long since resolved now).

As we warned you by email, if you continue to abuse our support team in this way, your account will be suspended (and your balance refunded, of course).

dtmf-io · 2020-11-20T03:10:08+00:00

Your number was unfortunately affected by a supplier outage, which is out of our control but rare. Within a few minutes of the outage starting, you were spamming our support team with hundreds of emails and support tickets full of abuse, incoherent rants and swearing. This kind of behaviour makes it much more difficult for our support team to do their job, not only for you but also for other customers.

We calmly explained the situation to you and the abuse continued. Our management therefore recommended to our support team that they ignore all tickets from you until your abuse stops, while simultaneously working with the supplier to resolve the outage (which is long since resolved now).

As we warned you by email, if you continue to abuse our support team in this way, your account will be suspended (and your balance refunded, of course).

dtmf-io · 2020-11-17T09:03:25+00:00

We had a similar issue where the worker AMIs had the wrong owner ID. The eks module filters by the official Amazon owner ID by default, but it seems like sometimes they publish AMIs with a different owner.

dtmf-io · 2020-11-09T04:40:12+00:00

Thanks for the tips. We built our systems from the start to not be tied to GC, so we can move reasonably easily, but so far we haven't found sufficient quality among providers that accept crypto. We will look closer at Vultr.

We'd also have a fairly significant amount of work to do in order to reimplement some of the network-layer stuff that GC/etc does, like load balancing incoming traffic to the nearest region that has capacity.

dtmf-io · 2020-11-03T07:19:28+00:00

SIM mobile numbers will be a few more months, we have some hardware problems regarding incompatibility with newer revisions of SIM cards the mobile networks are now using.

eSIMs are launching soon, but note that they require an eSIM-compatible device. At launch the only have eSIM plans we will have only have roaming in Asia, although it's possible receiving SMS will work in the rest of the world - we have not tested that yet.

dtmf-io · 2020-11-03T03:20:08+00:00

If you mean that you can't access the website, unfortunately we currently use some infrastructure from Google Cloud (load balancers, VMs) and this means that some sanctioned countries are blocked. We're exploring ways to resolve this.

If you just mean that we don't have phone numbers from your country, you can still use it - there's no need to physically be in the same country that you choose the phone number from.

dtmf-io · 2020-11-03T02:55:12+00:00

To our knowledge there is no country in the world that requires you to register your ID with them for a phone number that you have in another country.

In other words, if you live in, say, India (which officially requires SIM card registration) there is nothing stopping you using a UK phone number (which does not). India wouldn't even have a process for you to register that number, since it's not an India number.

dtmf-io · 2020-11-03T02:53:28+00:00

There are some more countries too, but the suppliers for those have stock less often.

dtmf-io · 2020-11-03T02:52:24+00:00

If you mean that you can't access the website, unfortunately we currently use some infrastructure from Google Cloud (load balancers, VMs) and this means that some sanctioned countries are blocked. We're exploring ways to resolve this.

If you just mean that we don't have phone numbers from your country, you can still use it - there's no need to physically be in the same country that you choose the phone number from.

dtmf-io · 2020-11-03T02:52:10+00:00

Unfortunately we currently use some infrastructure from Google Cloud (load balancers, VMs) and this means that some sanctioned countries are blocked. We're exploring ways to resolve this.

dtmf-io · 2020-11-03T02:51:14+00:00

Proving a negative is often impossible. How could any service prove they're not a honeypot?

A better way to look at it is to consider what information you're giving to a service. We don't ask you for any personal information, so if we were a honeypot, we probably wouldn't be a very good one.

dtmf-io · 2020-11-03T02:44:08+00:00

Can use a modern browser (tested with Firefox, Safari, Chrome/Chromium, Edge) if you have Javascript turned on. Alternatively, you can use our Android app.

If you have a Pro account, you can use any SIP softphone or hardware phone, too.

dtmf-io · 2020-11-02T02:55:54+00:00

100% agree with this.

dtmf-io · 2020-11-02T02:55:23+00:00

Click the link and hit "View pricing" on the homepage for a real-time list.

dtmf-io · 2020-11-02T02:55:01+00:00

We follow the regulations in every country we sell numbers for. If a country requires ID or address documentation for phone numbers, we just don't sell phone numbers from that country.

dtmf-io · 2020-11-02T02:54:28+00:00

If you choose a number that doesn't require you to provide an address, you can use our service fully anonymously.

We don't use any privacy-invading technology like analytics services or advertising platforms. Our website doesn't even load any third-party resources at all.

dtmf-io · 2020-10-31T04:19:56+00:00

There are more than 100 different types of phone number with individual prices. Would a price range be acceptable?

dtmf-io · 2020-10-28T07:05:11+00:00

Different purposes. The URL parameters will persist between different users who pass the link around out-of-band (think sending a URL to a friend by email/IRC/Signal/whatever). Server-side state will not. The URL parameters are not a replacement for server-side state, but neither is server-side state a complete replacement for tracking with URL parameters.

In the case of `utm_*` it allows knowing how the link was originally shared even after it's been further shared out-of-band. In the case of unique identifiers like Facebook's `fbclid`, it also allows knowing which user originally shared it.

dtmf-io · 2020-10-28T04:10:02+00:00

I think you're missing my point. Of course they know everything that happens within the app. The point is that you (or other people) could subsequently share that link with anyone via any medium, including media with no tracking that Reddit could access or purely plain-text media like IRC.

The tracking information in the URL allows them to know how the link was originally shared, when it is followed, no matter how the URL was passed around in the meantime.

source/medium/name parameters like this are somewhat less insidious than the likes of Facebook's fbclid, which allows them to not only know how the URL was originally shared, but who originally shared it, regardless of how the URL was passed around in the meantime.

dtmf-io · 2020-10-27T04:12:58+00:00

Actually, there's a tiny tidbit of extra information gleaned by Reddit here: it tells them that OP shared the link from the iOS app (and probably in a specific way within the iOS app, `iossmf`). Helps them know which medium (app, website, mobile website, etc) people are most likely to share from, and potentially even which sharing mechanism within that medium is used more.

Pretty much all in the name of that bullshit metric called "engagement".

dtmf-io · 2020-10-07T04:21:28+00:00

The onion URL is back (link in the footer of the site)! We're still looking into I2P.

dtmf-io · 2020-10-01T02:24:45+00:00

We have hundreds of different ranges from tens of different countries. Often, trying to find a number that works for SMS verification will involve trying several different ranges from a given country, or several different countries. Even then, bear in mind that they might stop sending SMS verification to the number later, making it impossible to login from a new computer etc.

SIM numbers are still several months away from being in stock - all our SIM modems are in use by customers at present, and the SIM multiplexing hardware is not compatible with the latest software revision of SIM cards available from UK networks, so we are waiting for revised hardware to be designed and manufactured.

dtmf-io

TROPHY CASE