AWS GameKit policies missing - amazon-web-services

I'm trying to integrate GameKit into a Unity project. I have difficulty with setting up the Login Credentials based on the following explanation
https://docs.aws.amazon.com/gamekit/latest/UnityDevGuide/setting-up-account-user-console.html
I can't seem to find the GameKitDeveloperPolicy in the list of policies. Also I don't see the GameKit service in the console.
Also I can't seem to find the suggested python plugin in the directory of the plugin
Am I missing something?

Related

Can I bind UI components to models with Amplify Studio without DataStore enabled?

I'm exploring using AWS Amplify for a personal project. I'm finding many tutorials for data binding, using collections, building forms with the Amplify UI... all features that I am excited to use. However, I'm struggling to figure out how to use many of Amplify Studio's features without enabling Amplify DataStore, a feature that I do not need for my project (and would prefer the simplicity of an architecture without it).
I can't seem to find any documentation anywhere (in AWS docs, stackoverflow answers, google searches...) that says enabling DataStore is required to bind my models to my UI components using Amplify's UI Library.
The only message that comes close is Enable DataStore to edit your data model visually on the Data tab in Amplify Studio, suggesting that enabling DataStore is required to modify the schema.graphql file using the UI, which feels very arbitrary to me.
I can't understand why DataStore would be mandatory for so many of Amplify Studio's features, and since I can't find any documentation specifying this... I feel like I'm misunderstanding something. But Amplify Studio also seems to be hinting that DataStore is indeed required.
Can I leverage AWS Amplify Studio's UI Library feature to bind my UI components to my data models without enabling DataStore?
Digging more through the AWS documentation, I came across this:
https://docs.amplify.aws/console/data/data-model/#data-modeling-in-amplify-studio
All data models built with Studio work with Amplify DataStore out-of-the-box.
Another way to word that could be:
Building a data model with Amplify Studio requires enabling Amplify DataStore for your project.
Looks like I have to accept enabling Amplify DataStore for my project in order to leverage the rest of Amplify Studio's features.

How to add billing permission to expo managed app?

I’m using expo sdk 42.0.0
The relevant platform is android
I’m using expo managed workflow, and right now I’m trying to implement IAP (In App Purchases). I saw that google play won’t let me add In App Product because I don’t have the BILLING permission in my apk/aab.
What I already did:
I’ve installed expo-in-app-purchases because I though it would make expo add the BILLING permission automatically.
I tried added to the app.json file the following line: "permissions": ["com.android.vending.BILLING"]
I also notice that when I add other permissions, it does not work. Maybe there is a problem with expo app.json permission in android.
Nothing worked. What can I do more to add the BILLING permission to my app?
Expo announced that it's their bug and how to workaround it. The link
To implement IAP u need one special package, u can find the tutorial here in the doc:
https://docs.expo.dev/versions/latest/sdk/in-app-purchases/

AWS full-stack react app. Build failed to complete successfully

I'm trying to make an SPA in React with AWS.
While I was going through the basic steps here (Step 3 ADD AUTHENTICATION ) :
I deployed the changes to the live environment, but the build failed.
I'm getting this error.
Can anyone please explain to me what caused this error?
This seems to be a known issue in the Amplify GitHub and can happen when the Amplify CLI version used by the Amplify Console is mismatched with the version you are using locally. Here is some more information: https://github.com/aws-amplify/amplify-cli/issues/6117#issuecomment-794176834
Compare your Amplify App -> Build Settings -> Build image settings -> Amplify CLI version with your version installed on your development machine by running amplify --version
Other than checking for version matching, I also have found out if amplify backend doesn't have a role attached to it, the built process is going to fail. to do that you follow the link bellow directions: https://docs.aws.amazon.com/amplify/latest/userguide/how-to-service-role-amplify-console.html
However, before that, go to the General tab under App settings to see if the role is empty or not. You might already have a role, if not follow that link.

I want to add “aws-iot-device-sdk” to my project

I want to add “aws-iot-device-sdk” to my project, but I couldn’t find such a plugin for vue js. Have you used it before.
https://github.com/aws/aws-iot-device-sdk-js
You can install aws iot sdk for javascript.

Ionic AWS Error

I am attempting to connect my Ionic mobile app to AWS backend and keep getting the same error.
Cannot find module "../aws-exports"
I've checked the node-modules folder and this is missing, but I have no idea what I should put here to fix this error.
The same code is in a lot of files in this app.
const aws_exports = require('../aws-exports').default;
I'm not sure what this code does exactly. If anyone has an experience with Ionic that could help that would be great.
Thanks,
Matthew.
You need to follow the steps in the README. Specifically, the section on Creating AWS Mobile Hub Project. When you init the AWSMobile project, aws-imports is created for you.
P.S. aws-amplify has introduced some changes in the last couple of weeks that cause the ionic starter to not work. Follow these steps to fix the errors.
If you sign into your Amazon console and you go to your Mobile Hub.
https://console.aws.amazon.com/mobilehub/home#/
You can click on your project and it will return the ID in the URL as follows:
https://console.aws.amazon.com/mobilehub/home#/YOUR_ID_HERE/build
You can then run the following command:
awsmobile init <mobile-hub-project-id>
The AWS Mobile Hub scripts should then fetch all relative dependencies and make the appropriate installations to rectify the issue.