Apns Voip Channel
Provides a Pinpoint APNs VoIP Channel resource.
Note: All arguments, including certificates and tokens, will be stored in the raw state as plain-text.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
import * as std from "@pulumi/std";
const app = new aws.pinpoint.App("app", {});
const apnsVoip = new aws.pinpoint.ApnsVoipChannel("apns_voip", {
applicationId: app.applicationId,
certificate: std.file({
input: "./certificate.pem",
}).then(invoke => invoke.result),
privateKey: std.file({
input: "./private_key.key",
}).then(invoke => invoke.result),
});
import pulumi
import pulumi_aws as aws
import pulumi_std as std
app = aws.pinpoint.App("app")
apns_voip = aws.pinpoint.ApnsVoipChannel("apns_voip",
application_id=app.application_id,
certificate=std.file(input="./certificate.pem").result,
private_key=std.file(input="./private_key.key").result)
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Aws = Pulumi.Aws;
using Std = Pulumi.Std;
return await Deployment.RunAsync(() =>
{
var app = new Aws.Pinpoint.App("app");
var apnsVoip = new Aws.Pinpoint.ApnsVoipChannel("apns_voip", new()
{
ApplicationId = app.ApplicationId,
Certificate = Std.File.Invoke(new()
{
Input = "./certificate.pem",
}).Apply(invoke => invoke.Result),
PrivateKey = Std.File.Invoke(new()
{
Input = "./private_key.key",
}).Apply(invoke => invoke.Result),
});
});
package main
import (
"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/pinpoint"
"github.com/pulumi/pulumi-std/sdk/go/std"
"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
pulumi.Run(func(ctx *pulumi.Context) error {
app, err := pinpoint.NewApp(ctx, "app", nil)
if err != nil {
return err
}
invokeFile, err := std.File(ctx, &std.FileArgs{
Input: "./certificate.pem",
}, nil)
if err != nil {
return err
}
invokeFile1, err := std.File(ctx, &std.FileArgs{
Input: "./private_key.key",
}, nil)
if err != nil {
return err
}
_, err = pinpoint.NewApnsVoipChannel(ctx, "apns_voip", &pinpoint.ApnsVoipChannelArgs{
ApplicationId: app.ApplicationId,
Certificate: pulumi.String(invokeFile.Result),
PrivateKey: pulumi.String(invokeFile1.Result),
})
if err != nil {
return err
}
return nil
})
}
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.pinpoint.App;
import com.pulumi.aws.pinpoint.ApnsVoipChannel;
import com.pulumi.aws.pinpoint.ApnsVoipChannelArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
public static void main(String[] args) {
Pulumi.run(App::stack);
}
public static void stack(Context ctx) {
var app = new App("app");
var apnsVoip = new ApnsVoipChannel("apnsVoip", ApnsVoipChannelArgs.builder()
.applicationId(app.applicationId())
.certificate(StdFunctions.file(FileArgs.builder()
.input("./certificate.pem")
.build()).result())
.privateKey(StdFunctions.file(FileArgs.builder()
.input("./private_key.key")
.build()).result())
.build());
}
}
resources:
apnsVoip:
type: aws:pinpoint:ApnsVoipChannel
name: apns_voip
properties:
applicationId: ${app.applicationId}
certificate:
fn::invoke:
function: std:file
arguments:
input: ./certificate.pem
return: result
privateKey:
fn::invoke:
function: std:file
arguments:
input: ./private_key.key
return: result
app:
type: aws:pinpoint:App
Import
Using pulumi import
, import Pinpoint APNs VoIP Channel using the application-id
. For example:
$ pulumi import aws:pinpoint/apnsVoipChannel:ApnsVoipChannel apns_voip application-id
Properties
The application ID.
The pem encoded TLS Certificate from Apple.
The default authentication method used for APNs. NOTE: Amazon Pinpoint uses this default for every APNs push notification that you send using the console. You can override the default when you send a message programmatically using the Amazon Pinpoint API, the AWS CLI, or an AWS SDK. If your default authentication type fails, Amazon Pinpoint doesn't attempt to use the other authentication type. One of the following sets of credentials is also required. If you choose to use Certificate credentials you will have to provide:
The Certificate Private Key file (ie. .key
file). If you choose to use Key credentials you will have to provide:
The ID assigned to your signing key. To find this value, choose Certificates, IDs & Profiles, and choose your key in the Keys section.