I'm new to Amazon Cloud Directory. I've been experimenting with adding objects via SDK (Javascript v3 SDK).
Is there way to see the objects in either the AWS Console or via some kind of developer client tool. I'm talking about a tool that does the same job as Compass does for MongoDB or SQLAce does for MySql etc.
Not being able to visually confirm the results of my experiments is frustrating.
Related
When we migrate from the SafetyNet Api to Google Play Integrity Api we need link a PlayStore application to the Google Cloud Project in the Google Play console.
For existing on production application should it be the same google cloud project in which safetyet's keys were created? Or can it be different/new Google Cloud project and it will not affect the existing clients? Does it matter which account I will link? What should I do if I lost the account which originally was used to created the SafetyNet API keys?
I search through Google's documentation but I have not found any information about this matter. I also have not used increased api usage quota.
Those two API's are not dependent on each other.
I've tried same application with two different Google Cloud projects and got the same token response. So I believe the answer is yes - you can link a new Google Cloud Project to your application.
I have a simple shell script which issues several commands using awscli and displays information to the screen. It depends on having correct settings in ~/.aws/config and ~/.aws/credentials. I want to distribute it to about 10 users who have IAM accounts with limited privileges. However I don't want to use the shell - I want something cross-platform, easy to use for the users and easy for me to update. So I decided that I want to create a simple web application in JS instead, using the AWS SDK.
It seems that this use case is specifically supported by AWS, the first bullet point under "Common Use Cases" in What Is the AWS SDK for JavaScript? is "Build a custom console to AWS services in which you access and combine features across Regions and services to best meet your organizational or project needs" which exactly describes what I want to do.
The problem is that I can't find the relevant documentation on how to perform the user authentication. All the examples that I was able to find talk about some "Amazon Cognito" service and discuss much more complicated use cases, such as authenticating pools of external users through an external authentication provider and mapping them to IAM roles, which sounds too complicated for what I want to do. Is there a way to just authenticate the users that I have with their IAM user/password, and authorize them to access the AWS services based on their existing IAM permissions? Or is using Cognito, creating additional roles, etc. mandatory?
While writing this question I found out another question about AWS Amplify and now I'm even more confused. Is AWS Amplify what I would want to use?
You can write a web app using the AWS SDK for JavaScript that invokes various AWS Services. You do NOT need to use AWS Amplify to create a web app.
A Web application that uses the AWS SDK for JavaScript uses creds like any other AWS app. Here is an AWS tutorial that shows how to use the AWS SDK for JavaScript to write a basic web app that invokes the AWS SQS service. It will hopefully point you in the right direction.
Creating an example messaging application
This topic covers Prerequisites and other information, such as creating the required AWS resources, you need to know to write a web app using the AWS SDK for JavaScript.
Also - the link you referenced was the JavaScript V2 DEV Guide. Its better to use the AWS JavaScript V3 DEV Guide.
I am developing an application that uses the google api to create projects on the google cloud platform and enable these projects to the Dialogflow api.
For this reason I created a service account with the Cloud Resource Manager API and Service Usage API enabled. In sequence I send two HTTP POST requests to the service account first to the address:
https://cloudresourcemanager.googleapis.com/v3/projects
to create a new project and then to the address
https://serviceusage.googleapis.com/v1/projects/{0}/services/dialogflow.googleapis.com:enable
to enable the Dialogflow api on the new project (clearly in place of {0} I'm going to put the code of the new project returned by the previous API).
Initially and for some time everything worked fine. Projects were created and with the Dialogflow API enabled.
Then all of a sudden the second api to enable dialogflow gives me a resource not found error and it doesn't work anymore.
I understand that the problem is the following:
the API for creating new project, although it does not give me any errors and is done successfully, it does not really create the project in the google cloud platform.
I add that I have a Google Cloud Identity account (required to address a parent folder when a new project is created) and an account with billing details linked to the service account. I also applied to Google to increase the maximum limit of projects allowed on the google cloud platform.
I don't know why suddenly google no longer allows me to create projects via its api.
Problem: Google Cloud Run only provides a subset of documented metadata
I have a simple JVM based application running on Google Cloud Run that queries http://metadata.google.internal for available metadata.
The only metadata available is at the following paths:
http://metadata.google.internal/computeMetadata/v1/instance/service-accounts
http://metadata.google.internal/computeMetadata/v1/instance/zone
http://metadata.google.internal/computeMetadata/v1/project/project-id
http://metadata.google.internal/computeMetadata/v1/project/numeric-project-id
As per the documentation, I was expecting more than this and hoping that I would be able to query the metadata server for the name of the Cloud Run service and the metadata required to configure Stackdriver Monitoring for a generic_node.
One clue that I have found is in the server header in the response from querying the Metadata server gives the value: Metadata Server for Serverless
Theory: Cloud Run is in beta and the Metadata Server for Serverless is separate from the typical metadata server and is a work in progress.
Question(s):
Is this theory valid?
Is this limitation documented somewhere?
Is there a roadmap for adding additional metadata?
Is there an alternative for determining the metadata needed to configure Stackdriver?
Compute Metadata service you linked is only available to Compute Engine products (such as GCE, GKE). Many of the endpoints in there are about VM details, VM metadata/tags, VM startup scripts etc.
These concepts don't apply to serverless compute environments. Therefore I don't think a feature request here will succeed.
Serverless products such as App Engine, Cloud Functions and Cloud Run support a minimal version of the metadata service to provide basic functionality to SDKs (such as Google Cloud client libraries, Stackdriver or OpenTelemetry/OpenCensus clients, or gcloud CLI). Using these endpoints, Google’s own client libraries can automatically get auth tokens, discover project IDs etc.
Also, these serverless products don't run on GCE, and don't have the same concepts. That's why a full metadata service isn't available for these products.
The applicable for serverless environments are the endpoints you listed in your question.
I don't think you will find much information in order to validate your theory as that has to do with the product's architecture and I don't think Google will share it for the moment, however, it does seem to be valid based on the evidence you found.
What can be done is to open a feature request to Google so that they work on adding more information to the metadata so that it cover your needs. As the product is on beta, they should be open to do some changes.
Hope you find this useful.
I am new to gcloud, I want to create my first gcloud vision and video intelligence project but do not know how to start and what are the pre-requisite for this. I have Windows 10 laptop and also created my goggle cloud account. Can you please guide my on setup work and how to start development work.
Thanks in Advance
Prerequisites: a Google Cloud Platform project with the Video Intelligence API and Vision API both enabled. The APIs are the interfaces between you / your applications and the Cloud services. There are multiple options to access the APIs:
One option is to install the Cloud SDK on your machine and initializing it - linking it with your project.
Afterwards, the Cloud SDK, which
is a set of tools for Cloud Platform. It contains gcloud, gsutil, and bq, which you can use to access Google Compute Engine, Google Cloud Storage, Google BigQuery, and other products and services from the command-line. You can run these tools interactively or in your automated scripts.
has the proper (command-line) tools to access the Google Cloud Vision and the Google Cloud Video Intelligence products.
Another option is to make direct calls to the APIs, i.e. via the REST endpoints. You can read about Cloud Vision APIs here, Video Intelligence APIs here and test them via Google's API Explorer.