I have a free account for the past 4 months on oracle cloud, it has a tenancy in Frankfurt and it has a vm computing instance
my free tier was expired about 3 months ago and i continued with always free resources, since then it worked just fine until they suddenly sent me a mail stating that my account free tier has ended (again!!) and that i was limited to always free resources.
i tried to connect to my vm but obviously it is down, when i log in to oracled cloud admin console it is working but when i log to the infrastructure dashboard it show me a page just saying :
{
"code" : "NotAuthenticated",
"message" : "The required information to complete authentication was not provided or was incorrect."
}
and they have exclusive support for paid accounts only.
so is there any help ?
Related
I wanted to create a Always Free Eligible VM Instance (VM.Standard.E2.1.Micro) on the Oracle Cloud, but it's not on my list.
And when I check my limit for VM.Standard.E2.1.Micro in
"Governance > Limits, Quotas and Usage", it say 0.
How can I create one? My Home Region is Canada Southeast (Montreal), ca-montreal-1.
My account's trial is not over yet. Should I wait till my trial is over to create it?
As per the Always Free website, at any time you can have up to the following:
Two Oracle Autonomous Databases with powerful tools like Oracle Application Express (APEX) and Oracle SQL Developer
Two Oracle Cloud Infrastructure Compute VMs; Block, Object, and Archive Storage; Load Balancer and data egress; Monitoring and Notifications
If you already are at capacity for this, then you would not be able to add an additional. Further details of Always Free resources can be found here - https://docs.oracle.com/en-us/iaas/Content/FreeTier/resourceref.htm
The always free provide you with the following
2 Compute virtual machines with 1/8 OCPU and 1 GB memory each.
2 Block Volumes Storage
100 GB total.
10 GB Object Storage.
10 GB Archive Storage.
Resource Manager: managed Terraform.
Focus on the specs of the free one
VM.Standard.E2.1.Micro is not available for ca-montreal-1 at this time (January 2021).
I created a new account in the Ashburn region where VM.Standard.E2.1.Micro is available.
I have an application that generates some reports at every hour. These reports are very critical (and sensitive) to the users and the only access is through the application (excel/pdf generation in memory with database) with previous user/password/role validation.
Last week the server that host the application shut down for several hours (hardware failure) and the users could not retrieve those reports (and i cant access to the db inmediatly).
My client needs to at least access the last generated reports. For example, if the failures occurs at 5 pm, he needs the report of the 4 pm.
So, i thought in store the reports in other place. The server/network administration is not my responsability. I dont have another server (and i cant avoid the network or hardware failures for ever), but i have a hard drive connected to the same server network (NAS).
Also i am thinking in storing the reports in Google Drive (client G suite with some encryption) or some other cloud service. But i am aware that i need permanent internet access.
¿What do you recommend me to do?
Have a nice day.
The best approach uses Nginx and creates multiple instances of the executable file and point to it if one instance stay down, the other instance will serve and the app will be live
When i clicked through my google cloud console yesterday, i found 26 virtual machines that i disabled then (because i think that i don´t use these - but i pay for them).
I use firebase, firestore, firestorage, firebase cloud functions and
app-engine / flex-engine for php and python cron-jobs.
But today, there are 26 more vms up and running and my bill goes up. Can I disable / delete these machines and disable building new ones or disable the google-compute-engine overall?
According to our documentation about Billing for stopped instances:
Your instances are not charged for per-second usage charges in TERMINATED state but any resources attached to the virtual machine will be charged until they are deleted, such as static IPs and persistent disks.
The link1 will also provide you with details about the state of resources for stopped instances.
For more pricing information. I would recommend that you visit the following links:
1- Google Compute Engine Pricing.
2- Pricing details on each GCP product.
To know how to manage and modify your project billing settings and many more. Visit our cloud billing documentation.
If we use Azure API management premium do we need to create a backup (disaster recovery) strategy?
It is replicated in as many separate regions as you want.
In the past, with non-premium we have called the API Management REST API to backup to Azure blog storage.
Obviously, you should always have a DR strategy but just wondering if it is overkill in this scenario.
Azure ApiManagement offers SLA on Proxy/Gateway uptime, so if you have a API Management deployed in multiple regions, the Proxy will continue to run, automatically failing over to non affected regions.
However the Publisher Portal, Developer Portal and Management REST Endpoint is still only hosted in the Master Region. If there a region wide disaster in the Master region of your service, they will not be accessible. Which would mean you cannot add new API/operations and new customers cannot subscribe for your service.
If one of the additional regions is impacted, the Proxy/Gateway it will sync up to latest configuration before starting up.
I am in the process of creating an Exchange Service account to listen for EWS notifications for up to 2000 mailboxes. I have been reading through the documentation and it states that
Sa1 can open the connection in the following ways:.... By
impersonating any of the users — m1 for example — so that the
connection is charged against a copy of m1’s budget. (M1 itself can
open ten connections by using Exchange Online, and all service
accounts impersonating m1 can open ten connections by using the copied
budget.)
If the connection limit is hit, the following workarounds are
available: If option 1 is used, the administrator can create multiple service accounts to impersonate additional users.
The microsoft documentation is here: (https://msdn.microsoft.com/EN-US/library/office/dn458789(v=exchg.150).aspx)
Can someone tell me if it is possible to open up 2000 streaming connections to EWS using the same service account by impersonating 2000 mailboxes?
Thanks.
Can someone tell me if it is possible to open up 2000 streaming connections to EWS using the same service account by impersonating 2000 mailboxes?
Yes I have apps that work with 3000+ users but it can be environment dependant. As the link you posted suggests that you should be using Grouping to maintain affinity in 2013 and greater. There is a maximum of 200 user per group (which basically means per connection). The concurrent connection charge if your using Grouping and Impersonation should be charged to the Mailbox your Anchoring the Group connection to (which is generally the first user in the group) not the service account. As each group should have a different anchor Mailbox you shouldn't run into any problems with the 10 User concurrent connection limit.
If you are using Exchange Online you'll find your users are spread across a large number of Servers and most probably data-centres so as long you implement grouping and impersonation correctly you shouldn't have any issues.